Mediant 3000 User's Manual Ver 4.8

TrunkPack Series
Mediant 3000
TrunkPack: VoIP cPCI & PCI Boards

Mediant Media Gateways
Users Manual version 4.8
Document # LTRT-95203
December 2005
User's Manual
Contents
Table of Contents
Introductory Notes ..................................................................................................21
1
Overview of the Mediant 3000 ..........................................................................23

1.1
1.2
1.3
General Features .....................................................................................24

High Availability.......................................................................................25
Functional Block Diagram ......................................................................27
Mediant 3000 Hardware Equipment .................................................................29

2.1
The Mediant 3000 Chassis ......................................................................29

2.1.1
2.2
The Mediant 3000 Boards .......................................................................31

2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.3
Alarm Indicators....................................................................................... 54
Mediant 3000 Hardware Installation.................................................................57

3.1
Unpacking ................................................................................................58
3.1.1
3.2
3.3
3.4
Package Contents ................................................................................... 58
Mounting the Mediant 3000 Chassis......................................................58

Cabling the Mediant 3000 .......................................................................61
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
Connecting the Earth ............................................................................... 62

Connecting the PSTN and ATM Interfaces.............................................. 62
Ethernet Ports.......................................................................................... 66
PEM/DC/3K Connections ........................................................................ 66
Connection the DC Power ....................................................................... 68
Component Replacement and Maintenance .........................................69

3.4.1
3.4.2
3.4.3
3.4.4
Power Consumption ................................................................................ 51

DC Input Power ....................................................................................... 51
The Power Entry Module (PEM/DC/3K) .................................................. 51
PS/DC/3K Power Supply Modules........................................................... 53
Cooling System .......................................................................................53

2.4.1
The TP-6310 Board and RTM ................................................................. 32

TP-6310 Board Panel LED Indicators...................................................... 36
6310/RTM ................................................................................................ 42
SA/M3K Synchronization and Alarm Board ............................................. 46
Board Hot-Swap Support......................................................................... 50
Power........................................................................................................50
2.3.1
2.3.2
2.3.3
2.3.4
2.4
Mediant 3000 Chassis ............................................................................. 30
Board Replacement ................................................................................. 70

PS/DC/3K Module Replacement ............................................................. 72
PEM/DC/3K Replacement ....................................................................... 72
Fan Tray Unit Replacement..................................................................... 73
Software Package..............................................................................................77
4.1
Unzipping the Software Package ...........................................................77

4.1.1
4.1.2
Version 4.8
Installing/Unzipping When Using a Windows Operating System ......... 77

Unzipping When Using a Linux/Solaris Operating System............... 78
December 2005
Mediant 3000
4.2
5
Software Directory Contents & Structure..............................................78
Getting Started ..................................................................................................81

5.1
Assigning the Mediant 3000 IP Address................................................81

5.1.1
5.1.2
5.2
6
Assigning an IP Address Using HTTP ..................................................... 81

Assigning an IP Address Using BootP..................................................... 82
Assigning the IP Addresses for High Availability Mode ......................82
Mediant 3000 Initialization & Configuration Files ...........................................83

6.1
6.2
6.3
Boot Firmware & Operational Firmware ................................................83

Mediant 3000 Startup ..............................................................................83
Using BootP/DHCP..................................................................................86
6.3.1
6.3.2
6.3.3
6.3.4
6.3.5
6.4
Configuration Parameters and Files ......................................................91

6.4.1
6.4.2
6.4.3
6.5
6.6
6.7
6.8
6.9
BootP/DHCP Server Parameters............................................................. 86

Host Name Support ................................................................................. 89
Selective BootP ....................................................................................... 89
Vendor Specific Information..................................................................... 89
Microsoft DHCP/BootP Server ............................................................. 90
Initialization (ini) File ................................................................................ 91
Auxiliary Files........................................................................................... 97
Automatic Update Facility ........................................................................ 98
Backup Copies of ini and Auxiliary Files.............................................100

Upgrading Mediant 3000 Software .......................................................100
Initializing the Mediant 3000 System in High Availability Mode ........100
Mediant 3000 System Initilization Process..........................................100
Special Mediant 3000 System Specific Behavior................................101
6.9.1
6.9.2
Rebooting the Redundant TP-6310 Board ............................................ 101

High Availability and SysLog ................................................................. 101
6.10 Actions upon Detecting Board Failure ................................................101

6.10.1 Failure in Active Board........................................................................... 101
6.10.2 Failure in a Redundant Board................................................................ 102
Standard Control Protocols ...........................................................................103

7.1
MGCP Control Protocol ........................................................................103

7.1.1
7.1.2
7.1.3
7.1.4
7.1.5
7.1.6
7.1.7
7.1.8
7.1.9
7.1.10
7.1.11
7.1.12
7.1.13
User's Manual
MGCP Overview .................................................................................... 103

MGCP Operation ................................................................................... 103
MGCP Call Agent Configuration ............................................................ 104
Configuration and Update of the Endpoint's Notified Entity ................... 104
MGCP KeepAlive Mechanism ............................................................... 105
MGCP Piggy-Back Feature ................................................................... 105
SDP Support in MGCP .......................................................................... 105
MGCP Fax ............................................................................................. 106
Fax Transport Type Setting with Local Connection Options.................. 109
MGCP Profiling ...................................................................................... 109
TGCP Compatibility ............................................................................... 110
Electronic Surveillance (CALEA) ........................................................... 110
RTP Media Encryption RFC 3711 Secured RTP................................ 111
4
User's Manual
7.1.14
7.1.15
7.1.16
7.1.17
7.2
MEGACO Overview............................................................................... 134

Operation ............................................................................................... 135
SDP Support in MEGACO ..................................................................... 145
Mapping Payload Numbers to Coders................................................... 157
Supported MEGACO Packages ............................................................ 159
MEGACO Profiling................................................................................. 170
MEGACO Termination Naming ............................................................. 170
VoATM Media Server Support ........................................................................175

8.1
8.2
Related Standards .................................................................................175

ATM AAL1 ..............................................................................................176
8.2.1
8.3
8.4
SVC Access (ATM AAL1) ...................................................................... 176
ATM AAL2 ..............................................................................................177

8.3.1
8.3.2
8.3.3
8.3.4
MGCP Coder Negotiation ...................................................................... 117

MGCP Endpoint Map............................................................................. 131
Compression Coders ............................................................................. 131
STUN - Simple Traversal of User Datagram Protocol ........................... 133
MEGACO (Media Gateway Control) Protocol ......................................134

7.2.1
7.2.2
7.2.3
7.2.4
7.2.5
7.2.6
7.2.7
Contents
Bearer Path Selection............................................................................ 177

Voice Profile Selection........................................................................... 177
PVC Access........................................................................................... 178
SVC Access (ATM AAL2) ...................................................................... 179
Hairpinning of ATM Connections.........................................................180
Mediant 3000 Management.............................................................................183

9.1
Using SNMP ...........................................................................................183

9.1.1
9.1.2
9.1.3
9.1.4
9.1.5
9.1.6
9.1.7
9.1.8
9.1.9
9.2
Embedded Web Server .........................................................................202

9.2.1
9.2.2
9.2.3
9.2.4
9.2.5
9.2.6
9.2.7
9.2.8
9.2.9
9.2.10
9.2.11
9.2.12
9.2.13
9.2.14
Version 4.8
SNMP Standards and Objects............................................................... 183

Carrier-Grade Alarm System ................................................................. 185
Cold Start Trap ...................................................................................... 186
Performance Measurements ................................................................. 186
SNMP Interface Details ......................................................................... 193
SNMP NAT Traversal ............................................................................ 199
Systems ................................................................................................. 200
High Availability Systems....................................................................... 201
Administrative State Control .................................................................. 201
Embedded Web Server Protection & Security Mechanisms.................. 202
Limiting the Embedded Web Server to Read-Only Mode ...................... 204
Correlating PC / Mediant 3000 IP Address & Subnet Mask .................. 205
Accessing the Embedded Web Server .................................................. 206
Using Internet Explorer to Access the Embedded Web Server ............. 207
Getting Acquainted with the Web Interface ........................................... 208
Protocol Management............................................................................ 211
Advanced Configuration Screen ............................................................ 218
Status and Diagnostic Menu.................................................................. 260
Software Update .................................................................................... 265
Software Upgrade Key........................................................................... 273
Save Configuration ................................................................................ 276
Reset Button .......................................................................................... 277
Mediant 3000 High Availability Mode..................................................... 278
5
December 2005
Mediant 3000
9.2.15 Restoring and Backing Up the Device Configuration............................. 278
10 Diagnostics & Troubleshooting .....................................................................281

10.1 Syslog.....................................................................................................281
10.1.1 Operating the Syslog Server.................................................................. 282
10.2 The Embedded Web Server's 'Message Log' (Integral Syslog) .........283
10.3 Changing the Network Parameters via CLI .........................................283
10.3.1 Assigning an IP Address Using the Command Line Interface (CLI) ...... 284
10.4 TP-6310 Self-Test...................................................................................284

10.5 Control Protocol Reports......................................................................285
10.5.1 TPNCP Error Report.............................................................................. 285
10.5.2 MGCP/MEGACO Error Conditions ........................................................ 285
10.5.3 SNMP Traps .......................................................................................... 285
10.6 Solutions to Possible Problems...........................................................286

10.6.1 Possible Common Problems ................................................................. 286
10.6.2 Possible Voice Problems ....................................................................... 287
10.6.3 User Error Messages............................................................................. 288
11 Functional Specifications...............................................................................301
11.1 Mediant 3000 Selected Specifications .................................................301
12 Appendix - BootP/TFTP Server ......................................................................307
12.1 Introduction............................................................................................307
12.1.1
12.1.2
12.1.3
12.1.4
12.1.5
12.1.6
12.1.7
Key Features ......................................................................................... 307

Specifications......................................................................................... 307
BootP/TFTP Server Installation ............................................................. 308
Logging Screen...................................................................................... 310
Preferences Screen ............................................................................... 311
Client Configuration Screen................................................................... 312
Template Screen ................................................................................... 314
13 Appendix - Individual ini File Parameters .....................................................315

13.1 Individual ini File Parameters ...............................................................315
13.1.1 System Parameters ............................................................................... 316
13.1.2 Infrastructure Parameters ...................................................................... 322
13.1.3 Media Processing Parameters............................................................... 335
13.1.4 PSTN Parameters.................................................................................. 347
13.1.5 357
13.1.6 SDH/SONET Configuration ................................................................... 357
13.1.7 SS7 Parameters .................................................................................... 362
13.1.8 Parameters Common to All Control Protocols ....................................... 364
13.1.9 MGCP-Specific Parameters................................................................... 371
13.1.10 MEGACO-Specific Parameters ............................................................. 375
13.1.11 Web Interface Parameters..................................................................... 379
13.1.12 SNMP Parameters................................................................................. 382
13.1.13 Voice Streaming Parameters................................................................. 383
13.1.14 SCTP Parameters.................................................................................. 384
13.1.15 VoATM Parameters ............................................................................... 386
User's Manual
User's Manual
Contents
14 Appendix - Table Parameters.........................................................................387

14.1 ini File Table Parameters ......................................................................387
14.1.1
14.1.2
14.1.3
14.1.4
14.1.5
SS7 ini File Table Parameters ............................................................... 387

ATM Port Table PARAMS ..................................................................... 399
NFS Servers Table ................................................................................ 405
T3 Configuration Table Parameters....................................................... 406
Example of T3 INI file Selection :........................................................... 407
15 Appendix - Auxiliary Files ..............................................................................409

15.1 Call Progress Tone and User-Defined Tone Auxiliary Files...............409
15.1.2 Modifying the Call Progress Tones File ................................................. 415
15.1.3 Converting a Modified CPT ini File to a dat File with the Download
Conversion Utility ................................................................................. 416
15.2 Playing the Prerecorded Tones (PRT) Auxiliary File ..........................416

15.3 Coder Table File.....................................................................................418
15.3.2 Converting a Modified CoderTable ini File to a dat File Using DConvert
Utility..................................................................................................... 419
15.3.3 Default Coder Table (Tbl) ini file ............................................................ 419
16 Appendix - RTP/RTCP Payload Types...........................................................421

16.1
16.2
16.3
16.4
Payload Types Defined in RFC 3551....................................................421

Payload Types Not Defined in RFC 3551 .............................................422
Default Dynamic Payload Types Which are Not Voice Coders..........423
Default RTP/RTCP/T.38 Port Allocation ...............................................423
17 Appendix - DTMF, Fax & Modem Transport Modes......................................425

17.1
17.2
17.3
17.4
17.5
17.6
DTMF/MF Relay Settings.......................................................................425

Fax/Modem Settings..............................................................................425
Configuring Fax Relay Mode ................................................................425
Configuring Fax/Modem ByPass Mode ...............................................426
Configuring Fax/Modem Bypass NSE mode .......................................426
Supporting V.34 Faxes ..........................................................................427
17.6.1 Using Bypass Mechanism for V.34 Fax Transmission .......................... 427
17.6.2 Using Events Only Mechanism for V.34 Fax Transmission................... 427
17.6.3 Using Relay Mode for Various Fax Machines (T.30 and V.34).............. 428
18 Appendix - CAS Protocol Table .....................................................................429

18.1 Constructing a CAS Protocol Table.....................................................429
18.2 Table Elements ......................................................................................429
18.2.1
18.2.2
18.2.3
18.2.4
Version 4.8
INIT variables......................................................................................... 429

Actions ................................................................................................... 429
Functions ............................................................................................... 430
States..................................................................................................... 430
December 2005
Mediant 3000
18.3
18.4
18.5
18.6
18.7
18.8
18.9
Reserved Words ....................................................................................432

States Line Structure ...........................................................................432
Action/Event...........................................................................................432
Function .................................................................................................435
Parameters .............................................................................................435
Next State ...............................................................................................437
Changing the Script File .......................................................................437
18.9.1 General .................................................................................................. 437
18.9.2 MFC R2 protocol.................................................................................... 438
19 Appendix - CAS to Analog Mapping Protocol ..............................................441

19.1 ini File Configuration.............................................................................444
19.2 MELCAS Call Flow Examples ...............................................................444
19.2.1
19.2.2
19.2.3
19.2.4
19.2.5
Establishing a Normal Call..................................................................... 444

Disconnect Process ............................................................................... 445
Re-Answer Scenario.............................................................................. 447
Flash Hook Detection ............................................................................ 448
Blocking and Unblocking Process ......................................................... 449
19.3 Pulse Dial Detection ..............................................................................449

19.4 ini File Configuration.............................................................................449
19.5 CAS Table Configuration ......................................................................449
20 Appendix - Security.........................................................................................451
20.1 IPSec and IKE ........................................................................................451
20.1.1 IKE ......................................................................................................... 452
20.1.2 IPSec ..................................................................................................... 453
20.1.3 Configuring IPSec and IKE .................................................................... 453
20.2 SSL/TLS..................................................................................................461
20.2.1
20.2.2
20.2.3
20.2.4
20.2.5
Web Server Configuration ..................................................................... 461

Using the Secure Web Server ............................................................... 462
Secure Telnet ........................................................................................ 462
Server Certificate Replacement............................................................. 462
Client Certificates................................................................................... 464
20.3 RADIUS Support ....................................................................................464

20.3.1 Setting Up a RADIUS Server................................................................. 465
20.3.2 Configuring RADIUS Support ................................................................ 466
20.4 Internal Firewall .....................................................................................468

20.4.1 Internal Firewal ...................................................................................... 469
20.5 Network Port Usage ..............................................................................471

20.6 Media Security .......................................................................................472
20.6.1 Packet Cable Security ........................................................................... 472
20.6.2 Secured RTP ......................................................................................... 473
User's Manual
User's Manual
Contents
20.7 Recommended Practices ......................................................................473

20.8 Legal Notice ...........................................................................................474
21 Appendix - SS7 Configuration Guide ............................................................475
21.1 SS7 Network Elements..........................................................................475
21.1.1
21.1.2
21.1.3
21.1.4
21.1.5
21.1.6
SS7 M2UA - SG Side ............................................................................ 475

SS7 M2UA Media Gateway Controller Side ....................................... 476
SS7 MTP3 Node.................................................................................... 476
SS7 MTP2 Tunneling............................................................................. 477
Configuration Extensions:...................................................................... 477
Other dependencies in ini File: .............................................................. 477
21.2 Examples of SS7 ini Files .....................................................................478

21.2.1
21.2.2
21.2.3
21.2.4
SS7 M2UA - SG Side ini File Example .................................................. 478

SS7 M2UA - Media Gateway Controller Side ini File Example.............. 479
SS7 MTP3 Node ini File Example ......................................................... 483
SS7 MTP2 Tunneling ini File Example .................................................. 487
21.3 SS7 Tunneling: Feature Description....................................................491

21.3.1 MTP2 Tunneling Technology................................................................. 493
21.3.2 IUA /DUA Behind NAT Support ............................................................. 493
21.3.3 SS7 Characteristics ............................................................................... 494
22 Appendix - Utilities..........................................................................................495
22.1 API Demonstration Utilities ..................................................................495
22.2 TrunkPack Downloadable Conversion Utility .....................................495
22.2.1
22.2.2
22.2.3
22.2.4
22.2.5
Process Call Progress Tones file(s) ...................................................... 497

Process Voice Prompts file(s)................................................................ 498
Process CAS Tables.............................................................................. 501
Process Prerecorded Tones File(s) ....................................................... 503
Process Encoded/Decoded ini File(s).................................................... 505
22.3 PSTN Trace Utilities ..............................................................................506

22.4 Enabling PSTN Trace via the Web .......................................................507
23 Appendix - MGCP Compliance.......................................................................509
23.1 MGCP Compliance Matrix .....................................................................509
24 Appendix - MEGACO Compliance .................................................................525
24.1 MEGACO Compliance Matrix................................................................525
25 Advanced Announcement Packages - Compliance Tables (MEGACO &
MGCP) ............................................................................................................537
25.1 H.248.9 Compliance Matrix ...................................................................537
25.1.1
25.1.2
25.1.3
25.1.4
Advanced Audio Server Base Package (aasb)...................................... 537

AAS Digit Collection Package (aasdc) Extends Aasb Package ............ 538
AAS Digit Collection Package (aasrec) Extends aasb Package............ 540
Adanced Audio Server Segment Management Package (aassm) ........ 541
25.2 H.248.9 Compliance Matrix - TD-51 (Early Draft).................................542

25.2.1 Advanced Audio Server Base Package (aasb) (Early Draft) ................. 542
25.2.2 Advanced Audio Server Set Package (aass)......................................... 545
Version 4.8
December 2005
Mediant 3000
25.2.3 Advanced Audio Server Override Package (aas0) ................................ 545

25.2.4 Segment Description Matrix................................................................... 545
25.3 PacketCable Audio Server Protocol Specification PKT-SP-ASP-I02010620 ANN-2 Interface ........................................................................547
25.3.1 Base Audio Package ............................................................................. 547
25.3.2 Advanced Audio Package...................................................................... 551
26 Appendix - Getting Started with VLANs and Multiple IPs............................553

26.1.1 Integrating Using the Embedded Web Server ....................................... 553
26.1.2 Integrating Using the ini File .................................................................. 555
26.2
26.3
26.4
26.5
Basic Setup ............................................................................................556

Setup Example.......................................................................................556
Preparing the Mediant 3000 for VLANs and Multiple IPs (MI) ............557
Verifying the VLANS and Multiple IP Settings Using the Embedded
Web Server ............................................................................................559
26.6 OAM Parameters....................................................................................561
26.7 MI and VLAN Parameters ......................................................................561
27 VoATM Related SDP Exchange Samples & Call Flows................................565

27.1 Sample SDP Exchanges .......................................................................565
27.2 for VoATM ..............................................................................................565
27.2.1 AAL1 ...................................................................................................... 565
27.2.2 AAL2 ...................................................................................................... 566
27.3 Call Flows...............................................................................................567

27.3.1 Simple Announcement Call Over AAL1 SVC ........................................ 568
27.3.2 Simple Announcement Call Over AAL2 SVC ........................................ 570
28 Appendix - SNMP Traps..................................................................................571

28.1 Alarm Traps............................................................................................571
28.1.1
28.1.2
28.1.3
28.1.4
28.1.5
28.1.6
Component: Board#<n> ........................................................................ 571

Component: Board#<n> ........................................................................ 574
Component: SS7#0 ............................................................................... 578
Component: Chassis#0 ......................................................................... 583
Component: System#0/Module#<m> .................................................... 586
Component: Interfaces#0/Sonet#<m>................................................... 591
28.2 Log Traps (Notifications) ......................................................................594

28.3 Other Traps ............................................................................................595
28.4 Trap Varbinds ........................................................................................596
29 Appendix - Customizing the Web Interface ..................................................599
29.1 Company & Product Bar Components ................................................599
29.2 Replacing the Main Corporate Logo ....................................................600
29.2.1 Replacing the Main Corporate Logo with an Image File........................ 600
29.2.2 Replacing the Main Corporate Logo with a Text String ......................... 602
User's Manual
10
User's Manual
Contents
29.3 Replacing the Background Image File.................................................602

29.4 Customizing the Product Name ...........................................................603
29.4.1 Customizing the Web Browser Title Bar ................................................ 604
29.5 Modifying ini File Parameters via the AdminPage..............................604

30 Appendix - Regulatory Information ...............................................................607
31 List of Abbreviations.......................................................................................611
32 Index.................................................................................................................617
Version 4.8
11
December 2005
User's Manual
Contents
List of Figures
Figure 1-1: 3000 System HA 1+1 Architecture.......................................................................................26
Figure 1-2: 6310 Functional Block Diagram ...........................................................................................27
Figure 2-1: 3000 Front View (High Availability Mode)............................................................................30
Figure 2-2: 6310 Board...........................................................................................................................32
Figure 2-3: 6310/RTM/HA/STM1-OC3 ...................................................................................................33
Figure 2-4: T3-RTM ................................................................................................................................33
Figure 2-5: 6310 Board: STM1 Panel.....................................................................................................34
Figure 2-6: 6310 Board: T3 Panel ..........................................................................................................35
Figure 2-7: 6310/RTM/ STM1-OC3 Board .............................................................................................43
Figure 2-8: TP-6310/T3 Board ...............................................................................................................44
Figure 2-9: 6310/RTM/Redundant..........................................................................................................46
Figure 2-10: SA-3 Board - Basic Configuration with Alarm & Status Only.............................................48
Figure 2-11: SA-3 Board - Alarm, Status and Stratum 3 Synchronization .............................................48
Figure 2-12: SA/M3K Alarm Board.........................................................................................................49
Figure 2-13: PEM/DC/3K Module...........................................................................................................52
Figure 2-14: PS/DC/M3K Power Supply ................................................................................................53
Figure 2-15: Fan Tray and Alarm Indicators...........................................................................................54
Figure 3-1: 3000 Chassis - Front Details - High Availablity System.......................................................58
Figure 3-2: 3000 Chassis- Rear Details - High Availablity System ........................................................60
Figure 3-3: Two types of SFP Modules and Their Locks .......................................................................63
Figure 3-4: Redundancy Connection Scheme for the 6310 RTM ..........................................................64
Figure 3-5: TP-6310/T3 Connection Diagram ........................................................................................65
Figure 3-6: RJ-45 LAN/Ethernet Network Port and Connector ..............................................................66
Figure 3-7: Normal Logic Alarm Connection Diagram ...........................................................................68
Figure 3-8: DC Power and Alarm Connectors........................................................................................69
Figure 3-9: Blank Panel for Rear Slots...................................................................................................70
Figure 3-10: Fan Tray Unit .....................................................................................................................74
Figure 3-11: Air Filter Insertion Position Indicators ................................................................................75
Figure 3-12: Removing the Air Filter ......................................................................................................75
Figure 6-1: Startup Process Diagram.....................................................................................................85
Figure 7-1: MEGACO-R2 Call Disconnect Flow Diagram................................................................... 141
Figure 8-1: SVC (AAL2) Access to VoATM Media Server .................................................................. 179
Figure 8-2: Looped Virtual Path between VoATM Media Server and Edge Switch ............................ 181
Figure 9-1: Enter Network Password Screen ...................................................................................... 207
Figure 9-2: Web Interface Screen - Example ...................................................................................... 208
Figure 9-3: Quick Setup Screen .......................................................................................................... 210
Figure 9-4: Protocol Management Screen .......................................................................................... 212
Figure 9-5: Basic Configuration Screen (MGCP) ................................................................................ 213
Figure 9-6: Basic Configuration Screen (MEGACO)........................................................................... 213
Figure 9-7: General Parameters Screen (MGCP) ............................................................................... 215
Figure 9-8: General Parameters Screen (MEGACO).......................................................................... 216
Figure 9-9: Channel Configuration Screen (MGCP) ........................................................................... 217
Figure 9-10: Channel Configuration Screen (MEGACO) .................................................................... 217
Figure 9-11: Advanced Configuration Screen (MGCP)....................................................................... 218
Figure 9-12: Advanced Configuration Screen (MEGACO).................................................................. 218
Figure 9-13: Advanced Configuration Parameters Screen ................................................................. 219
Figure 9-14: Network Settings Drop-Down Menu ............................................................................... 219
Figure 9-15: Media Settings Drop-Down Menu ................................................................................... 220
Figure 9-16: SS7 Settings Drop-Down Menu ...................................................................................... 220
Figure 9-17: IP Settings Screen .......................................................................................................... 221
Figure 9-18: Application Settings Screen ............................................................................................ 222
Figure 9-19: NFS Settings Table Screen ............................................................................................ 223
Figure 9-20: Routing Table Screen ..................................................................................................... 224
Figure 9-21: VLAN Settings Screen .................................................................................................... 225
Figure 9-22: Voice Settings Screen..................................................................................................... 226
Figure 9-23: Fax/Modem/CID Settings Screen ................................................................................... 226
Version 4.8
13
December 2005
Mediant 3000
Figure 9-24: RTP Settings Screen (Network Settings)........................................................................ 227
Figure 9-25: IPmedia Settings Screen ................................................................................................ 228
Figure 9-26: General Settings Screen................................................................................................. 228
Figure 9-27: DS3 Settings Screen....................................................................................................... 229
Figure 9-28: TP-6310/T3 Burn Configuration Screen ......................................................................... 230
Figure 9-29: TP-6310 T3 Restart Screen ........................................................................................... 230
Figure 9-30: Trunk Settings Screen .................................................................................................... 231
Figure 9-31: Q931 Bit Map Screen...................................................................................................... 233
Figure 9-32: MTP2 Attributes Screen.................................................................................................. 234
Figure 9-33: SS7 Signaling Node Timers Screen ............................................................................... 235
Figure 9-34: SS7 Link Set Timers Screen........................................................................................... 236
Figure 9-35: SS7 Links Screen ........................................................................................................... 237
Figure 9-36: SS7 Signaling Nodes Screen.......................................................................................... 238
Figure 9-37: SS7 SN Link Sets Screen ............................................................................................... 239
Figure 9-38: SS7 SN Routes Screen .................................................................................................. 239
Figure 9-39: SS7 SigTran Group IDs Screen...................................................................................... 240
Figure 9-40: SS7 SigTran Interface IDs Screen.................................................................................. 241
Figure 9-41: TDM Bus Settings Screen............................................................................................... 241
Figure 9-42: Configuration File Screen ............................................................................................... 243
Figure 9-43: Regional Settings Screen - Sending CPT, CAS and/or Voice Prompt File to the Device244
Figure 9-44: Web User Accounts Screen - Security Administrator Level ........................................... 246
Figure 9-45: Enter Network Password Dialog ..................................................................................... 246
Figure 9-46: Web User Accounts Screen - For Users with Privileges Lower than Security Administrator247
Figure 9-47: Web & Telnet Access List Screen................................................................................... 248
Figure 9-48: Firewall Settings Screen ................................................................................................. 249
Figure 9-49: Certificate Sighing Request Screen................................................................................ 250
Figure 9-50: Certificate Signing Request ............................................................................................ 251
Figure 9-51: General Security Settings Screen................................................................................... 252
Figure 9-52: IPSec Table Screen (Existing Table Row)...................................................................... 253
Figure 9-53: IPSec Table Screen (Non -Existing Table Row)............................................................. 253
Figure 9-54: IKE Table Screen (Existing Table Row) ......................................................................... 255
Figure 9-55: IKE Table Screen (Non -Existing Table Row)................................................................. 255
Figure 9-56: Management Settings Screen......................................................................................... 257
Figure 9-57: SNMP Managers Table Screen ..................................................................................... 258
Figure 9-58: SNMP Community String Screen.................................................................................... 259
Figure 9-59: Status and Diagnostic Menu Screen .............................................................................. 260
Figure 9-60: Trunk and Channel Status Screen.................................................................................. 261
Figure 9-61: Basic Information Screen................................................................................................ 262
Figure 9-62: RTP/RTCP Information Screen....................................................................................... 263
Figure 9-63: Voice Information Screen................................................................................................ 263
Figure 9-64: Message Log Screen ...................................................................................................... 264
Figure 9-65: Versions Screen.............................................................................................................. 265
Figure 9-66: Start Software Upgrade Screen ...................................................................................... 266
Figure 9-67: Start Software Upgrade Screen ...................................................................................... 267
Figure 9-68: Load CMP File Dialog Screen......................................................................................... 268
Figure 9-69: File Loading Dialog Screen............................................................................................. 269
Figure 9-70: File Loading Dialog Screen - CPT Type Displayed ........................................................ 270
Figure 9-71: File Loading Dialog Screen - Reset Button Stage .......................................................... 271
Figure 9-72: End of Process Dialog Screen ........................................................................................ 271
Figure 9-73: Auxiliary Files Download Screen .................................................................................... 272
Figure 9-74: Software Upgrade Key Screen ....................................................................................... 275
Figure 9-75: Example of a Software Upgrade Key File Containing Multiple S/N Lines ...................... 275
Figure 9-76: Save Configuration Dialog Screen.................................................................................. 277
Figure 9-77: Reset Screen .................................................................................................................. 277
Figure 10-1: Syslog Server Main Settings Screen .............................................................................. 281
Figure 10-2: Setting the Syslog Server IP Address............................................................................. 282
Figure 12-1: Main Screen .................................................................................................................... 309
Figure 12-2: Preferences Screen ........................................................................................................ 311
User's Manual
14
User's Manual
Contents
Figure 12-3: Client Configuration Screen ............................................................................................ 312

Figure 12-4: Templates Screen........................................................................................................... 314
Figure 19-1: CAS to Analog Mapping Protocol ................................................................................... 441
Figure 19-2: Establishing Normal Call - PSTN Originate .................................................................... 444
Figure 19-3: Establishing Normal Call - PSTN Terminate................................................................... 445
Figure 19-4: Disconnect Process - TE Clear the Call ......................................................................... 446
Figure 19-5: Disconnect Process - PSTN Explicit Disconnect Signal................................................. 446
Figure 19-6: Release Call Without Explicit Disconnect Signal ............................................................ 447
Figure 19-7: Re-answer Scenario - PSTN Originate........................................................................... 447
Figure 19-8: Re-answer Scenarion - PSTN Terminate ....................................................................... 448
Figure 19-9: Flash Hook Detection...................................................................................................... 448
Figure 19-10: Blocking and Unblocking Process ................................................................................ 449
Figure 20-1: IPSec Encryption ............................................................................................................ 452
Figure 20-2: IKE Table Screen............................................................................................................ 456
Figure 20-3: IPSec Table Screen ........................................................................................................ 460
Figure 21-1: SS7 M2UA - SG Side...................................................................................................... 475
Figure 21-2: SS7 M2UA - MGC Side .................................................................................................. 476
Figure 21-3: SS7 MTP3 Node ............................................................................................................. 476
Figure 21-4: SS7 MTP2 Tunneling...................................................................................................... 477
Figure 21-5: M2UA Architecture.......................................................................................................... 492
Figure 21-6: M2TN Architecture .......................................................................................................... 492
Figure 21-7: Protocol Architecture for MTP2 Tunneling...................................................................... 493
Figure 22-1: TrunkPack Downloadable Conversion Utility R2.5.2 ...................................................... 496
Figure 22-2: Call Progress Tones Screen ........................................................................................... 497
Figure 22-3: Voice Prompts Screen .................................................................................................... 498
Figure 22-4: Select Files Window........................................................................................................ 499
Figure 22-5: Voice Prompts Window with wav Files ........................................................................... 500
Figure 22-6: File Data Window............................................................................................................ 500
Figure 22-7: Call Associated Signaling (CAS) Screen ........................................................................ 502
Figure 22-8: Prerecorded Tones File(s) Screen.................................................................................. 503
Figure 22-9: Prerecorded Tones File(s) Screen with wav Files .......................................................... 504
Figure 22-10: File Data Dialog Box ..................................................................................................... 504
Figure 22-11: Encoded ini File(s) Screen............................................................................................ 505
Figure 22-12: Trunk Traces Screen .................................................................................................... 508
Figure 22-13: UDP2File Utility Dialog Box .......................................................................................... 508
Figure 26-1: VLAN Settings Screen Example ..................................................................................... 554
Figure 26-2: IP Settings Screen Example ........................................................................................... 554
Figure 26-3: IP Routing table Screen Example ................................................................................... 555
Figure 26-4: IP Settings Screen Example ........................................................................................... 560
Figure 26-5: Routing Table Screen ..................................................................................................... 560
Figure 26-6: VLAN Settings screen..................................................................................................... 560
Figure 27-1: Remote Gateway H.248 AAL1 SVC Call Flow - 6310 Master ........................................ 568
Figure 27-2: Remote Gateway H.248 AAL1 SVC Call Flow - 6310 Slave .......................................... 569
Figure 27-3: Remote Gateway H.248 AAL2 SVC Call Flow ............................................................... 570
Figure 29-1: Web Interface Title Bar ................................................................................................... 599
Figure 29-2: Customized Web Interface Title Bar ............................................................................... 599
Figure 29-3: Logo Image Download Screen........................................................................................ 600
Figure 29-4: Default Web Browser Title Bar........................................................................................ 604
Figure 29-5: ini Parameters Screen .................................................................................................... 605
Version 4.8
15
December 2005
Mediant 3000
List of Tables
Table 2-1: Chassis Dimensions..............................................................................................................30
Table 2-2: TP-6310 Board: STM-1 Panel LED Indicators ......................................................................36
Table 2-3: TP-6310 Board: STM-1 Panel LED Alarm Signals for SDH or SONET Terminology...........38
Table 2-4: TP-6310/T3 Board Panel LED Indicators..............................................................................39
Table 2-5: TP-6310 Board: T3 Panel LED Alarm Signals ......................................................................42
Table 2-6: SA/M3K Board LED Indicators..............................................................................................49
Table 2-7: Power Requirements.............................................................................................................50
Table 2-8: PEM/DC/3K Front View Component Descriptions ................................................................52
Table 2-9: PS/DC/3K LED Indicators .....................................................................................................53
Table 2-10: Chassis Front Panel Alarm Indicators.................................................................................54
Table 3-1: Mediant 3000 FrontDetails ....................................................................................................59
Table 3-2: Mediant 3000 Rear Details....................................................................................................60
Table 3-3: RJ-45 Receptacle Pinouts.....................................................................................................66
Table 3-4: Alarm Terminal Block Pin Details..........................................................................................67
Table 4-1: Software Package Contents..................................................................................................78
Table 6-1: Command Line Switch Descriptions .....................................................................................87
Table 6-2: Vendor Specific Information Field Tags ................................................................................89
Table 6-3: Example of Vendor Specific Information Field Structure ......................................................90
Table 6-4: Table Structure Example.......................................................................................................94
Table 7-1: MGCP Fax Package Gateway Mode ................................................................................. 106
Table 7-2: Fax Transport Type ............................................................................................................ 109
Table 7-3: SRTP ABNF Parameter Description .................................................................................. 111
Table 7-4: MGCP Mapping of Payload Numbers to Coders ............................................................... 118
Table 7-5: Generic Media Package - G............................................................................................... 121
Table 7-6: DTMF Package - D ............................................................................................................ 121
Table 7-7: Line Package - L ................................................................................................................ 122
Table 7-8: Handset Emulation Package - H ........................................................................................ 123
Table 7-9: Trunk Package - T.............................................................................................................. 124
Table 7-10: PacketCable (NCS) Line Package - L.............................................................................. 124
Table 7-11: Generic Media Package - A ............................................................................................. 125
Table 7-12: RTP Package - R ............................................................................................................. 126
Table 7-13: CAS Package - MS .......................................................................................................... 127
Table 7-14: CAS Package - DT........................................................................................................... 128
Table 7-15: ISUP Trunk Package - IT ................................................................................................. 128
Table 7-16: Fax Package Definition - FXR.......................................................................................... 130
Table 7-17: V5 Package Definition...................................................................................................... 130
Table 7-18: Signal List Package Definition.......................................................................................... 131
Table 7-19: Compression Coders ....................................................................................................... 131
Table 7-20: Silence Suppression Operation........................................................................................ 143
Table 7-21: Table 32: MEGACO Mapping Payload Numbers to Coders............................................ 157
Table 7-22: Generic Media Package - G............................................................................................. 159
Table 7-23: Base Root Package - ROOT............................................................................................ 160
Table 7-24: Tone Generator Package - ToneGen .............................................................................. 160
Table 7-25: Tone Detection Package - ToneDet................................................................................. 161
Table 7-26: DTMF Generator Package - DG ...................................................................................... 161
Table 7-27: DTMF Detection Package - DD........................................................................................ 162
Table 7-28: Call Progress Tones Generator Package - CG................................................................ 162
Table 7-29: Call Progress Tones Detection Package - CD................................................................. 163
Table 7-30: Network Package - NT ..................................................................................................... 163
Table 7-31: RTP Package - RTP......................................................................................................... 164
Table 7-32: Generic Announcement Package .................................................................................... 164
Table 7-33: Expanded Call Progress Tones Generator Package - XCG............................................ 165
Table 7-34: Basic Service Tones Generation Package - SRVTN....................................................... 165
Table 7-35: Expanded Services Tones Generation Package - XSRVTN ........................................... 165
Table 7-36: Basic CAS Signal/Events ................................................................................................. 166
Table 7-37: International CAS Signal/Events ...................................................................................... 166
User's Manual
16
User's Manual
Contents
Table 7-38: CAS Blocking Signal/Events ............................................................................................ 167

Table 7-39: ICASC Signal/Events Table ............................................................................................. 167
Table 7-40: MF Generator Package - MFG......................................................................................... 167
Table 7-41: MF Generator Package - MFG......................................................................................... 168
Table 7-42: Inactivity Timer Package - IT............................................................................................ 169
Table 7-43: Basic Call Progress Tones Generator with Directionality Package - BCG ...................... 169
Table 7-44: Extended digit collection Package - XDD ....................................................................... 170
Table 7-45: Enhanced Digits Collection Package - EDD .................................................................... 170
Table 7-46: MEGACO Endpoint Names.............................................................................................. 172
Table 8-1: Related Standards ............................................................................................................. 175
Table 8-2: GIT Information Element Encoding of EECID.................................................................... 176
Table 8-3: ITU 1 Call Profile ................................................................................................................ 177
Table 8-4: ITU 2 Call Profile ................................................................................................................ 177
Table 8-5: Custom 200 Call Profile ..................................................................................................... 177
Table 8-6: SVC Traffic Profile.............................................................................................................. 179
Table 9-1: Available Access Levels and their Privileges..................................................................... 203
Table 9-2: Access Default Attributes ................................................................................................... 204
Table 9-3: Default IP Address and Subnet Mask ................................................................................ 206
Table 9-4: DS3 Settings ...................................................................................................................... 229
Table 9-5: Trunk Status Color Indicator Key ....................................................................................... 231
Table 9-6: Trunk and Channel Status Color Indicator Key.................................................................. 261
Table 10-1: Solutions to Possible Common Problems........................................................................ 286
Table 10-2: Solutions to Possible Voice Problems ............................................................................. 287
Table 10-3: User Error Messages ....................................................................................................... 288
Table 11-1: Mediant 3000 Selected Specifications ............................................................................. 301
Table 13-1: System Parameters.......................................................................................................... 316
Table 13-2: Infrastructure Parameters ................................................................................................ 323
Table 13-3: Media Processing Parameters ......................................................................................... 335
Table 13-4: PSTN Parameters ............................................................................................................ 347
Table 13-5: STM-1 Numbering Conversion Table .............................................................................. 358
Table 13-6: OC3 Numbering Conversion Table .................................................................................. 360
Table 13-7: SS7 Parameters............................................................................................................... 362
Table 13-8: Control Protocol Parameters............................................................................................ 365
Table 13-9: MGCP Specific Parameters ............................................................................................. 371
Table 13-10: MEGACO Specific Parameters ...................................................................................... 376
Table 13-11: Web Interface Parameters ............................................................................................. 379
Table 13-12: SNMP Parameters ......................................................................................................... 382
Table 13-13: Voice Streaming Parameters ......................................................................................... 384
Table 13-14: SCTP Parameters .......................................................................................................... 384
Table 13-15: VoATM Parameters........................................................................................................ 386
Table 14-1: SS7 Signaling Nodes Table Parameters ......................................................................... 387
Table 14-2: SS7 Signaling Node Timers Table Parameters ............................................................... 389
Table 14-3: SS7 Signaling LinkSet Timers Table Parameters............................................................ 391
Table 14-4: SS7 Signaling Link Table Parameters ............................................................................. 392
Table 14-5: SS7 Signaling LinkSets Table Parameters ...................................................................... 395
Table 14-6: SS7 Signaling LinkSet-Links Table Parameters .............................................................. 396
Table 14-7: SS7 RouteSets Table Parameters ................................................................................... 397
Table 14-8: SS7 RouteSet-Routes Table Parameters ........................................................................ 397
Table 14-9: SigTran Interface Groups Table Parameters ................................................................... 398
Table 14-10: SigTran Interface IDs Table Parameters ....................................................................... 399
Table 14-11: ATM Port Table Parameters .......................................................................................... 400
Table 14-12: ATM Port Loopback Table Parameters.......................................................................... 400
Table 14-13: ATM Remote Gateway Table Parameters ..................................................................... 402
Table 14-14: ATM AAL2 PVC Table Parameters................................................................................ 403
Table 14-15: ATM SVC Profile Table Parameters .............................................................................. 404
Table 14-16: NFS Servers Table Parameters ..................................................................................... 405
Table 14-17: T3 Configuration Table Parameters............................................................................... 406
Version 4.8
17
December 2005
Mediant 3000
Table 15-1: Default Call Progress Tones ............................................................................................ 413
Table 16-1: Payload Types Defined in RFC 3551............................................................................... 421
Table 16-2: Payload Types Not Defined in RFC 3551 ........................................................................ 422
Table 16-3: Dynamic Payload Types Not Defined in RFC 3551 ......................................................... 423
Table 16-4: Default RTP/RTCP/T.38 Port Allocation .......................................................................... 423
Table 17-1: V.34 Fax to V.34 Fax - Bypass Mode .............................................................................. 427
Table 17-2: V.34 Fax to V.34 Fax - Events Only Mode....................................................................... 428
Table 17-3: V.34 Fax to V.34 Fax - Relay Mode ................................................................................. 428
Table 18-1: ST_DIAL: Table Elements................................................................................................ 430
Table 18-2: CAS Parameters .............................................................................................................. 435
Table 19-1: Trunk/B-channel Mapping ................................................................................................ 442
Table 19-2: Mapping Table.................................................................................................................. 442
Table 20-1: IKE Table Configuration Parameters ............................................................................... 454
Table 20-2: Default IKE First Phase Proposals................................................................................... 455
Table 20-3: SPD Table Configuration Parameters.............................................................................. 457
Table 20-4: Default IKE Second Phase Proposals ............................................................................. 458
Table 20-5: RADIUS Authentication Settings...................................................................................... 468
Table 20-6: Internal Firewall Fields ..................................................................................................... 469
Table 20-7: Default TCP/UDP Network Port Numbers ....................................................................... 471
Table 23-1: MGCP Compliance Matrix................................................................................................ 509
Table 24-1: MEGACO Compliance Matrix .......................................................................................... 525
Table 25-1: Events (aasb) ................................................................................................................... 537
Table 25-2: Audio Operartion Failure Event Parameters (aasb)......................................................... 537
Table 25-3: Signals (aasb) .................................................................................................................. 538
Table 25-4: Play Announcement Signal Parameters (aasb) ............................................................... 538
Table 25-5: Events (aasdc) ................................................................................................................. 538
Table 25-6: Play Collect Success Event Parameters (aasdc)............................................................. 538
Table 25-7: Signals (aasdc)................................................................................................................. 539
Table 25-8: Play Collect Signal Parameters (aasdc) .......................................................................... 539
Table 25-9: Properties (aasrec)........................................................................................................... 540
Table 25-10: Events (aasrec) .............................................................................................................. 540
Table 25-11: Play Record Success Event Parameters (aasrec)......................................................... 540
Table 25-12: Signals (aasrec) ............................................................................................................. 540
Table 25-13: Play Record Signal Parameters (aasrec)....................................................................... 541
Table 25-14: Events (aasb) (Early Draft)............................................................................................. 542
Table 25-15: Audio Operation Complete Event Parameters (aasb) (Early Draft) ............................... 542
Table 25-16: Audio Operation Failure Event Parameters (aasb) (Early Draft) ................................... 542
Table 25-17: Signals (aasb) (Early Draft)............................................................................................ 543
Table 25-18: Play Announcement Signal Parameters (aasb) (Early Draft) ........................................ 543
Table 25-19: Play Collect Signal Parameters (aasb) (Early Draft)...................................................... 543
Table 25-20: Play Record Signal Parameters (aasb) (Early Draft) ..................................................... 544
Table 25-21: Supported Segment Descriptor Elements...................................................................... 545
Table 25-22: Segment Descriptor Variables ....................................................................................... 545
Table 25-23: Events ............................................................................................................................ 547
Table 25-24: PlayAnnouncement Parameters .................................................................................... 547
Table 25-25: PlayCollect Parameters.................................................................................................. 547
Table 25-26: PlayRecord Parameters ................................................................................................. 548
Table 25-27: ManageAudio Parameters ............................................................................................. 550
Table 25-28: Segment Descriptor Elements ....................................................................................... 550
Table 25-29: Variables ........................................................................................................................ 550
Table 25-30: Set Capability ................................................................................................................. 551
Table 25-31: ManageAudio Parameters ............................................................................................. 551
Table 26-1: Example of VLAN and Multiple IPs Configuration............................................................ 553
Table 26-2: Example of IP Routing Table Configuration..................................................................... 555
Table 26-3: Routing Table Rules......................................................................................................... 558
Table 26-4: Multiple IP Parameters..................................................................................................... 561
Table 26-5: VLAN Parameters ............................................................................................................ 562
Table 26-6: Shared VLAN and MI Parameters.................................................................................... 563
User's Manual
18
User's Manual
Contents
Table 28-1: acBoardFatalError Alarm Trap ......................................................................................... 571

Table 28-2: acBoardConfigurationError Alarm Trap ........................................................................... 572
Table 28-3: acBoardTemperatureAlarm Alarm Trap........................................................................... 573
Table 28-4: acBoardEvResettingBoard Alarm Trap............................................................................ 573
Table 28-5: acFeatureKeyError Alarm Trap ........................................................................................ 574
Table 28-6: acgwAdminStateChange Alarm Trap............................................................................... 574
Table 28-7: acOperationalStateChange Alarm Trap........................................................................... 575
Table 28-8: acActiveAlarmTableOverflow Alarm Trap ........................................................................ 576
Table 28-9: acAtmPortAlarm Alarm Trap ............................................................................................ 576
Table 28-10: acSS7LinkStateChangeAlarm Trap ............................................................................... 578
Table 28-11: acSS7LinkInhibitStateChangeAlarm Trap ..................................................................... 579
Table 28-12: acSS7LinkBlockStateChangeAlarm............................................................................... 580
Table 28-13: acSS7LinkCongestionStateChangeAlarmTrap.............................................................. 580
Table 28-14: acSS7LinkSetStateChangeAlarm Trap.......................................................................... 581
Table 28-15: acSS7RouteSetStateChangeAlarm Trap....................................................................... 582
Table 28-16: acSS7SNSetStateChangeAlarmTrap ............................................................................ 582
Table 28-17: acSS7RedundancyAlarm ............................................................................................... 583
Table 28-18: acFanTrayAlarm Alarm Trap.......................................................................................... 583
Table 28-19: acPowerSupplyAlarm Alarm Trap .................................................................................. 584
Table 28-20: acPEMAlarm Alarm Trap ............................................................................................... 585
Table 28-21: acSAMissingAlarm Alarm Trap ...................................................................................... 585
Table 28-22: acUserInputAlarm Alarm Trap........................................................................................ 586
Table 28-23: acHASystemFaultAlarm Alarm Trap .............................................................................. 587
Table 28-24: acHASystemConfigMismatchAlarm Alarm Trap ............................................................ 588
Table 28-25: acHASystemSwitchOverAlarm Alarm Trap.................................................................... 589
Table 28-26: acBoardTemperatureAlarm Alarm Trap......................................................................... 589
Table 28-27: acBoardEthernetLinkAlarm Alarm Trap ......................................................................... 590
Table 28-28: AcSonetSectionLOFAlarm Alarm Trap .......................................................................... 591
Table 28-29: AcSonetSectionLOSAlarm Alarm Trap .......................................................................... 592
Table 28-30: AcSonetLineAISAlarm Alarm Trap................................................................................. 592
Table 28-31: AcSonetLineRDIAlarm Alarm Trap ................................................................................ 593
Table 28-32: acKeepAlive Log Trap.................................................................................................... 594
Table 28-33: acPerformanceMonitoringThresholdCrossing Log Trap ................................................ 594
Table 28-34: acHTTPDownloadResult Log Trap ................................................................................ 595
Table 28-35: coldStart Trap................................................................................................................. 595
Table 28-36: authenticationFailure Trap ............................................................................................. 595
Table 28-37: acBoardEvBoardStarted Trap ........................................................................................ 596
Table 28-38: AcDChannelStatus Trap ................................................................................................ 596
Table 29-1: Customizable Logo ini File Parameters for the Image File .............................................. 601
Table 29-2: Customizable Logo ini File Parameters for the String Text ............................................. 602
Table 29-3: Customizable Background ini File Parameters ................................................................ 603
Table 29-4: Customizable Product Name ini File Parameters ............................................................ 604
Table 31-1: List of Abbreviations......................................................................................................... 611
Version 4.8
19
December 2005
User's Manual
Introductory Notes
Introductory Notes
Tip:
When viewing this manual on CD, Web site or on any other electronic
copy, all cross-references are hyperlinked. Click on the page or section
numbers (shown in blue) to reach the individual cross-referenced item
directly. To return back to the point from where you accessed the
cross-reference, press the alt and keys.
Notice
This Users Manual describes the installation and use of the Mediant 3000.
Information contained in this document is believed to be accurate and reliable at the time of
printing. However, due to ongoing product improvements and revisions, AudioCodes cannot
guarantee the accuracy of printed material after the Date Published nor can it accept
responsibility for errors or omissions. Updates to this document and other documents can be
viewed by registered Technical Support customers at www.audiocodes.com under Support /
Product Documentation.
2005 AudioCodes Ltd. All rights reserved.
This document is subject to change without notice.
Date Published: December 20, 2005
Date Printed: December 21, 2005
Trademarks
AC logo, Ardito, AudioCoded, AudioCodes, AudioCodes logo, IPmedia, Mediant,
MediaPack, MP-MLQ, NetCoder, Stretto, TrunkPack, VoicePacketizer and VoIPerfect,
are
trademarks
or
registered
trademarks
of
AudioCodes
Limited.
All other products or trademarks are property of their respective owners.
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be
disposed of with unsorted waste. Please contact your local recycling authority for
disposal of this product.
Customer Support
Customer technical support and service are provided by AudioCodes' Distributors,
Partners, and Resellers from whom the product was purchased. For Customer support
for products purchased directly from AudioCodes, contact support@audiocodes.com
Version 4.8
21
December 2005
Mediant 3000
Abbreviations and Terminology

Each abbreviation, unless widely used, is spelled out in full when first used. Only
industry-standard terms are used throughout this manual. Hexadecimal notation is
indicated by 0x preceding the number.
Related Documentation
The documentation package contains the following four publications available on the
AudioCodes Web site:
User's Manual
Mediant 3000 User's Manual (this manual) - contains the boards' physical
description, installation instructions, standard control protocols and management
protocols description and general features of the board which are not control
protocol specific (for example various networking issues).
VoPLib API Reference Manual, Document # LTRT-840xx - intended for users,

who wish to control the board via the AudioCodes VoPLib API (over PCI or
TPNCP). This manual is a documentation browser in HTML or CHM formats
(created from the VoPLib documented source files). It provides detailed
descriptions of the VoPLib functions, events, structures, enumerators and error
codes. The Reference Library is an essential reference for developers,
containing extended documentation, information and examples of the VoPLib.
VoPLib Application Developers Manual, Document # LTRT-844xx

describes AudioCodes proprietary TrunkPack Control Protocol (TPNCP) based
on AudioCodes API. The manual details how TPNCP provides control of the
boards enabling Users to easily develop their applications without having to
implement complex, standard control protocols.
Mediant 3000 Release Notes, Document # LTRT-617xx - contains the various

new features and known constraints of the software version.
22
User's Manual
1. Overview of the Mediant 3000
Overview of the Mediant 3000

The Mediant 3000 is a VoIP gateway, offering integrated voice gateway functionality
capable of delivering up to 2016 simultaneous calls, the Mediant 3000 supports all
necessary functions for voice and fax streaming over IP networks.
Supporting up to 480/2016 voice channels with STM-1/OC-3 PSTN interfaces, the
Mediant 3000 addresses mid-density applications deployed in IP, ATM or mixed
IP/ATM networks. The Mediant 3000 supports a wide variety of VoIP and cellular
vocoders, standards-compliant signaling and call control and is based on AudioCodes'
VoIPerfect architecture core technology.
The Mediant 3000 can work in two system modes:
Non-High Availability mode (only one pair of TP-6310 VoP communication board
and SA/M3K Synchronization and Alarm board).
High Availability 1+1 mode (two pairs of TP-6310 VoP communication boards and
SA/M3K Synchronization and Alarm boards, one is active and the other is in
standby mode).
For High Availability, the Mediant 3000's hardware design contains redundant
modules for every part in the system, including redundant network connectivity,
comprehensive switchover processing and backup data storage and access, as well
as applicable load-sharing schemes.
To acheive high-availability, the software itself resides on redundant components and
monitors system components to detect a hardware failure, as well as handling the
switchover procedures to overcome a possible failure. In addition, components are
hot-swappableso that they can be replaced while the system is fully operational with
no disruption to service.
The Mediant 3000 contains:
up to two TP-6310 VoP communication boards
a 6310/RTM/HA/STM1-OC3 Rear Transition Module and a

6310/RTM/HA/Redundant Rear Transition Module together in 1+1 system
configuration
up to two SA/M3K Synchronization and Alarm boards
two Power Entry Modules (PEM/DC/3K)
two Power Supplies (PS/DC/3K)
These components function in either an Active / Standby redundant or load-sharing

configuration to provide full continuous performance coverage and are ideal building
blocks for deploying high-density, high availability Voice over Packet systems.
(For more details on the high availability 1+1 system, refer to 'The High Availability
1+1 System' on page 25.
Note: These features are to be implemented fully in the next applicable release.
Version 4.8
23
December 2005
Mediant 3000
The Mediant 3000 technology includes Asynchronous Transfer Mode (ATM) network
connectivity, which supports either the ATM Adaptation Layer - 1 (AAL1) or ATM
Adaptation Layer - 2 (AAL2) protocols used in support of bearer network traffic.
For a detailed overview of the VoATM capabilites, refer to ''VoATM Related SDP
Exchange Samples & Call Flows'' on page 565.
The Mediant 3000 supports a broad selection of voice processing related algorithms,
including G.711, G.723.1, G.729A and multiple UMTS,GSM and CDMA Vocoders,
G.168-2000 compliant echo cancellation, T.38 real-time Fax over IP, a wide selection
of In-band and Out-of-band tone detection and generation, as well as signaling
protocol support including ISDN PRI and SigTran (M2UA, M3UA, IUA).
The Mediant 3000 incorporates 1+1 PSTN connections, either directly to OC-3/STM-1
PSTN telephony interfaces or to an enterprise PBX, 1+1 ATM connections, two GbE
(Gigabit Ethernet) ports for connection to the LAN in non-high availability system and
four GbE ports in 1+1 system.
This manual describes the following elements of the Mediant 3000:
Hardware equipment components and hardware installation
Software package, Configuration Files and Software Initialization & installation
Standard Control Protocols support
Management Protocol support
VoATM support
Mediant 3000 Management
Diagnostics & Troubleshooting
Various appendices provide additional information.
1.1
General Features
The Mediant 3000 has the following features:
Up to 2016 voice/fax/data independent multiple LBR channels
1+1 OC3c/STM-1 Integrated Automatic Protection Switching (APS) for PSTN

interface
1+1 OC3c ATM APS protected interfaces
Packet interface: Dual GbE link ports (for redundancy)
Vocoder configuration options:
User's Manual
G.711, G.726, G.727, G.723, G.729, G.729E, AMR, GSM-FR, EVRC, GSMEFR & iLBC
Redundant Active /Standby configuration
Load-sharing power supply configuration with separate power sources
Independent vocoder selection per channel
Extensive media processing functions
3-way calling feature
RTP stream multiple destination connection

24
User's Manual
1.2
Packet telephony standard compliant
Open architecture
Flexible deployment and multiple density options
Carrier Grade Alarm System
NEBS Level 3 compliant
Superior, high quality VoATM transmissions
Superior, high quality VoIP calls and FoIP transmissions
VoIP packet streaming (RTP/ RTCP) per RFC 3550/2551
Call Control: TPNCP (proprietary TrunkPack Network Call Control Protocol),

MGCP (RFC 3435), MEGACO (H.248) standard control protocols and TGCP
Real-time Fax over IP/T.38 with superior performance (round trip delay of up to 9
sec)
Integrated Automatic Protection Switching (APS) STM-1/OC-3 for ATM interface
TDM- Switching for transferring TDM streams between timeslots
Signaling: Transparent SS7, IUA, M2UA, M3UA (without point code sharing)
IP to IP Mediation capabilities
IP to IP Transcoding (G.711 to and from LBR, to GSM Vocoders, to UMTS

vocoders and to CDMA vocoders)
Tone detection and generation (MF, DTMF, RFC 2833)
G.168-2000 compliant Echo Cancelation with a 32, 64 or 128 msec tail
Silence Suppression supporting VAD (Voice Activity Detection) and CNG

(Comfort Noise Generation)
Automatic Fax Bypass modes
DTMF Detection and Generation according to TIA 464B
DTMF Relay according RFC 2833
PSTN Signaling: CAS, ISDN PRI (To be implemented in the next applicable
release)
Transport of SS7 signaling, with the use of SigTran. MTP-3 and higher layer
messages are relayed using M2UA, M3UA over SCTP over IP
MF-R1, MFC-R2 and Call Progress Tone detection and generation
API control via IP
Management Interfaces: SNMP V2, Embedded Web Server, EMS (Optional)
High Availability
The system includes two TP-6310 boards. One of the TP-6310 boards is the active
(working) board and the other TP-6310 board is the redundant (standby) board.
Version 4.8
25
December 2005
Mediant 3000
The figure below illustrates the general architecture of the Mediant 3000 with 1+1 High
Availability.
Figure 1-1: 3000 System HA 1+1 Architecture
SDH, ATM 2xGbE
Rear
side
Lower
side
Front
side
2xGbE
RTM with full

interfaces
RTM with
ETH
interfaces
Slot1
Slot2
Slot3
TP6310
Active board
SA
Active card
TP6310
Redundant
board
Upper
side
Slot4
SA
Redundant
card
Internal Network connection
If both TP-6310 boards are installed at the time the system is powered up, the TP6310 board in Slot 1 always initially assumes the Active functionality and the TP-6310
board in Slot 3 always initially assumes the Redundant functionality. If only one board
is installed, (no matter what slot it is occupying) it always assumes the Active
functionality. If at a later time, a second TP-6310 board is added, this second TP-6310
board assumes the redundant functionality.
There is one internal Ethernet (ETH) link between the Active and Redundant boards,
which is used for the management of the high availability feature. This link is
automatically and internally configured and is used by both of the boards.
Slots 2 and 4 in the front are occupied with the SA/M3K boards. One SA/M3K board
assumes the Active functionality, while the other SA/M3K board assumes the
Redundant functionality, according to each board state.
On the rear of the chassis, a 6310/RTM/HA/STM1-OC3 is located in slot number 2. Its
ATM and PSTN connections and ETH interface are always connected to the Active
TP-6310 board in the front in slot 1. The 6310/RTM/HA/Redundant is located in slot 3
and supplies the ETH interfaces to the TP-6310 board in the front in slot 3.
Two ETH links can be connected to each board through each 6310/RTM. At least one
link per board must be connected, but two are recommended for LAN redundancy.
After system initialization is complete, network access is available only to the Active
board. The Redundant ETH links have no network access.
Each board has its own local IP address (the one that it received by BootP/DHCP)
used for loading the software by TFTP. The system has a global IP address used by
the active board at run time.
For SNMP details related the high availability refer to the 'Using SNMP' on page 183
and 'Appendix SNMP Alarm Traps' on page 571.
User's Manual
26
User's Manual
1.3
Functional Block Diagram

The figure below illustrates the functionality of the TP-6310 board.
Figure 1-2: 6310 Functional Block Diagram
H.110 Bus
Interface
H.100 Bus
H.110 TSI
PCM Highway
PCM Highway
Framers
Time Slot
Assigner
MPC8260
Parallel
Bus
PCM Highway
PSTN
STM-1 / OC-3
Transceiver
F/O
SDRAM
HPI
Up to
21 AC491
DSPs on
Module
0 to 8
AC491
DSPs on
Baseboard
MPC8260
Parallel
Bus
Flash
CPU
Controller
MPC8280
Utopia Bus
Utopia
Bridge
Utopia Bus
P
C
I
PCI
Controller
PCI Bus
Network
Processor
C-5e
SDRAM
SRAM
next applicable release
Cu
Ethernet
Phy
RJ-45 Copper
10/100/1000
or Optical GbE
6 ATM
Transceivers
Version 4.8
27
F/O
F/O
December 2005
Mediant 3000
User's Manual
28
User's Manual
2. Mediant 3000 Hardware Equipment
Mediant 3000 Hardware Equipment

This section describes the hardware equipment of the Mediant 3000.
Included are:
2.1
One 19 Chassis 2U high
Up to 2 TP-6310 I/O boards
One 6310/RTM/HA/STM1-OC3 (Rear Transition Module)
One 6310/RTM/HA/Redundant (Rear Transition Module for High Availability

systems only)
Up to 2 SA/M3K Synchronization and Alarm boards
2 PEM/DC/3K Power Entry Modules
2 PS/DC/3K Power Supplies
One FM/M3K Fan Tray
One AF/M3K Air Filter
The Mediant 3000 Chassis

The Mediant 3000 Media Gateway is comprised of a compact, rugged 19-inch rack
mount unit, 2U high (3.5" or 89 mm), with 4 front and rear slots. The chassis contains
two -48 VDC power supplies. The Mediant 3000 is populated by up to two TP-6310
compactPCI boards, one 6310/RTM/HA/STM1-OC3 on which both ATM and PSTN
interface connections and two ETH interface connections are located, one
6310/RTM/HA/Redundant with two ETH interface connections in 1+1 system, and up
to two SA/M3K Synchronization and Alarm boards.
Version 4.8
The Mediant 3000 chassis' front cage, slot #2 and #4 house the SA/M3K boards.
The Mediant 3000 chassis' front cage, slot #1 and #3 house the TP-6310 boards.
The Mediant 3000 chassis' rear cage, slot #2 houses the 6310/RTM/HA/STM1OC3 and, in High Availability 1+1 systems, #3 houses the
6310/RTM/HA/Redundant. All other Rear slots are covers with protective blank
panels.
The Mediant 3000 chassis houses the fan tray on the front-left side. It includes an
air filter.
The Mediant 3000 chassis houses the two power supplies on the front-right side.
The Mediant 3000 chassis houses the two power entry modules on the rear-left
side.
29
January 2006
Mediant 3000
The figure below shows the front view of the Mediant 3000 chassis.
Figure 2-1: 3000 Front View (High Availability Mode)
2.1.1
Mediant 3000 Chassis

The Mediant 3000 Media Gateway chassis is designed to meet NEBS level 3
requirements. It contains a 4-slot card cage. Boards are inserted from the front and
the back and engage the midplane on either side inside the card cage. A diagram
indicating the numbers of the slots and Power Supplies is located on the Fan Tray
panel. The midplane contains slot keys (located in the middle of the midplane) to
match the appropriate board. This prevents insertion of a board in an improper
location. The chassis included an ID Prom component to clearly define the hardware
version. The chassis also includes a DIP switch to configure the shelf geographical
addressing.
The chassis also houses a fan tray unit and air filters to the left of the card cage and
two Power Supply modules to the right of the card cage.
Note: While the slot keys on the midplane are designed to prevent the insertion of
a board in an incorrect location, be sure not to force a board into a slot to
avoid damaging either the board or the midplane.While the slot keys on the
midplane are designed to prevent the insertion of a board in an incorrect
location, be sure not to force a board into a slot to avoid damaging either the
board or the midplane.
Table 2-1: Chassis Dimensions

Dimension
Value
Width
48.3 cm (19 inches)
Height
2U or 8.9 cm (3.5 inches)
Depth
29.68 cm (11.69 inch)
Weight (Fully loaded)
13 kg (29 lb)
User's Manual
30
User's Manual
Table 2-1: Chassis Dimensions

Dimension
Value
Weight (Fully loaded in packaging)
Approx. 16 kg (35.5 lb)
2.2
The Mediant 3000 Boards

The boards included in the Mediant 3000 are:
Up to 2 TP-6310 I/O boards
One 6310/RTM/HA/STM1-OC3 (Rear Transition Module)
One 6310/RTM/HA/Redundant (Rear Transition Module for High Availability

systems only)
(For detailed information on the TP-6310 boards and 6310/RTMs, refer to 'The
TP-6310 Board' below)
Up to 2 SA/3K Synchronization and Alarm boards (refer to SA Synchronization

and Alarm RTM)
The TP-6310 board is a member of the 6310 series - TrunkPack cPCI VoP
communication platform family. The board is a high-density, hot-swappable,
compactPCI resource board with a capacity of 2016 DS0 channels, supporting all
necessary functions for voice, data and fax streaming over IP networks. It is available
in two versions:
TP-6310 board with STM-1/OC3 interface
TP-6310 board with T3/DS3 interface
Both board versions utilize the same front board, but its panel markings are modified
to accommodate the differences in the connections.
Each board version utilizes a different Rear Transition Module which provides the
appropriate connectors.
The 6310/RTM STM-1 version contains STM-1/OC3 interfaces for both ATM and
PSTN and provides integrated voice and signaling gateway functionality.
The 6310/RTM T3 version contains T3/DS3 interfaces for PSTN and provides the
same integrated voice and signaling gateway functionality as TP-6310 STM-1.
The TP-6310 board and 6310/RTM versions are shown in the figures below.
The TP-6310 board and RTMs are shown below. The 6310/RTM/STM-1/DC3 panel
contains Tx and Rx transceivers for up to 3 pairs of OC-3c ATM connectors and 1 pair
of OC-3 PSTN connectors. Each I/O connection is a cage provided with a slim form
pluggable SFP 155 Mbps optical module to connect to an optical fiber with an STM1/LC-type optical connector.
To ensure full integrated Automatic Protection Switching (APS) for both PSTN and
ATM interfaces, the fiber optic cables must be connected to corresponding PSTN and
ATM connectors on the 6310/RTM/HA/STM1-OC3. The PSTN interface is provided
with 1+1 protection.
The T3/DS3 panel contains Tx and Rx transceivers for up to 3 pairs of OC-3c ATM
connectors and 3 T3 PSTN interface ports.
Version 4.8
31
January 2006
Mediant 3000
Each OC-3c ATM I/O connection is a cage provided with a slim form pluggable SFP
155 Mbps optical module to connect to an optical fiber with an LC-type optical
connector. Each T3 PSTN interface port is an SMB connector.
Both board types are designed for protection capabilities. The 6310/RTM/ Redundant
provides a unique Redundant protection functionality. The 6310/RTM/ Redundant
itself does not provide any PSTN or ATM ports. The same redundant RTM should be
used for both STM-1 and T3 versions.
The following figures provide details about the board panels, LED indicators and
connectors:
'TP-6310 Board Diagram' on page 34
'TP-6310 Board Panel LED Indicators' on page 36
'6310/RTM/HA/STM1-OC3 Diagram' on page 43
'6310/T3 Board' on page 44
The TP-6310 should be considered as a complete Media Gateway module. Physically,

the TP-6310 occupies one slot of a cPCI chassis, that features its own MAC address,
IP address and board handle (when using the acOpenRemoteBoard API function),
etc. In addition, it has an STM-1/OC-3 PSTN interface with APS capability (1+1), as
well as an STM-1/OC-3 ATM interface with APS capability (1+1).
Note:
Currently, ATM APS and PSTN APS are partially compliant to GR253 only.
A redundant GbE interface that can be provided as copper 10/100/1000 or as an

Optical GbE interface (two different types of PEMs provides these types of interface.)
2.2.1
The TP-6310 Board and RTM

The figures below show the TP-6310 board and the TP-6310 RTM.
Figure 2-2: 6310 Board
User's Manual
32
User's Manual
Figure 2-3: 6310/RTM/HA/STM1-OC3
Figure 2-4: T3-RTM
The 6310/ RTM/HA/STM1-OC3 is shown with SFP modules inserted in corresponding

pairs of ATM and PSTN interfaces. For detailed information, refer to 'TP-6310 Board'.
Version 4.8
33
January 2006
Mediant 3000
Figure 2-5: 6310 Board: STM1 Panel

Fail Off - Normal Operation
Red - Board Failure
ACT Green - Active Board
Yellow - Redundant (HA)
Availability Ready
FAIL
ACT
GBE
1
LINK
GBE
Link 1 & 2
Green - Link OK
Blinking Green - Activity
Yellow - Protection Link OK
Off - No Link, No Carrier
LINK
ALRM
PSTN
LINK
ALRM
PSTN
Link A, B & C
Green - Working Link OK

Off - No Link
LINK
ALRM
ALRM (Alarm)
Off - Normal Operation, No Alarm
Red - Alarm
Refer to TP-6310 Board: STM-1 LED Alarm
Signal table below
6310 Series
1A
RX/TX
ALRM
RX/TX
2A
RX/TX
ATM
3A
1B
2B
3B
SWAP READY
Blue - Board can be removed or
has been inserted successfully
ALRM
ALRM
RX/TX
ALRM
RX/TX
ALRM
ATM
RX/TX - Receive/Transmit
Blinking Green - Link OK; Rx/Tx OK
Green - Link OK; No Rx/Tx
Blinking Yellow - Protection Link OK; Rx/Tx OK
Yellow - Protection Link OK; No Rx/Tx
ALRM (Alarm) Red
Off Normal Operation
Red Alarm
Refer to TP-6310 Board: LED Alarm Signal
table for for SDH or SONET below
RX/TX
ALRM
PWR
SWAP
READY
PWR (Power)
Green - Power On
Note: Some STM-1 boards exist that do not include PSTN C LED Indicators.
User's Manual
34
User's Manual
Figure 2-6: 6310 Board: T3 Panel

Fail Off - Normal Operation
Red - Board Failure
ACT Green - Active Board
Yellow - Redundant (HA)
Availability Ready
FAIL
ACT
GBE
1
LINK
GBE
Link 1 & 2
Green - Link OK
Blinking Green - Activity
Off - No Link
LINK
ALRM
PSTN
LINK
ALRM
PSTN
Link A, B & C
Green - T3/DS3 Synchronized
Yellow RAI Alarm
Off - No Link
LINK
C
ALRM
ALRM (Alarm)
Red - Alarm
Refer to TP-6310 Board: T3 LED Alarm
Signal table below
6310 Series
1A
RX/TX
ALRM
RX/TX
2A
1B
2B
3B
Version 4.8
ALRM
ATM
3A
SWAP READY
Blue - Board can be removed or
has been inserted successfully
ALRM
RX/TX
RX/TX
ALRM
RX/TX
ALRM
ATM
RX/TX - Receive/Transmit
Blinking Green - Link OK; Rx/Tx OK
Green - Link OK; No Rx/Tx
Blinking Yellow - Protection Link OK; Rx/Tx OK
Yellow - Protection Link OK; No Rx/Tx
Off No link
ALRM (Alarm)
Red - Alarm
Refer to TP-6310 Board: LED Alarm Signal
table for SDH or SONET below
RX/TX
ALRM
PWR
SWAP
READY
35
PWR (Power)
Green - Power On
January 2006
Mediant 3000
2.2.2
TP-6310 Board Panel LED Indicators

Table 2-2: TP-6310 Board: STM-1 Panel LED Indicators
Group
LED # LED Label

FAIL
ACT
Color
States
Off
Normal Operation
Red
Failure
Off
Stand alone board (non HA system)
Blinking Yellow
Redundant board in standby mode
Green
GbE
Link
Working board
Off
No Link, No Carrier
Green
Link
Blinking Green
Activity
Off
No Link
Green
PSTN
Link
Alrm
Link
Alrm
ATM
1A
Rx/Tx
(continues
below)
Alrm
User's Manual
Link
Blinking Green
Activity
Off
No Link
Green
Working Link OK
Yellow
Protection Link OK
Off
Normal operation
Red
Refer to TP-6310 Board Panel LED Alarm

Signals for SDH or SONET Terminology
Off
No Link
Green
Working Link OK
Yellow
Protection Link OK
Off
Normal operation
Red

Off
No Link
Blinking Green
Working Link OK; Rx/Tx OK
Green
Working Link OK; No Rx/Tx
Blinking Yellow
Protection Link OK; Rx/Tx OK
Yellow
Protection Link OK; No Rx/Tx
Off
Normal operation
36
User's Manual

Group
LED # LED Label
2A
Rx/Tx
Color
States
Red

Off
No Link
Blinking Green
Green
Working = link OK = no Rx/Tx
Blinking Yellow
Yellow
Alrm
3A
Rx/Tx
Alrm
1B
Rx/Tx
Alrm
2B
Version 4.8
Rx/Tx
Working Rx/Tx
Protection Rx/Tx
Protection link OK = no Rx/Tx
Off
Normal operation
Red

Off
No Link
Blinking Green
Green
Blinking Yellow
Yellow
Off
Normal operation
Red

Off
No Link
Blinking Green
Green
Blinking Yellow
Yellow
Off
Normal Operation
Red

Off
No Link
Blinking Green
Green
Blinking Yellow
Yellow

37
January 2006
Mediant 3000

Group
LED # LED Label
Color
Alrm
3B
Rx/Tx
States
Off
Normal Operation
Red

Off
No Link
Blinking Green
Green
Blinking Yellow
Yellow
Alrm
PWR
Off
Normal Operation
Red

Off
Board Power is down
Green
SWAP
READY
Normal Operation
Off
Blue
Normal Operation (see Note)
Table 2-3: TP-6310 Board: STM-1 Panel LED Alarm Signals for SDH or SONET Terminology
Meaning of Alarm Signals for SDH or SONET
Alarm (Red)
For Alarm LEDs
ALRM A, 1-A, 2-A,
3-A
ALRM B, 1--B, 2-B,
3-B
Off
User's Manual
SDH Name
Status
SONET Name
LOS
Loss of Signal
LOS
RS-LOF
(RS = Regenerator Section)
Loss of Frame
LOF
MS-AIS
(MS = Multiplex Section)
Alarm Indication
Signal
AIS-L
(L = Line)
MS-RDI
(MS = Multiplex Section)
Remote Defect
Indication
RDI-L
(L = Line)
Normal Operation
38
User's Manual
Table 2-4: TP-6310/T3 Board Panel LED Indicators

Group
LED #
LED Label
Color
FAIL
Off
Normal Operation
Red
Failure
Off
Stand alone board (non HA system)
ACT
Blinking Yellow
Green
GbE
Link
Off
Green
Link
ALRM
Link
ALRM
Redundant board in standby mode

Working board
No Link, No Carrier
Link
Blinking Green
Activity
Off
No Link
Green
PSTN
States
Link
Blinking Green
Activity
Off
No Link
Green
T3 Synchronized
Yellow
RAI
Off
No Near End Alarms
Red
Traffic loss due to one of the following 3

signals:
Off
LOS
Loss of Signal
LFA
Loss of Frame
Alignment
AIS
Alarm Indication Signal

(The blue alarm)
No Link
Green
T3 Synchronized
Yellow
RAI
Remote Alarm
Indication (The yellow
alarm)
Off
No Near End Alarms
Red

signals:
LOS
Version 4.8
Remote Alarm
Indication (The yellow
alarm)
39
Loss of Signal
January 2006
Mediant 3000

Group
LED #
LED Label
Link
ALRM
ATM
1A
Rx/Tx
(continues
below)
Alrm
2A
Rx/Tx
Color
Off
Loss of Frame Alignment
AIS

(The blue alarm)
No Link
T3 Synchronized
Yellow
RAI
Off
No Near End Alarms
Red

signals:
Off
LOS
Loss of Signal
LFA
AIS

(The blue alarm)
No Link
Blinking Green
Green
Blinking Yellow
Yellow
Off
Normal operation
Red

Off
No Link
Green
Blinking Yellow
Yellow
User's Manual
LFA
Green
Blinking Green
Alrm
States
Working Rx/Tx
Working = link OK = no Rx/Tx
Protection Rx/Tx
Protection link OK = no Rx/Tx
Off
Normal operation
Red

40
User's Manual

Group
LED #
LED Label
Color
3A
Rx/Tx
Off
Alrm
1B
Rx/Tx
Alrm
2B
Rx/Tx
Alrm
3B
Rx/Tx
Alrm
Version 4.8
States
No Link
Blinking Green
Green
Blinking Yellow
Yellow
Off
Normal operation
Red

Off
No Link
Blinking Green
Green
Blinking Yellow
Yellow
Off
Normal Operation
Red

Off
No Link
Blinking Green
Green
Blinking Yellow
Yellow
Off
Normal Operation
Red

Off
No Link
Blinking Green
Green
Blinking Yellow
Yellow
Off
Normal Operation
41
January 2006
Mediant 3000

Group
LED #
LED Label
Color
PWR
States
Red

Off
Board Power is down
Green
Normal Operation
Off
SWAP READY
Blue
Normal Operation (see Note)
Table 2-5: TP-6310 Board: T3 Panel LED Alarm Signals

Meaning of Alarm Signals for T3
Alarm (Red)
SDH Name
For Alarm LEDs

ALRM A, B, C
Off
2.2.3
Status
LFA
AIS
RAI
Remote Alarm Indication (Yellow Alarm)
Normal Operation
6310/RTM
The 6310/RTM/HA/STM1-OC3 (Rear Transition Module) provides the fiber optic I/O
connections for both ATM and PSTN links. Each I/O connection is an SFP (Small
Form Factor Pluggable) module with hot-insertion capabilities provided with a 155
Mbps optical SFP Module for a fiber optic STM-1/OC-3 interface.
The 6310/RTM/HA/STM1-OC3 is positioned in slot 2 directly behind an SA/M3K board
in the rear of the chassis and contains eight SFP receptacles and two RJ-45 Ethernet
ports, shown in the figure below. The 6310/RTM/HA/Redundant is positioned in slot 3,
directly behind an TP-6310 board in the rear of the chassis and contains two RJ-45
Ethernet ports only.
The 6310/RTM/HA/STM1-OC3 also includes two Gigabit Ethernet connectors that can
be used with either RJ-45 connector or fiber optic STM-1/OC-3 SPF module
connector. The GbE Port connects the system to the LAN. According to customer
order, the connection can be made with either fiber optic cables that attach to a SFP
Module or Category 5 LAN Cables.
User's Manual
42
User's Manual
Figure 2-7: 6310/RTM/ STM1-OC3 Board
1
A
2
A
3
A
A
T
M
1
B
2
B
ATM
Group A
3 SFP Receptacles
Marked 1A, 2A, & 3A
Mail links
Each SFP receptacle
houses an SFP module
ATM
Group B
3 SFP Receptacles
Marked 1B, 2B, & 3B
Protected links
Each SFP receptacle
3
B
P
S
T
N
1
A
1
B
PSTN
2 Pairs of SFP Receptacles
Marked 1A(Mail link)
and 1B (Protected link)
Each SFP receptacle
6310 Series
E
T
H
E
R
N
E
T
Version 4.8
Ethernet Ports 1+1 Redundancy

1 and 2
Make a
Redundant pair
43
January 2006
Mediant 3000
Figure 2-8: TP-6310/T3 Board
1
A
2
A
3
A
A
T
M
1
B
2
B
ATM
Group A
3 SFP Receptacles
Marked 1A, 2A, & 3A
Mail links
Each SFP receptacle
ATM
Group B
3 SFP Receptacles
Marked 1B, 2B, & 3B
Protected links
Each SFP receptacle
3
B
LASER PRODUCT
CLASS 1
TX
T3
RX
T3 PSTN
3 Pairs of T3 SMB TX and RX
Connectors
Marked A, B and C
TX
RX
TX
RX
6310 Series
E
T
H
E
R
N
E
T
User's Manual

1 and 2
Make a
Redundant pair
44
User's Manual
Note:
This board is High Availability.
Note: The unused SFP recepticles are covered with dust covers as shown in the
figure, ''Redundancy Connection Scheme for the 6310/RTM/HA/STM1-OC3''
on page 64.
Version 4.8
45
January 2006
Mediant 3000
Figure 2-9: 6310/RTM/Redundant
6310 Series
E
T
H
E
R
N
E
T
2.2.4

1 and 2
Make a
Redundant pair
SA/M3K Synchronization and Alarm Board

The SA/M3K synchronization and alarm board is a 6U to be plugged into the front
slots 2 and 4. This module monitors and controls the chassis environmental
components, by controlling the fans operation, monitoring the proper operation of the
power supply modules, monitoring the midplane voltages and controlling the chassis
LEDs. It interconnects to all of the chassis elements. Alarms detected are transmitted
User's Manual
46
User's Manual

via the midplane to the various LED indicators on the chassis and boards, as well as
to the Alarm Terminal Closures on the PEM/DC/3K modules.
The following list summarizes the SA/M3K functionality:
Monitoring all midplane voltages (3.3V, 5V, +12V, -12V)
Monitoring proper operation of all power supplies
Monitoring and controlling chassis temperature by changing the fans speed as a

function of chassis temperature
Controlling the state of alarm closures
Controlling the front panel chassis LEDs
Detecting the state of front chassis push-button
Detecting the availability of the power at the inlet leeds
There are two types of SA/M3K boards:
SA/M3K - Basic configuration with Alarm and Status only
SA/M3K/Stratum3 - Alarm, Status and Stratum 3 Synchronization
The SA/M3K boards are not cPCI compliant. However they are protected via code
keys on the midplane.
Version 4.8
47
January 2006
Mediant 3000
The figures below show the SA/M3K board and the SA/M3K/Stratum3 board.
Figure 2-10: SA-3 Board - Basic Configuration with Alarm & Status Only
Figure 2-11: SA-3 Board - Alarm, Status and Stratum 3 Synchronization
User's Manual
48
User's Manual
Figure 2-12: SA/M3K Alarm Board

cPCI Latch
FAIL
ACT
BITS/SETS
Sychronization Source
Status indicators 1 or 2
Green OK
Red Alarm
Fail Red Board Faillure

ACT Green Installation OK
Yellow - Standby
SA-3 Series
Status
ACT SRC
ACT SRC Active

Source
Sychronization Source
Status indicators 1 or 2
Green OK
Red Alarm
BITS/SETS
1
2
1
2
PWR Green Power On
PWR
SWAP
READY
SWAP READY Blue Board

can be removed or has been
inserted successfully
cPCI Latch
Table 2-6: SA/M3K Board LED Indicators

Label
Color
FAIL
Red
ACT
Green
Function
Board failure (fatal error)
Board initialization sequence terminated Bi-color indicator
OK
Indicates the Active board
Version 4.8
49
January 2006
Mediant 3000
Table 2-6: SA/M3K Board LED Indicators

Label
Color
Function
Yellow
Board initialization sequence terminated

OK
Yellow on indicates Standby board
BITS/SETS
Green
lit indicator indicates which Timing

source the board is using
LEDs 1 or 2
Red
Normally Off; Not in use
STATUS
Green
Functioning OK
LEDs 1 or 2
Red
Timing source failure
Off
Indicates that Timing is not coming from

this source
ACT SRC
Green
LEDs 1 or 2
Red
Timing source failure
Off
Indicates that this is not an Active

Source
HOT-SWAP
Blue
Board can be removed or inserted
PWR
Green
2.2.5
Active Source
Only one of the

LED pairs is lit
Only one of the

LED pairs is lit
Power is supplied to the board
Supplying the clock synchronization for the I/O Boards (Optional)
Interfacing BITS/SETS (Optional)
Board Hot-Swap Support

All of the boards are hot-swappable - the boards can be removed or inserted when the
system is under power.
2.3
Power
The Mediant 3000 Media Gateway chassis is powered by two DC sources configured
as 1+1.
Table 2-7: Power Requirements

Type
DC
User's Manual
Power Requirements
Connection Provisions
-40 to -72 V DC
PEMs with Input terminals
50
User's Manual
2.3.1
Power Consumption
The average power consumption for a full complement of boards is approximately 252
watts (5.25 A @ 48 VDC).
2.3.2
DC Input Power
WARNING
Use two separate DC power sources to avoid total power failure if one of the
DC power sources fails.
When using DC power as the primary input, ensure that the external power
supply complies with the safety requirements of CAN/CSA-C22.2 No. 6095000 UL 60950, and EN 60950
2.3.3
The Power Entry Module (PEM/DC/3K)

Two Power Entry Modules (PEM/DC/3K) are provided with the Mediant 3000 chassis.
Their function is to protect and to regulate the incoming power to the chassis, as well
as to combine the dual power feeds. Each PEM/DC/3K module contains the following
connectors and indicators:
GbE Port Connector - N/A
BITS/SETS Connector - The BITS (Building Integrated Timing Source) / SETS

(SDH Equipment Timing Source) Connector links to the Synchronization and
Timing source. One PEM is connected to the main BITS/SETS external source
and the second PEM is connected to a secondary source.
Alarm Terminal Block Closures - Contains 4 groups of terminals for connecting

external Telco alarm devices according to Critical, Major, and Minor severities as
indicated. Devices can be controlled using Common, Normally Open method.
The IN connector is for User-defined connections, which are to be implemented in
a future version.
DC Power Inlet - -48 VDC power connector
PWR IN & OUT Indicators - IN indicates that incoming primary voltage (-48
VDC) is detected. OUT indicates that the PEM/DC/3K secondary Power is good
and activate.OUT work in conjunction with the blue LED. (Refer to the SWAP
RDY Indicator below.) When Blue LED is on and OUT LED is off meaning there is
a power fault in the PEM/DC/3K board and it is out of service. When Blue LED is
off and OUT LED is on means that board is in service. When both BLUE and
OUT is in the on condition means that board is in service and can be extractable
due to uSW activation on panel.
For normal operation, both in and out power indicators should be lit.
Version 4.8
SWAP RDY Indicator - This indicates that the PEM/DC/3K unit is ready for HotSwap and can be removed or has been inserted successfully while the rest of the
system continues running. However, the PEM/DC/3K is not Hot-Swappable at
this time.
51
January 2006
Mediant 3000
Note 1: To ensure that the redundant configuration includes redundant electrical

input, connections must be made in both PEM/DC/3K modules.
Note 2: The power cord must be removed before removing the PEM/DC/3K
Figure 2-13: PEM/DC/3K Module

1
Table 2-8: PEM/DC/3K Front View Component Descriptions

Item #
Label
Component Description
ETH Port
Not Applicable Ethernet Interface is connected via Ethernet ports

on the 6310/RTM.
BITS/SETS
Standard E1/T1 RJ-45 Connector
DC IN
DC Power Inlet -48 VDC

Power LEDs
PWR IN/OUT LEDs
IN - Green - Incoming voltage detected

OUT - Green - Backplane power is alive
Alarm Terminal Block Closures
Alarm Terminal
Block
4 groups of Common, Normally Open

Connectors for Critical, Major, Minor and IN (User Defined)
SWAP RDY LED
Hot-Swap ready LED - Can be removed or has been inserted

successfully
Not Applicable - refer to note below.
User's Manual
52
User's Manual
WARNING
The PEM/DC/3K units are not hot-swapable.
PEM/DC/3K, disconnect the power cables.
2.3.4
Before extracting a
PS/DC/3K Power Supply Modules

Power for the Mediant 3000 Media Gateway is typically provided from redundant DC
power feeds, whose input voltage ranges from -40 to -72 V DC to accommodate
nominal -48 and -60 V DC mains. Power supply units function in a load-shared
configuration to provide necessary voltages and failsafe operation.
The PS/DC/3K power supply, shown below, is an advanced-design, multi-output
switching power supply, which can be provided in DC primary input power
configurations. This power supply can provide, on a continuous basis, four separate
outputs: +3.3 V, +5 V, +12 V and -12 V for a total of 250 watts.
The power supply is cPCI standards compliant that comes in an ultra-compact design
measuring 3U/8HP x 160.0mm. The unit has a handle for easy removal and reinsertion, under power (hot-swap capable).
Figure 2-14: PS/DC/M3K Power Supply
Table 2-9: PS/DC/3K LED Indicators

Label
Color
Power
Green
Fault
Red
2.4
Function
Power is supplied to the board
Power Supply failure
Cooling System
The Mediant 3000 Media Gateway components are cooled by a Fan Tray Unit, located
at the left of the card cage. (Refer to the figure showing the 'Mediant 3000's front view'
on page 30) The Fan Tray Unit draws air in through a perforated grill at the left side of
Version 4.8
53
January 2006
Mediant 3000
the chassis. The incoming air passes through a removable filter (located within the fan
assembly, immediately inside the perforated grill), whose honeycombed design
prevents RF interference. The clean air passes through the entire set of boards,
cooling each one. The air is drawn by 8 fans, within the fan tray unit and exits the
Mediant 3000 via perforated vents on the right side of the chassis.
Blank panels are used to cover all unoccupied slots (as per customers configuration)
on both sides of the chassis. The front blank panels are especially constructed to
assist optimal air flow within the chassis.
The Fan Tray Unit is easily removed and is hot swappable. The fans are divided into
two independent functional segments to prevent single point of failure. It contains 8
fans and an air filter, providing necessary airflow for each board in the card cage, even
if one of the fans or one segment stops working.
Warning
When removing the fan tray unit, the fans continue to rotate at a high speed.
Use caution and do not to touch the rotating fan blades.
Figure 2-15: Fan Tray and Alarm Indicators
2.4.1
Alarm Indicators
Alarm indicators on the Fan Tray panel of the chassis are connected to the SA/M3K
fault detection and alarm system provided with the Mediant 3000 Media Gateway.
The table below describes the chassis front panel alarm indicators.
Table 2-10: Chassis Front Panel Alarm Indicators

Componen
t
Label
LED 1
User's Manual
SYSTEM
Description
Color Code
Indicates correct
functioning of
Green
54
Remarks
Steady Green indicates proper SC
board functioning
User's Manual
Table 2-10: Chassis Front Panel Alarm Indicators

Componen
t
Label
Description
Color Code
system software
Red
Remarks
Steady Red during initialization of
active SC
Default = Red
LED 2
CRITICAL
Indicates the
detection of a fault
(or faults)
categorized as
Critical
Green when no critical alarms

Green
Red
Red when critical alarm is set.

When This Led is on, all other
Major and Minor severity LEDs are
also lit.
Default = Red
LED 3
LED 4
LED 5
Pushbutton
1
MAJOR
MINOR
SHELF
ACO
Indicates the
(or faults)
categorized as
Major
Green
Orange
Indicates the
(or faults)
categorized as
Minor
Green
Orange
Indicates the health

or failure of the
chassis hardware
as detected by the
alarm module.
Green
Red
Alarm Cut-Off
---
Green when no Major alarms

Orange when Major alarm is set.
When this Led is on, the Minor
severity LEDs is also lit.
Default = Orange
Green when no Minor alarms
Orange when minor alarm is set.
Default = Orange
Green = initialization complete
Red = during initialization process
Default = Red
Used to mute the Telco alarm relay
devices attached to the PEM.
Returns all of the alarm relays to
normal position, deactivating the
alarm relay devices. Both the
chassis LEDs and other gateway
alarm signals are NOT affected.
Activated with finger
Version 4.8
55
January 2006
User's Manual
3. Mediant 3000 Hardware Installation
Mediant 3000 Hardware Installation

Caution Electrical Shock
The equipment must only be installed or serviced by qualified service personnel.
Caution Laser
Note that some boards contains a Class 1 LED/Laser emitting device, as defined by
21CFR 1040 and IEC825.
Do NOT stare directly into the beam or into fiber optic terminations as this can
damage your eyesight.
Care in Handling Fiber Optic Cabling

Note 1: When handling the fiber optic cables, be sure to implement the following
points:
Excessive bending of the Fiber Optic Cable can cause distortion and signal losses
Ensure the minimum bending radius recommended by the Fiber Optic Cable
supplier
Maximum Fiber Optic Cable length for multimode fiber is 550 m
Note 2: Incoming optic cabling from the network infrastructure can originate from the
top of the rack or from another shelf within the rack. Preserve the minimumbending ratio indicated by the cable manufacturer.
Note 3: To assure full high-availability capabilities, the configuration of the interface
to the IP backbone must include certain redundant features from which two
separate fiber optic cables are incoming to the Mediant 3000. For more
information on, refer to ''Connecting the PSTN and ATM Interfaces'' on page
62.
To install the Mediant 3000 take these 3 steps:

1.
Unpack the Mediant 3000 (refer to "Unpacking" below).
2.
Mount the Mediant 3000 (refer to ''Mounting the Mediant 3000 Chassis'' on page
58).
3.
Cable the Mediant 3000 (refer to ''Cabling the Mediant 3000'' on page 61).
After powering-up the Mediant 3000, the Ready and LAN LEDs on the boards front
panel turn to green (after a self-testing period of about 60 seconds). Any malfunction
changes the Ready LEDs to red (refer to ''Mediant 3000 Hardware Overview'' on page
29 for details on the Mediant 3000 hardware and its LEDs).
When you have completed the hardware setup, proceed to the ''Software Package'' on
page 77).
Version 4.8
57
January 2006
Mediant 3000
3.1
Unpacking
To unpack the Mediant 3000 take these 6 steps:
3.1.1
1.
Open the carton and remove the packing materials.
2.
Remove the Mediant 3000 from the carton.
3.
Check that there is no equipment damage.
4.
Check, retain and process any documents.
5.
Notify AudioCodes of any damage or discrepancies.
6.
Retain any diskettes or CDs.
Package Contents
Ensure that the Mediant 3000 package contains (in addition to the Mediant 3000):
3.2
CD (software and documentation)
Mounting the Mediant 3000 Chassis

The figures below display the front and rear details of the Mediant 3000 chassis.
Figure 3-1: 3000 Chassis - Front Details - High Availablity System
User's Manual
58
User's Manual
Table 3-1: Mediant 3000 FrontDetails

Item #
Component
Description
ESD Terminal
For ESD connection

The FM/3K Fan Tray also houses the AF/3K Air Filter
The front panel contains the Alarm indicators:
FM/3K / AF/3K
System
Critical
Major
Minor
Shelf
The component location diagram indicates the numbering of the

board slots and power supply units.
The TP-6310 boards
3
TP-6310
In the 1+1 configuration - TP-6310 boards occupy slots 1 & 3 (The

board in slot 1 is initially active; the board in slot 3 is initially
standby (redundant))
In a simplex configuration one TP-6310 board occupies slot 1
only
The SA/3K boards
SA/3K
In the 1+1 configuration - SA/3K boards occupy slots 2 & 4 (The

board in slot 2 is initially active; the board in slot 4 is initially
standby (redundant))
In a simplex configuration one SA/3K board occupies slot 2 only
PS/DC/3K
Power Supply LEDs
Mounting brackets
Latches and screws
Version 4.8
PS/DC/3K Power Supply unit

2 units in a load-sharing configuration
Power Green indicates that the PS/DC/3K unit is ON
Fault Red indicates fault in the PS/DC/3K unit
For mount on a standard Telco rack
Each component is secured by latches and screws
The FM/3K Fan Tray has a handle and is secured by screws
59
January 2006
Mediant 3000
Figure 3-2: 3000 Chassis- Rear Details - High Availablity System
Table 3-2: Mediant 3000 Rear Details

Item #
Component
Description
PEM/DC/3K
PEM/DC/3K Power Entry Modules Refer to 'Power Entry

Module (PEM/DC/3K)' on page 51
Contains:
6310/RTM/HA/STM1OC3
ATM/PSTN STM-1/OC-3 connectors that house the SFP

modules
GbE Ethernet Interface ports - can be used with either RJ-45
connector or fiber optic STM-1/OC-3 SPF module connector
6310/RTM/HA/Redund
ant
Contains GbE Ethernet Interface ports - can be used with either

RJ-45 connector or fiber optic STM-1/OC-3 SPF module
connector
Blank Panels
Covers the unoccupied slots
Latches and screws
Each component is secured by latches and screws
ESD Terminal
For ESD connection
Earthing Terminal
Use a one-hole G-32 lug and 6-8 AWG wire

Above the ESD and Earthing terminals is the component
location diagram indicates the numbering of the board slots and
power supply units.
User's Manual
60
User's Manual
Rack Mount Safety Instructions (UL)

Note:
When mounting the chassis on a rack, be sure to implement the following

Safety instructions:
Elevated Operating Ambient - If installed in a closed or multiunit rack assembly, the operating ambient temperature of the
rack environment may be greater than room ambient. Therefore,
consideration should be given to installing the equipment in an
environment compatible with the maximum ambient temperature
(Tma) specified by the manufacturer.
Reduced Air Flow - Installation of the equipment in a rack

should be such that the amount of air flow required for safe
operation on the equipment is not compromised.
Mechanical Loading - Mounting of the equipment in the rack

should be such that a hazardous condition is not achieved due to
uneven mechanical loading.
Circuit Overloading - Consideration should be given to the

connection of the equipment to the supply circuit and the effect
that overloading of the circuits might have on overcurrent
protection and supply wiring. Appropriate consideration of
equipment nameplate ratings should be used when addressing
this concern.
Reliable Earthing - Reliable earthing of rack-mounted

equipment should be maintained. Particular attention should be
given to supply connections other than direct connections to the
branch circuit (e.g., use of power strips.)
To install the Mediant 3000 chassis in a 19-inch rack, take these 2

steps:
3.3
1.
Attach the device to the rack structure with the brackets, using rack screws(not
provided). Note that optional rear and mid attachment is supported.
2.
Go to ''Cabling the Mediant 3000'' on page 61 for cabling details.
Cabling the Mediant 3000

The connection to the Mediant 3000 should be made in the following order:
Version 4.8
Chassis Earthing
6310/RTM/HA/STM-OC3 Fiber Optic Connections to the 6310/RTM/HA/STMOC3
6310/RTM/HA/STM-OC3 Ethernet Connections
PEM/DC/3K Connections
BITS/SETS Links (applicable in future releases)

61
January 2006
Mediant 3000
3.3.1
DC Power Connection
Connecting the Earth

Earthing
Safety Earth
Intrinsically, the Mediant 3000 chassis must be safety-earthed using an equipmentearthing conductor. Do not depend on locknut-bushings and double-locknuts
for bonding purposes. Use the earthing hardware provided with the chassis.
Earthing Electrode
The gateway must be earthed to a stable local earth reference. The gateway's earth
terminal should be connected thought a separate earth wire (6-8 AWG
recommended) to the rack's earthing. The earth connections resistance
must not be greater than 0.1 ohm. Verify that the racks earthing is properly
performed.
To connect the earthing cable take this step:
Permanently connect the unit to a suitable earth with the earthing screw on the
rear connector panel, using a one-hole G-32 lug and 6-8 AWG wire.
3.3.2
Connecting the PSTN and ATM Interfaces
3.3.2.1
Connecting Fiber Optic Cables to the SFP Trunk Interfaces

To ensure full 1+1 redundancy protection, the fiber optic cables must be connected to
corresponding PSTN and ATM connectors in the TP-6310 RTM.
Note: The ATM synchronization reference link must be connected to the first port
of the fiber group (port 1A and1B).
3.3.2.2
Fiber Optic Connections

AudioCodes provides 155 Mbps Optical SFP modules for OC-3/STM-1 links. To
interface with these connectors, the customer should provide incoming twin fiber optic
cable with an LC-type plug.
3.3.2.3
SFP Modules
The SFP modules contain a locking mechanism that insures that the module can not
be inadvertently pulled out of the port socket. There are several types of SFP
modules, two of which are displayed in the figure below
User's Manual
62
User's Manual
Note: The SFP modules are supplied already inserted into the TP-6310 RTM. If
an SFP module is removed from the RTM, be sure to set the SFP module to
the Lock position BEFORE inserting it into the RTM port.
Figure 3-3: Two types of SFP Modules and Their Locks
3.3.2.4
Connecting the PSTN Interface for 6310/RTM with STM1-OC3

Interface
To connect the PSTN interface, take these 2 steps:
3.3.2.5
1.
On an TP-6310 RTM, connect twin single-mode fiber optic cable with LC-type
plugs to the PSTN transceivers marked 1A in the PSTN Group.
2.
Connect twin fiber optic cable with LC-type plugs to the PSTN transceivers
marked 1B in the PSTN Group.
Connecting the PSTN Interface for 6310/RTM with T3/DS3 Interface

To connect the T3 PSTN interface, take this step:
1.
3.3.2.6
On an TP-6310 RTM, connect twin SMB T3 cables to the T3 Tx and Rx

connectors.
Connecting the ATM Interface

As shown in the figure below, the ATM connections marked as ATM Group 1 are
protected by the ATM Group 2. Connection 1A in ATM Group A is protected by
connection 1B in ATM Group B, similarly, connection 2A in ATM Group A is protected
by connection 2B in ATM Group B, as well as connection 3A in ATM Group A is
protected by connection 3B in ATM Group B. The complement of connections
achieves full 3+3 redundancy.
To connect the ATM interface, take these 2 steps:

1.
Version 4.8
On the TP-6310 RTM, connect twin single-mode fiber optic cable with LC-type
plugs to the ATM transceivers marked 1A, 2A and 3A in the ATM Group A.
63
January 2006
Mediant 3000
2.
Connect twin fiber optic cable with LC-type plugs to the ATM transceivers marked
1B, 2B and 3B in the ATM Group B.
Figure 3-4: Redundancy Connection Scheme for the 6310 RTM
1
A
AMP
AMP
AMP
Dust covers
cover the unused
recepticles
as needed
A
T
M
AMP
2
A
3
A
1
B
AMP
AMP
AMP
AMP
P
S
T
N
ATM 1+1 Redundancy

1A (from Group A) and 1B (from Group B)
Each make a redundant pair
2
B
3
B
1
A
PSTN 1+1 Redundancy

1A and 1B
Make a
Redundant pair
1
B
6310 Series
E
T
H
E
R
N
E
T

1 and 2
Make a
Redundant pair
Note: In the current version, only Connection 1A in ATM Group A and 1B in ATM
Group B are implemented. The other ATM receptacles are covered with
dust covers as shown in the figure above.
User's Manual
64
User's Manual
Figure 3-5: TP-6310/T3 Connection Diagram
1
A
AMP
AMP
AMP
Dust covers
cover the unused
recepticles
as needed
A
T
M
AMP
2
A
3
A
1
B
AMP
AMP
AMP
AMP
P
S
T
N
ATM 1+1 Redundancy

Each make a redundant pair
2
B
3
B
1
A
PSTN 1+1 Redundancy

1A and 1B
Make a
Redundant pair
1
B
6310 Series
E
T
H
E
R
N
E
T
Version 4.8

1 and 2
Make a
Redundant pair
65
January 2006
Mediant 3000
3.3.3
Ethernet Ports
3.3.3.1
Connecting GbE (Gigabit Ethernet) Interfaces

Either RJ-45 connectors or fiber optic STM-1/OC-3 SPF module connectors can be
used for the GbE (Gigabit Ethernet) Interfaces ports on the 6310/RTM/HA/STM1-OC3
and 6310/RTM/HA/Redundant rear transition module.
To connect the GbE interfaces, take thIs step:
On each of the 6310/RTMs, connect the LAN to each of the GbE port connectors
using either:
Category 5 LAN cables with RJ-45 plugs (Refer to the figure below.)
OR,
Multi-mode fiber optic cables with dual LC plugs.
Table 3-3: RJ-45 Receptacle Pinouts

Pin #
FE Signal
GE Signal
TX DATA+1
Tx A+
TX DATA-
Tx A-
RX DATA+2
Rx B+
N/C
Tx C+
N/C
Tx C-
RX DATA-
Rx B-
N/C
Rx D+
N/C
Rx D-
Figure 3-6: RJ-45 LAN/Ethernet Network Port and Connector
3.3.4
PEM/DC/3K Connections
The PEM/DC/3K connection procedures described in this section include:
User's Manual
66
User's Manual
BITS/SETS Connector
DC Power Connections
To make the PEM/DC/3K connections to the Alarm terminal block

closures, take these 3 steps:
1.
Check the Telco alarm equipment that is to be connected to the Alarm Terminal
Closures.
External alarm indicators can be connected to the PEMs of the Mediant 3000
system.
Use the green Terminal Block Connector to connect external devices according
to the Critical, Major, and Minor as indicated. (Refer to 'DC Power and Alarm
Connectors' on page 69.) Devices can be controlled using the Common,
Normally Open method. User-defined connection is to be implemented in a
future version.
The PEM provides 3 dry contact relays for connecting to Telco alarm equipment.
Each alarm output is a dry relay contact. Each contact can withstand up to a
maximum of 30V DC when open and carries up to a maximum of 2A DC when
closed.
Use 20 AWG copper wire for these connections.
This connection method is recommended for providing a dual-redundant
solution.
2.
Connect the closures of both PEMs using the normal logic method in which the
equipment has NO (Normally Open) and COM terminals. (Refer to the figure
below.)
3.
Make the connections according to the figure below and the appropriate diagram
below. Refer to the figure below for the position of the pins.
Table 3-4: Alarm Terminal Block Pin Details

Pin Number
Description
1 - Common
2 N.O.
CRT - Critical Alarm
3 - Common
4 N.O.
MJR - Major Alarm
5 - Common
6 N.O.
MNR - Minor Alarm
7 Alarm In
8 GND
IN - User Alarm In
Version 4.8
67
January 2006
Mediant 3000
Figure 3-7: Normal Logic Alarm Connection Diagram
Alarm
Connections
on PEM/DC/3K
NO
COM
NO
Alarm
Connections
on PEM/DC/3K
TELCO
Alarm Equipment
COM
NO
COM
To make the PEM/DC/3K connections on the BIT/SET Connector, take this step:
3.3.5
BIT/SET Connector: On each of the PEMs, connect the external synchronization

sources to the BITS/SETS connectors using Category 5 cables with RJ-45 plugs.
Connection the DC Power

Redundancy
To ensure redundant protection, both power supply modules must be connected to
power.
To attach the Power Supply Cabling, take this step:
User's Manual
The Gateway is equipped with a DC power inlet (type MSTB2.5/2-STF (5.08mm)

of Phoenix Contact) on each of the PEMs, on the rear of the chassis. Connect
each -48 VDC power supply using 6-8 AWG cables. The DC input is floating and
the maximum input current is 5.25 amp. Note the + / - polarity indicated under the
DC IN. Refer to the figure below.
68
User's Manual
Figure 3-8: DC Power and Alarm Connectors
The hardware installation in now complete.
3.4
Component Replacement and Maintenance

Note: Electronic components on printed circuit boards are extremely sensitive to
static electricity. Normal amounts of static electricity generated by clothing
can damage electronic equipment. To reduce the risk of damage due to
electrostatic discharge when installing or servicing electronic equipment, it is
recommended that anti-static grounding straps and mats be used.
Before removing or replacing boards from the chassis, take these

2 steps:
1.
Locate the 2 ESD (electrostatic discharge) connections on the Mediant 3000

chassis. One is located on the front right bottom corner (when facing the front
cage), protruding from the flange. The other is located on the rear right corner
(when facing the rear cage), next to the earth connections.
2.
Attach a wrist strap for electrostatic discharge (ESD) and connect it to the ESD
connections in either the front or the back of the chassis using a banana plug or
an alligator clip.
Note: Do not set components down without protecting them with an anti-static bag.
Version 4.8
69
January 2006
Mediant 3000
3.4.1
Board Replacement
In the event of a board failure, the Mediant 3000 Media Gateway system automatically
performs a switchover to the standby board (now making it the active board) and
notifies users with an alarm. Replace the failed board as soon as possible to restore
the systems availability. The boards are hot-swappable, meaning that the board can
be inserted and removed while the Mediant 3000 chassis is under power
Note: It is imperative to cover all unoccupied slots in the front cage of the chassis
and all unoccupied slots in the rear cage of the chassis with blank panels to
maintain internal airflow pressure. See the most current release notes for
more information before changing any configuration.
Figure 3-9: Blank Panel for Rear Slots
3.4.1.1
Locking the Mediant 3000 Prior to Shutdown

The Mediant 3000 Media Gateway components are hot-swappable, which means that
they can be removed from the chassis without requiring that the Mediant 3000 Media
Gateway be taken out of service. However, when the Mediant 3000 Media Gateway is
a single gateway (engineered into the network with a N+1 redundancy meaning that
other gateways in the network are available to take the load in the event of a card
failure), the chassis may be powered down before replacing the components. The
exception is for cleaning or replacing the fan filters, which can be carried out while the
system is fully functioning.
Prior to powering down the Mediant 3000, it should be locked gracefully (with no
active calls forced to terminate) using the element management system employed in
your system. For more information on performing graceful lock, refer to the user
documentation accompanying the element management system employed in your
system.
Graceful shutdown parameters, also known as node maintenance, are provided via an
SNMP interface. For more information about these parameters, refer to ''Node
Maintenance'' on page 201 and' 'Graceful Shutdown'' on page 202.
3.4.1.2
Removing Boards
To remove the TP-6310 or SA/M3K board from the chassis, take
these 3 steps:
1.
User's Manual
Unfasten the screws on brackets at both ends of the panel that secure the board
to the chassis.
70
User's Manual
2.
Press the red ejector buttons on the two black ejector/injector latches on both
ends.
3.
Grasp the panel and ease the board out of the slot.
To remove the 6310/RTM from the chassis, take these 4 steps:
3.4.1.3
1.
On the 6310/RTM, disconnect all cables.
2.
Unfasten the screws on the plate of the board.
3.
Press the red ejector buttons on the two black ejector/injector latches on both
ends.
4.
Pull on the two ejector/injector latches and ease out the board from the slot.
Inserting Boards
Note 1: Make a note of the MAC address of the replacement board as it is needed
for setting the correct parameter configuration for the replacement board in
the element management system you are utilizing.
Note 2: Be sure NOT to use excessive force when inserting boards into the chassis
cage.
To insert the TP-6310 or SA/M3K board into the chassis, take these
5 steps:
1.
Hold the board horizontally.
2.
With the black ejector/injector latches in the open (pulled out) position, insert the
board in the slot, aligning the board on the groves on each end.
3.
Ease the board all the way into the slot until the ejector/injector latches touch the
chassis.
4.
Press the two black ejector/injector latches on both ends inward, toward the
middle until you hear a click.
5.
Fasten the screws on the front plate of the board to secure the board to the
chassis and to ensure that the board has an earth connection to the chassis.
To insert the 6310/RTM into the chassis, take these 6 steps:
Version 4.8
1.
Hold the board horizontally.
2.
With the black ejector/injector latches in the open (pulled out) position, insert the
board in the slot, aligning the board on the groves on each end.
3.
Ease the board all the way into the slot until the ejector/injector latches touch the
chassis.
4.
Press the two black ejector/injector latches on both ends inward, toward the
middle until you hear a click.
5.
Fasten the screws on the front plate of the board to secure the board to the
chassis and to ensure that the board has an earth connection to the chassis.
6.
Reattach the cables.
71
January 2006
Mediant 3000
3.4.1.4
Configuring and Unlocking the Mediant 3000

The MAC address of the replacement board should be updated in the parameter
configuration in the element management system you are utilizing.
The Mediant 3000 should be unlocked using the element management system
employed in your system. For more information on performing graceful lock, refer to
the user documentation accompanying the element management system employed in
your system.
3.4.1.5
Restoring ini Files and Other Configuration Files

Use the backup copies of ini files and other configuration files to restore
configurations as suggested in the ''Embedded Web Server'' on page 202. Use the
utilities provided in ''Backup Copies of 'ini 'and Auxiliary Files'' on page 100 to load
these files.
3.4.2
PS/DC/3K Module Replacement

To remove a faulty PS/DC/3K power supply, take these 3 steps:
1.
Unfasten the 4 screws on the plate of the power supply to be removed.
2.
Press the red ejector button on the black ejector/injector latch.
3.
Pull on the ejector/injector latch and ease out the power supply from the slot.
To insert a replacement PS/DC/3K power supply, take these 4

steps:
3.4.3
1.
Hold the power supply horizontally with the black ejector/injector latch pointed
outward.
2.
With the black ejector/injector latch in the open (pulled out) position, insert the
power supply in the slot.
3.
Ease the power supply all the way into the slot until the ejector/injector latch
touch the chassis.
4.
Press the black ejector/injector latch inward, toward the middle until you hear a
click.
PEM/DC/3K Replacement
To remove a faulty PEM/DC/3K, take these 5 steps:
User's Manual
1.
Remove the power cable to the PEM to be removed.
2.
Remove all other cables attached to the PEM to be removed.
3.
Unfasten the 4 screws on the plate of the PEM to be removed.
4.
Press the red ejector button on the black ejector/injector latch.
5.
Pull on the ejector/injector latch and ease out the PEM from the slot.
72
User's Manual
To insert a replacement PEM/DC/3K, take these 6 steps:
3.4.4
1.
Hold the PEM horizontally with the black ejector/injector latch pointed outward.
2.
With the black ejector/injector latch in the open (pulled out) position, insert the
PEM into the slot.
3.
Ease the PEM all the way into the slot until the ejector/injector latch touch the
chassis.
4.
Press the black ejector/injector latch inward, toward the middle until you hear a
click.
5.
Except for the power cables, re-connect all of the cables.
6.
Reconnect the power cables.
Fan Tray Unit Replacement

The Fan Tray Unit is located to the left of the Mediant 3000 chassis front.
Note: Be sure to prepare a replacement Fan Tray Unit before removing the faulty
Fan Tray Unit. It is imperative the chassis does not remain without the Fan
Tray Unit for more than a short period of time.
To remove a faulty fan tray unit, take these 2 steps:
Warning
When removing the fan tray unit, the fans continue to rotate at a high speed.
Use caution not to touch the rotating fan blades.
1.
Release the 2 screws on the top left-hand corner and the bottom left-hand corner
of the front panel of the fan tray unit.
2.
Pull on the fan tray units handle outward.
To insert a replacement fan, take these 3 steps:

1.
Insert the fan tray unit into its slot, until the front panel is flush with the chassis
plate.
2.
Verify that the fan is functioning correctly by checking that the software has not
reported any fan failure.
You can also check the fan tray itself - remove the fan tray and check that all of
the fans are spinning, then re-insert the fan tray.
Version 4.8
73
January 2006
Mediant 3000
3.
Fasten the screws at both the upper and lower ends of the fan tray unit.
Figure 3-10: Fan Tray Unit
User's Manual
74
User's Manual
3.4.4.1
Air Filter Replacement

The NEBS compliant air filters should be replaced approximately every 90 days. In
addition, the air filters should be checked weekly to make sure they are not saturated
and require replacement. The figure, 'Air Filter Insertion Position Indicators', below
shows the Insertion Direction indicator and upper side indicator provided on the filter.
The figure, 'Removing the Air Filter', below shows the air filter partially removed from
the Mediant 3000 chassis. You should clean an air filter no more than three times,
after which the air filter requires replacement.
Figure 3-11: Air Filter Insertion Position Indicators
Figure 3-12: Removing the Air Filter
To remove the air filter, take these 2 steps:

1.
Version 4.8
Remove the Fan Tray Unit (refer to ''Replacing the Fan Tray Unit'' on page 73).
75
January 2006
Mediant 3000
2.
With your fingertips, grasp the inside of the steel frame of the air filter and pull it
out of its slot. It should slide out relatively easily. If it does not, pull with slightly
more force.
WARNING
Be sure to prepare all of the equipment you need to clean the air filter before
removing the air filter for cleaning. It is imperative the chassis not remain
without the Fan Tray Unit for long. Be sure to reinsert the Fan Tray Unit
while you are cleaning the air filter and reinsert the air filter as soon as it is
clean and dry.
To insert the air filter, take these 2 steps:
User's Manual
1.
With the Upper Side indicator showing and the Insertion Direction arrow pointing
toward the Fan Tray slot, slide the air filter into its slot, pushing it all the way in.
2.
Replace the Fan Tray Unit in its location into the chassis (refer to ''Replacing the
Fan Tray Unit'' on page 73).
76
User's Manual
4. Software Package
Software Package
After installing the device and powering it up, you are ready to install the utilities that
are included in the software package. This software package must be installed on the
host PC/machine to be used to manage the device. The software package is supplied
to customers on a CD accompanying the Mediant 3000.
To get started, take these basic steps:
4.1
1.
Install the software package (go to Installing the Software Package" below.)
2.
Check the software package contents (go to ''Software Directory Contents &
Structure'' on page 78.)
3.
Go to ''Getting Started'' on page 81.
Unzipping the Software Package

The software package is contained on a CD supplied with the device. It is also
available on the AudioCodes' FTP Web site.
4.1.1
Customers using a Windows operating system may choose to install the

package via the installation wizard, or choose to unzip the software package from
the supplied zip file (refer to "Installing/Unzipping When Using a Windows
Operating System" below).
Customers using a Linux/Solaris operating system unzip the software

package from the tar.z (refer to "Unzipping When Using a Linux/Solaris
Operating System" below).
Installing/Unzipping When Using a Windows Operating

System
To install the package, take these 2 steps:
1.
Double-click on the setup.exe executable.
2.
Follow on-screen instructions.
To unzip when using a Windows operating system, take these 3

steps:
Version 4.8
1.
Using a tool like WinZip, open the zip file.
2.
Click the button Extract; the Extract screen opens.
3.
Navigate to the directory that you require to be the root directory for the
installation and click the button Extract; the files are extracted to the location you
specified.
77
January 2006
Mediant 3000
4.1.2
Unzipping When Using a Linux/Solaris Operating System

To unzip when using a Linux/Solaris operating system, take
these 2 steps:
4.2
1.
To open the tar.Z archive, uncompress the tar.Z file.
2.
Enter the command: tar -xvf xxxxxx.tar.
Software Directory Contents & Structure

Table 4-1: Software Package Contents
Contents
Directory
Description
Auxiliary Files
.\Auxiliary_Files\MIB_Files
Various MIB files, e.g., SNMP MIB

files: ACL.my, RTP.my, ds1.my,
MIB_2.my, V2_MIB.my
.\Auxiliary_Files\Sample_Call_Pro Contains examples of Call Progress

Tones configuration files
gress_Files
.\Auxiliary_Files\Sample_CAS_Pr
otocol_Files
Contains examples of CAS protocol

files
.\Auxiliary_Files\Sample_Ini_Files Contains examples of configuration

(ini) files
Users can utilize these sample files
as a baseline for creating
customized configuration files.
Firmware
The package firmware files (cmp

and hex files) are used for firmware
updates. The device contains preinstalled firmware when it is
supplied to customers.
.\Firmware
AudioCodes supplied applications

that are used for various purposes:
Utilities
User's Manual
.\Utilities\BootP_TFTP_Server
BootP TFTP Server. This sample

tool can be used to configure the
network parameters and optionally
download SW and configuration
files to AudioCodes devices.
.\Utilities\DConvert
DConvert Utility - used to build

configuration files that can then be
downloaded to the device
.\Utilities\MGCP_Call_Manager_D
emo
MGCP Call Manager Demo a

sample MGCP call manager. Runs
a basic call flow.
.\Utilities\PCI_Diagnostic_Utility
PCI Diagnostic Utility a utility for

diagnostics of AudioCodes PCI
78
User's Manual
4. Software Package
Table 4-1: Software Package Contents

Contents
Directory
Description
boards.
.\Utilities\PSTN_Trace_Utility
PSTN Trace Utility a utility for

analyzing a trace of PSTN signaling
events recorded by an AudioCodes
device.
.\Utilities\SpecialID_Utility
Special ID Utility - TBD

AudioCodes proprietary API for
controlling and managing the
device.
VoP API Library
Detailed information on the

VoPLibrary can be found in
AudioCodes VoPLib API Reference
Manual, Document #: LTRT-840xx
and VoPLib Users Manual,
Document #: LTRT-844xx.
.\VoP_API_Library\VoPLib\
Contains the VoPLib source files

(including the source and header
files, as well as the library in debug
and release versions for windows
Operating System).
.\VoP_API_Library\VoPLib_API_E
xamples
Contains examples of code.
.\VoP_API_Library\VoPLib_Tcl_E
xtensions
TCL-based demo program named

Apirunce (available for Linux,
Solaris and Windows Operating
Systems).
.\VoP_API_Library\VoPShell
Console-based demo program.
.\VoP_API_Library\windrvr_5
Contains the WinDriver PCI driver

files and utilities for various
operating systems.
.\VoP_API_Library\windrvr_6
Contains the WinDriver PCI driver

files and utilities for various
operating.
All relevant product documentation
Documentation
Note: All the demo programs described above are for reference only. Flawless
operation and stability of these applications can not be guaranteed.
Version 4.8
79
January 2006
User's Manual
5. Getting Started
Getting Started
The Mediant 3000 is supplied with application software already resident in its flash
memory (with factory default parameters). The Mediant 3000 is also supplied with an
Embedded (integrally stored) Web Server.
'Assigning the Mediant 3000 IP Address' below describes how to assign an IP address
to the Mediant 3000.
For detailed information on how to fully configure the gateway refer to the' Mediant
3000 Initialization & Configuration Files' on page 83 and to the 'Embedded Web
Server' on page 202.
5.1
Assigning the Mediant 3000 IP Address

To assign an IP address to the Mediant 3000 use one of the following methods:
HTTP using a Web browser (refer to ''Assigning an IP Address Using HTTP'' on

page 81).
BootP (refer to ''Assigning an IP Address Using BootP'' on page 82).
DHCP (refer to ''Using BootP/DHCP'' on page 86).
The default networking parameters are shown below.

Default Networking Parameters
Default IP address: 10.1.10.10
Default subnet mask is 255.255.0.0
Default gateway IP address is 0.0.0.0
5.1.1
Assigning an IP Address Using HTTP

To assign an IP address using HTTP, take these 8 steps:
Version 4.8
1.
Connect your PC to the Mediant 3000. Either connect the network interface on
your PC to a port on a network hub / switch (using an RJ-45 Ethernet cable), or
use an Ethernet cross-over cable to directly connect the network interface on
your PC to the RJ-45 jack on the Mediant 3000.
2.
Change your PCs IP address and subnet mask to correspond with the Mediant
3000 factory default IP address and subnet mask, shown in the table above. For
details on changing the IP address and subnet mask of your PC, refer to
Windows Online Help (Start>Help).
3.
Access the Mediant 3000 Embedded Web Server (refer to ''Embedded Web
Server'' on page 202).
4.
In the Quick Setup screen (shown in the ''Quick Setup Procedure'' on page 209),
set the Mediant 3000 IP Address, Subnet Mask and Default Gateway IP
Address fields under IP Configuration to correspond with your network IP
settings. If your network doesnt feature a default gateway, enter a dummy value
in the Default Gateway IP Address field.
81
January 2006
Mediant 3000
5.
Tip:
5.1.2
Click the Reset button and click OK in the prompt. The Mediant 3000 applies the
changes and restarts. This takes approximately 1 minute to complete. When the
Mediant 3000 has finished restarting, the Ready and LAN LEDs on the front
panel are lit green.
Record and retain the IP address and subnet mask you assign the Mediant
3000. Do the same when defining a new username or password. If the
Embedded Web Server is unavailable (for example, if youve lost your
username and password), use the BootP/TFTP configuration utility to access
the device, reflash the load and reset the password (refer to the Appendix,
''BootP/TFTP Server'' on page 307 for detailed information on using a
BootP/TFTP configuration utility to access the device).
6.
Disconnect your PC from the Mediant 3000 or from the hub / switch (depending
on the connection method you used in step 1 above).
7.
Reconnect the Mediant 3000 and your PC (if necessary) to the LAN.
8.
Restore your PCs IP address & subnet mask to what they originally were. If
necessary, restart your PC and re-access the Mediant 3000 via the Embedded
Web Server with its new assigned IP address.
Assigning an IP Address Using BootP

Note: BootP procedure can also be performed using any standard compatible
BootP server.
Tip:
You can also use BootP to load the auxiliary files to the Mediant 3000 (refer
to ''Using BootP/DHCP'' on page 86 and the Appendix, ''BootP/TFTP Server''
on page 307).
To assign an IP address using BootP, take these 3 steps:
5.2
1.
Open the BootP application (supplied with the Mediant 3000 software package).
2.
Add the client configuration for the Mediant 3000, refer to 'Client Configuration
Screen'.
3.
Reset the gateway physically causing it to use BootP. The Mediant 3000 changes
its network parameters to the values provided by the BootP.
Assigning the IP Addresses for High Availability

Mode
The M3KGlobalIpAddr board parameter is set (burned to flash or received by the ini
file) in the active board to a valid IP address that is different than the local IP address
of the TP-6310 boards, but with the same subnet.
User's Manual
82
User's Manual
6. Mediant 3000 Initialization & Configuration Files
Mediant 3000 Initialization &

Configuration Files
This section describes the Configuration Options and Initialization Procedures for the
Mediant 3000. It includes:
6.1
Boot Firmware & Operational Firmware (refer to 'Boot Firmware & Operational
Firmware' below)
Startup Process (refer to 'Mediant 3000 Startup' below)
BootP/DHCP (refer to 'Using BootP/DHCP' on page 86)
Configuration Parameters and Files (refer to 'Configuration Parameters and Files'

on page 91)
Auxiliary Files (refer to the 'Appendix - Auxiliary Files' on page 409)
Boot Firmware & Operational Firmware

The Mediant 3000 runs two distinct software programs: Boot firmware and operational
firmware.
6.2
Boot firmware - Boot firmware (also known as flash software) resides in the
Mediant 3000's non-volatile memory. When the Mediant 3000 is reset, Boot
firmware is initialized and the operational software is loaded into the SDRAM from
a TFTP server or integral non-volatile memory. Boot firmware is also responsible
for obtaining the Mediant 3000's IP parameters and ini file name (used to obtain
the Mediant 3000's configuration parameters) via integral BootP or DHCP clients.
The Boot firmware version can be viewed on the Embedded Web Servers GUI
(refer to ''Embedded Web Server'' on page 202). The last step the Boot firmware
performs is to jump to the first line of code in the operational firmware.
Operational firmware files - The cmp and hex operational firmware, in the form of
a cmp file (the software image file) and hex file (the uncompressed software
image file), is supplied in the software package contained on the CD
accompanying the Mediant 3000. These files contain the Mediant 3000's main
software, providing all the services described in this manual. The cmp file is
usually burned into the Mediant 3000's non-volatile memory so that it does not
need to be externally loaded each time the Mediant 3000 is reset (except when
the board is controlled via PCI).
Mediant 3000 Startup

The Mediant 3000's startup process begins when the Mediant 3000 is reset. The
startup process ends when the operational firmware is running. The startup process
includes how the Mediant 3000 obtains its IP parameters, firmware and configuration
files.
The Mediant 3000 is reset when one of the following scenarios occurs:
1.
Version 4.8
The Mediant 3000 is manually reset.
83
January 2006
Mediant 3000
User's Manual
2.
acOpenRemoteBoard() is called with RemoteOpenBoardOperationMode set to

Full Configuration Mode (valid for VopLib API users only).
3.
acOpenBoard is called; VoPLib users who control the Mediant 3000 via PCI call
this API to initialize the Mediant 3000 (valid for VopLib API users only).
4.
acResetRemoteBoard() is called in the VoPLib API (valid for VopLib API users
only).
5.
There is a device irregularity.
6.
Users perform a reset in the Embedded Web Server GUI or SNMP manager.
7.
The flow chart in the figure below illustrates the process that occurs in scenarios
1-6.
84
User's Manual
Figure 6-1: Startup Process Diagram

Reset command from Web interface,
SNMP, or acRemoteOpenBoard()
VoPLib API
Reset board via Power Reset,

acResetRemoteBoard() VoPLib API or
board exception
BootP
x times
Yes
No
Update network
parameters from
BootP/DHCP reply
DHCP
x times
No
Yes
BootP/DHCP
reply contains firmware
file name?
No
Yes
Download
firmware via
TFTP
BootP/DHCP
reply contains ini file
name?
BootP/DHCP
reply contains ini file
name?
No
Preconfigured
firmware URL?
Yes
Yes
No
Yes
Download
firmware via
TFTP
No
Preconfigured
ini file URL?
Yes
Device
reset
Download
configuration
files via TFTP
No
Run operational software
Version 4.8
85
January 2006
Mediant 3000
Note 1: The BootP/DHCP server should be defined with an ini file name when you
need to modify configuration parameters or when you're working with a large
Voice Prompt file that is not stored in non-volatile memory and must be
loaded after every reset.
Note 2: The default time duration between BootP/DHCP requests is set to 1 second.
This can be changed by the ini file parameter BootPDelay. Also, the default
number of requests is 3 and can be changed by the ini file parameter
BootPRetries, (both parameters can also be set using the Command Line
Switches in the BootP/TFTP Server).
Note 3: The ini file configuration parameters are stored in non-volatile memory after
the file is loaded. When a parameter is missing from the ini file, a default
value is assigned to this parameter and stored in non-volatile memory
(thereby overriding any previous value set for that parameter). Refer to
''Using BootP/DHCP'' on page 86 and the Appendix, ''BootP/TFTP Server''
on page 307.
Note 4: By default, the configuration files are stored in non-volatile memory. Use the
ini file parameter, 'SaveConfiguration=0', to refrain from storing the
configuration files in the non-volatile memory after loading.
6.3
Using BootP/DHCP
The Mediant 3000 uses the Bootstrap Protocol (BootP) and the Dynamic Host
Configuration Protocol (DHCP) to obtain its networking parameters and configuration
automatically after it is reset. BootP and DHCP are also used to provide the IP
address of a TFTP server on the network, and files (cmp and ini) to be loaded into
memory.
DHCP is a communication protocol that automatically assigns IP addresses from a
central point. BootP is a protocol that enables a device to discover its own IP address.
Both protocols have been extended to enable the configuration of additional
parameters specific to the Mediant 3000.
A BootP/DHCP request is issued after a power reset or after a device exception.
Note: BootP is normally used to initially configure the Mediant 3000. Thereafter,
BootP is no longer required as all parameters can be stored in the
gateways non-volatile memory and used when BootP is inaccessible. For
example, BootP can be used again to change the IP address of the
Mediant 3000.
6.3.1
BootP/DHCP Server Parameters

BootP/DHCP can be used to provision the following parameters (included in the
BootP/DHCP reply. Note that some parameters are optional):
User's Manual
IP address, subnet mask - These mandatory parameters are sent to the

MediaPack every time a BootP/DHCP process occurs.
Default gateway IP address - An optional parameter that is sent to the

MediaPack only if configured in the BootP/DHCP server.
86
User's Manual
TFTP server IP address - An optional parameter that contains the address of the
TFTP server from which the firmware (cmp) and ini files are loaded.
DNS server IP address (primary and secondary) - Optional parameters that

contain the IP addresses of the primary and secondary DNS servers. These
parameters are available only in DHCP and from Boot version 1.92.
Syslog server IP address - An optional parameter that is sent to the MediaPack

only if configured in the BootP/DHCP server. This parameter is available only in
DHCP.
Firmware file name An optional parameter that contains the name of the
firmware file to be loaded to the gateway via TFTP.
ini file name - An optional parameter that contains the name of the ini file to be
loaded to the gateway via TFTP.
Command Line Switches
In the BootP/TFTP Server, you can add command line switches in the Boot File field
(in the Client Configuration screen). Command line switches are used for various
tasks, such as to determine if the firmware should be burned on the non-volatile
memory or not. The table below describes the different command line switches.
To use a command line switch, take these 4 steps:

1.
In the Boot File field, leave the file name defined in the field as it is (e.g.,
ramxxx.cmp).
2.
Place your cursor after cmp.
3.
Press the space bar.
4.
Type in the switch you require (refer to the table below).
Example: ramxxx.cmp -fb to burn flash memory

ramxxx.cmp -fb -em 4 to burn flash memory and for Ethernet Mode 4 (autonegotiate)
The table below lists and describes the available switches.
Table 6-1: Command Line Switch Descriptions

Switch
Description
-fb
Burn ram.cmp in non-volatile memory. Only the cmp file (the compressed firmware
file) can be burned to the Mediant 3000's non-volatile memory. The hex file (the
uncompressed firmware file) can not be burned.
Version 4.8
87
January 2006
Mediant 3000
Table 6-1: Command Line Switch Descriptions

Switch
Description
-br
BootP retries:
1 = 1 BootP retry, 1 sec
2 = 2 BootP retries, 3 sec
15 = BootP retries indefinitely
Use this switch to set the number of BootP retries that the Mediant 3000 sends
during start-up. The Mediant 3000 stops issuing BootP requests when either an
AA122BootP reply is received or Number Of Retries is reached. This switch takes
effect only from the next Mediant 3000 reset.
-bd
BootP delays. 1 = 1 sec (default), 2 = 10 sec, 3 = 30 sec, 4 = 60 sec, 5 = 120 sec.

This sets the delay from the Mediant 3000s reset until the first BootP request is
issued by the Mediant 3000. The switch only takes effect from the next reset of the
Mediant 3000.
-bs
Selective BootP
-be
Use -be 1 for the Mediant 3000 to send client information that can be viewed in the
main screen of the BootP/TFTPname (refer tthe figure, Client Configuration Screen,
showing BootP/TFTP Servers main screen with the column 'Client Info' on the
extreme right). Client Info can include IP address, number of channels (in the case
of AudioCodes' media gateways), which cmp file is burned into the Mediant 3000's
non-volatile memory, etc.
Note: After programming a new cmp software image file, all configuration
parameters and tables are erased. Reprogram them by downloading the
ini file.
User's Manual
Configuration (ini) file name - The ini file is a proprietary configuration file with
an ini extension, containing configuration parameters and tables. For more
information on this file, refer to ''Configuration Parameters and Files'' on page 91.
When the Mediant 3000 detects that this optional parameter field is defined in
BootP, it initiates a TFTP process to load the file into the Mediant 3000. The new
configuration contained in the ini file can be stored in the Mediant 3000's integral
non-volatile memory. Whenever the Mediant 3000 is reset and no BootP reply is
sent to the board or the ini file name is missing in the BootP reply, the Mediant
3000 uses the previously stored ini file.
88
User's Manual
6.3.2
Host Name Support

From Boot software version 1.92 and above, the Mediant 3000 registers a devicespecific Host Name on the DNS server by defining the Host Name field of the DHCP
request. The host name is set to acl_nnnnnnn, where nnnnnnn is the serial number
of the Mediant 3000 (the serial number is equal to the last 6 digits of the MAC address
converted from Hex to decimal). The DHCP server registers this Host Name on the
DNS server. This feature allows users to configure the Mediant 3000 via the Web
Browser by providing the following URL: http://ACL_<serial number> (instead of
using the boards IP address).
6.3.3
Selective BootP
The Selective BootP mechanism, available from Boot version 1.92, allows the integral
BootP client to filter out unsolicited BootP replies. This can be beneficial for
environments where more than one BootP server is available and only one BootP
server is used to configure devices.
6.3.4
To activate this feature, add the command line switch -bs 1 to the Firmware File
Name field.
To deactivate, use -bs 0. When activated, the Mediant 3000 accepts only BootP
replies containing the text AUDC in the Vendor Specific Information field.
Vendor Specific Information

The Mediant 3000 uses the Vendor Specific Information field in the BootP server to
provide device-related initial startup parameters (according to RFC 1533). This field is
not available in DHCP servers. The field is disabled by default.
To enable / disable this feature user can do one of the following:
a.
Set the ini file parameter 'ExtBootPReqEnable' = 0 to disable, or 1 to enable.
b.
Use the -be command line switch in the Boot file field in the BootP server as
follows: ramxxx.cmp -be 0 to disable, or -be 1 to enable.
The table below details the Vendor Specific Information field according to the Mediant
3000:
Table 6-2: Vendor Specific Information Field Tags

Tag #
Description
Value
220
Board Type
#02
221
Current IP Address
XXX.XXX.XXX.XXX
222
Burned Boot Software Version
X.XX
223
Burned CMP Software Version
XXXXXXXXXXXX
12
224
Geographical Address
0 - 31
225
Chassis Geographical Address
0 - 31
226
TPM ID
N/A
Version 4.8
89
Length (bytes)
January 2006
Mediant 3000
Table 6-2: Vendor Specific Information Field Tags

Tag #
Description
Value
Length (bytes)
227
Rear I/O Version
N/A
228
Indoor - Outdoor
N/A
(Indoor is valid for FXS only. FXO

is always Outdoor.)
229
E&M
N/A
230
Analog Channels
N/A
The structure of the Vendor Specific Information field is demonstrated in the table
below.
Vendor-Specific
Information Code
Length Total
Tag Num
Length
Value
Tab Num
Length
Value
Tag Num
Length
Value (1)
Value (2)
Value (3)
Value (4)
Tag End
Table 6-3: Example of Vendor Specific Information Field Structure
42
12
220
02
227
221
10
70
255
6.3.5
Microsoft DHCP/BootP Server

The Mediant 3000 can be configured with a third party BootP server (besides
AudioCodes' BootP/TFTP Server), including the Microsoft DHCP server, to provide
the TP-6310 with an IP address and other initial parameter configurations.
To configure the Microsoft Windows NT DHCP Server to configure an IP address
to BootP clients, add a reservation for each BootP client.
For information on how to add a reservation, view the "Managing Client Reservations
Help" topic in the DHCP Manager.
The reservation builds an association between MAC address (12 digits), provided in
accompanying product documentation) and the IP address. Windows NT Server
provides the IP address based on the TP-6310 MAC address in the BootP request
frame.
To configure the Microsoft Windows NT DHCP server to provide Boot File
information to BootP clients, edit the BootP Table in the DHCP Manager. The BootP
Table is located in the Server Properties dialog, accessed from the Server menu. For
information on editing the BootP Table, view the "BootP Table" Help topic in the
DHCP Manager.
The following parameters must be specified:
User's Manual
90
User's Manual
Local IP address - The Mediant 3000s IP address
Subnet mask
Gateway IP address - Default Gateway IP address
BootP File name - Optional (refer to the following Note)
Note: The BootP File field should normally not be used. The field is only used for
software upgrade (refer to ''Upgrading Mediant 3000 Software'' on page
100).
6.4
Configuration Parameters and Files

The Mediant 3000's configuration is stored in two file groups.
The Initialization file - an initialization (ini) text file containing configuration

parameters of the Mediant 3000.
The auxilliary files - dat files containing the raw data used for various tasks such
as Call Progress Tones, Voice Prompts, logo image, etc.
These files contain factory-pre-configured parameter defaults when supplied with the
Mediant 3000 and are stored in the Mediant 3000's non-volatile memory. The Mediant
3000 is started up initially with this default configuration. Subsequently, these files can
be modified and reloaded using either of the following methods:
via BootP/TFTP during the startup process (refer to ''Using BootP/DHCP'' on

page 86 and the Appendix, ''BootP/TFTP Server'' on page 307).
via the Embedded Web Server (refer to ''Embedded Web Server'' on page 202).
The modified auxiliary files can be burned into the non-volatile memory (refer to the
SaveConfiguration parameter in ''Downloading Auxiliary Files'' on page 97) so that the
modified configuration is utilized with subsequent resets. The configuration file is
always stored on the non-volatile memory. There in no need to repeatedly reload the
modified files after reset.
Note 1: Users who configure the Mediant 3000 with the Embedded Web Server do
not require downloading the ini file and have no need to utilize a TFTP
server.
Note 2: SNMP users configure the Mediant 3000 via SNMP. Therefore a very small
ini file is required which contains the IP address for the SNMP traps.
6.4.1
Initialization (ini) File

The ini file name must not include hyphens or spaces. Use Underscore instead.
The ini file can contain a number of parameters. The ini file structure supports the
following parameter value constructs:
Version 4.8
Parameter = Value (refer to 'Parameter = Value Constructs'). The lists of

parameters are provided in the Appendix, ''Individual 'ini 'File Parameters'' on
page 315.
91
January 2006
Mediant 3000
Tables of Parameter Value (refer to ''Table of Parameter Value Constructs'' on

page 94).
The example below shows a sample of the general structure of the ini file for both the
Parameter = Value and Tables of Parameter Value Constructs.
[Sub Section Name]
Parameter_Name = Parameter_Value
Parameter_Name = Parameter_Value
.
..
; REMARK
[Sub Section Name]
...
; Tables Format Rules:
[Table_Name]
; Fields declaration
Format Index_Name_1 ... Index_Name_N = Param_Name_1 ...
Param_Name_M
; Table's Lines (repeat for each line)
Table_Name Index_1_val ... Index_N_val = Param_Val_1 ...
Param_Val_M
[\Table_Name]
6.4.1.1
Parameter Value Structure

The following are the rules in the ini File structure for individual ini file parameters
(Parameter = Value):
Lines beginning with a semi-colon ';' (as the first character) are ignored.
An Enter must be the final character of each line.
The number of spaces before and after "=" is not relevant.
If there is a syntax error in the parameter name, the value is ignored.
Syntax errors in the parameter value field can cause unexpected errors (because
parameters may be set to the incorrect values).
Sub-section names are optional.
String parameters, representing file names, for example,

CallProgressTonesFileName, must be placed between two inverted commas
('').
The parameter name is NOT case sensitive; the parameter value is not case
sensitive except for coder names.
Numeric parameter values should be entered only in decimal format.
The ini file should be ended with one or more Enters.
ini File Examples

The example below shows a sample ini file for MGCP.
[TDM BUS configuration]
User's Manual
92
User's Manual
; 1=aLaw 3=ulaw
PCMLawSelect = 1
BaseUDPPort = 4000
[Trunk Configuration]
; E1_euro_isdn
ProtocolType = 1
; USER_TERMINATION_SIDE
TerminationSide = 0
; EXTENDED_SUPER_FRAME
FramingMethod = 0
;HDB3
LineCode = 2
[MGCP]
EndpointName = 'ACgw'
CallAgentIP = 10.1.2.34
[Channel Params]
DJBufferMinDelay = 75
RTPRedundancyDepth = 1
[Files]
CallProgressTonesFilename = 'CPUSA.dat'
VoicePromptsFilename = 'tpdemo_723.dat'
CasFilename = 'E_M_WinkTable.dat'
Trace Level = 0
The example below shows a sample ini file for MEGACO.
[MEGACO]
; List of Call agents, separated by ','. The default is the loading
computer.
PROVISIONEDCALLAGENTS = 10.2.1.254
; List of ports for the above Call Agents, separated by ','. The
default is 2944.
PROVISIONEDCALLAGENTSPORTS = 2944
; IP of the LOG server
LOGSERVERIP = 10.2.1.254
; The next 3 field are the parts of the termination name. For
example, if you wish the
; name to look like: 'gw3/tr0/ep1', you shall define: ;GATEWAYNAME
= 'gw3/',
; TRUNKNAME = 'tr', and ENDPOINTNAME = 'ep' . The RTP in built from
the GATEWAYNAME,
; the string 'RTP' and a number. In this example it shall be: gw3/
RTP0.;
GATEWAYNAME = 'c4'
TRUNKNAME = 's'
ENDPOINTNAME = 'c'; This parameter activates MEGACO. If omitted,
MGCP will be active
MGCONTROLPROTOCOLTYPE = 2
; The following disables the keep-alive mechanism if set to 0, else
it is enabled
KEEPALIVEENABLED = 1
;
; This parameter defines the profile used. 1 - is for version 2, 2
- for version 1
MGCPCOMPATIBILITYPROFILE = 2
Version 4.8
93
January 2006
Mediant 3000
Note: Before loading an ini file to the Mediant 3000, make sure that the extension
of the ini file saved on your PC is correct: Verify that the checkbox Hide
extension for known file types (My Computer>Tools>Folder Options>View)
is unchecked. Then, verify that the ini file name extension is xxx.ini and NOT
erroneously xxx.ini.ini or xxx~.ini.
The lists of individual ini file parameters are provided in the Appendix, ''Individual 'ini'
File Parameters'' on page 315.
6.4.1.2
Tables of Parameter Value Structure

Tables group the related parameters of a given entity. Tables are composed of rows
and columns. The columns represent parameters types, while each row represents an
entity. The parameters in each row are called the line attributes. Rows in table may
represent (for example) a trunk, SS7 Link, list of timers for a given application, etc.
Examples of the structure of the tables are provided below. For a list of supported
tables please refer to the 'Appendix - Table Parameters' on page 387.
[ SS7_SIG_INT_ID_TABLE ]
FORMAT SS7_SIG_IF_ID_INDEX = SS7_SIG_IF_ID_VALUE,
SS7_SIG_IF_ID_NAME, SS7_SIG_IF_ID_OWNER_GROUP, SS7_SIG_IF_ID_LAYER,
SS7_SIG_IF_ID_NAI, SS7_SIG_M3UA_SPC;
SS7_SIG_INT_ID_TABLE 1 = 101, AMSTERDAM1, 3, 3, 1, 4;
SS7_SIG_INT_ID_TABLE 5 = 100, BELFAST12, 3, 3, 0, 11;
[ \SS7_SIG_INT_ID_TABLE ]
This tables below are shown in document format for description purposes:
Table 6-4: Table Structure Example
IF ID Index
IF ID Value
SS7_SIG_IF
SS7_SIG_IF _ID_OWNE SS7_SIG_IF SS7_SIG_IF SS7_SIG_M
_ID_NAME R_GROUP
_ID_LAYER _ID_NAI
3UA_SPC
101
AMSTERDA
M1
100
BELFAST12
11
6.4.1.2.1
Table Structure Rules

Tables are composed of four elements:
User's Manual
Table-Title - The Table's string name in square brackets. In the example above,
the Table Title is: [ SS7_SIG_INT_ID_TABLE ].
Format Line - This line specifies the table's fields by their string names. In the
example above, the format line is: FORMAT SS7_SIG_IF_ID_INDEX =
SS7_SIG_IF_ID_VALUE, SS7_SIG_IF_ID_NAME,
SS7_SIG_IF_ID_OWNER_GROUP, SS7_SIG_IF_ID_LAYER,
SS7_SIG_IF_ID_NAI, SS7_SIG_M3UA_SPC
94
User's Manual
The first word MUST be "FORMAT", followed by indices field names, and
after '=' sign, all data fields names should be listed.
Items must be separated by ',' sign.
The Format Line must end with ';' sign.
Data Line(s) - The actual values for parameters are specified in each Data line.
The values are interpreted according to the format line. The first word must be the
table's string name.
Items must be separated by a ',' sign.
A Data Line must end with a ';' sign.
Indices (in both the Format line and the Data lines) must all appear in order,
as determined by the table's specific documentation. The Index field must
NOT be omitted. Each row in a table must be unique. For this reason, each
table defines one or more Index fields. The combination of the Index fields
determines the 'line-tag'. Each line-tag may appear only once. In the
example provided in the table above, Table Structure Example', there is only
one index field. This is the simplest way to mark rows.
Data fields in the Format line may use a sub-set of all of the configurable
fields in a table only. In this case, all other fields are assigned with the predefined default value for each configured line.
The order of the Data fields in the Format line is not significant (unlike the
Index-fields). Field values in Data lines are interpreted according to the order
specified in the Format line.
The sign '$$' in the Data line means that the user wants the pre-defined
default value assigned to the field for the given line.
The order of Data lines is insignificant.
Data lines must match the Format line, i.e. it must contain exactly the same
number of Indices and Data fields and should be in exactly the same order.
A line in a table is identified by its table-name and its indices. Each such line
may appear only once in the ini file.
End-of-Table-Mark: Marks the end of a table. Same as Table title, but string
name is preceded by '\'.
Below is an example of the table structure in an ini file.

; Table: Items Table.
; Fields: Item_Name, Item_Serial_Number, Item_Color, Item_weight.
; NOTE: Item_Color is not specified. It will be given default
value.
[Items_Table]
; Fields declaration
Format Item_Index = Item_Name, Item_Serial_Number, Item_weight;
Items_Table 0 = Computer, 678678, 6;
Items_Table 6 = Computer-screen, 127979, 9;
Items_Table 2 = Computer-pad, 111111, $$;
[\Items_Table]
Version 4.8
95
January 2006
Mediant 3000
6.4.1.2.2
Tables in the Uploaded ini File

Tables are grouped according to the applications they configure. For example, several
tables are required to configure SS7, and other tables are required to configure ATM
(if available).
When uploading the ini file, the policy is to include only tables that belong to
applications, which have been configured. (Dynamic tables of other applications are
empty, but static tables are not.) The trigger for uploading tables is further
documented in the applications' specific sections.
6.4.1.2.3
Secret Tables
A table is defined as a secret table if it contains at least one secret data field or if it
depends on such a table. A secret data field is a field that must not be revealed to the
user. An example of a secret field can be found in an IPSec application. The IPsec
tables are defined as secret tables because the IKE table contains a pre-shared key
field, which must not be revealed. The SPD table depends on the IKE table.
Therefore, the SPD table is defined as a secret table.
There are two major differences between tables and secret tables:
The secret field itself can not be viewed via SNMP, Web Server or any other tool.
ini File behavior: These tables are never uploaded in the ini File (e.g., 'Get INIFile from WEB'). Instead, there is a commented title that states that the secret
table is present at the board, and is not to be revealed.
Secret tables are always kept in the boards non-volatile memory, and may be
over-written by new tables that should be provided in a new ini File. If a secret
table appears in an ini File, it replaces the current table regardless of its content.
The way to delete a secret table from a board is, for example, to provide an
empty table of that type (with no data lines) as part of a new ini File. The empty
table replaces the previous table in the board.
6.4.1.3
Secured Configuration File Download

The ini file contains sensitive information required for appropriate functioning of the
Mediant 3000. The ini file is uploaded to the Mediant 3000 or downloaded from the
gateway using TFTP or HTTP protocols. These protocols are unsecured (and thus
vulnerable to a potential hacker). Conversely, if the ini file is encoded, the ini file
would be significantly less vulnerable to outside harm.
6.4.1.3.1
Encoding Mechanism
The ini file to be loaded and retrieved could be available as is or encoded. When an
encoded ini file is downloaded to the Mediant 3000, it is also retrieved encoded from
the Mediant 3000 as well. When a decoded file is downloaded to the Mediant 3000, it
is also retrieved decoded from the Mediant 3000 as well.
The ini file to be loaded and retrieved is available with or without encoding. When an
encoded ini file is downloaded to the Mediant 3000, it is retrieved as encoded from the
Mediant 3000 as well. When a decoded file is downloaded to the Mediant 3000, it is
retrieved as decoded from the Mediant 3000 as well.
In order to create an encoded ini file, the user must first create an ini file and then
apply the DConvert utility to it in order to encode it. (Refer to the Appendix, ''Utilities''
on page 495 for detailed instruction on ini file encoding.)
User's Manual
96
User's Manual
In order to decode an encoded ini file retrieved from the Mediant 3000, the user must
retrieve an encoded ini file from the Mediant 3000 using the Web server (refer to
"Downloading Auxiliary Files" below) and then use the DConvert utility in order to
decode it. (Refer to the Appendix, ''Utilities'' on page 495 for detailed instruction on
decoding the ini file.)
Downloading the ini file with or without encoding may be performed by utilizing either
TFTP or HTTP.
6.4.2
Auxiliary Files
The auxiliary files are dat files each containing the raw data used for a certain task
such as Call Progress Tones, Voice Prompts, logo image, etc. The dat files are
created using the DConvert utility (refer to the Appendix, ''Utilities'' on page 495),
which converts auxiliary source files into dat files. Some sample auxiliary source files
are available in the software package under: .\ Auxiliary_Files\. dat files. These dat
files are downloaded to the Mediant 3000 using TFTP (see below) or HTTP via the
Software Upgrade Wizard (refer to ''Upgrading Mediant 3000 Software'' on page 100.)
This section describes the various types of auxiliary files.
Note: The auxiliary source files use the same ini file extension type as the ini
configuration file, however, the functionality is different. Whenever the
term, "ini file" is used, it refers to the configuration file and NOT to the
auxiliary files.
6.4.2.1
Downloading Auxiliary Files via TFTP During the Board Startup

Each auxiliary file has a corresponding ini file parameter in the form of
[AuxilaryFileType]FileName. This parameter takes the name of the auxiliary file to be
downloaded to the Mediant 3000. If the ini file does not contain a parameter for a
specific auxiliary file type, the Mediant 3000 uses the last auxiliary file that was stored
on the non-volatile memory. The SaveConfiguration ini file parameter enables storing
the auxiliary files on the non-volatile memory.
The following list contains the ini file parameters for the different types of auxiliary files
that can be downloaded to the Mediant 3000:
VoicePromptsFileName - The name (and path) of the file containing the voice
prompts. This file should be constructed using the TrunkPack Conversion Utility
supplied as part of the software package on the CD accompanying the Mediant
3000. The Voice Prompt buffer size in the board is 10 Mbytes.
The Voice Prompt buffer size is also controlled by the software upgrade key. For
more information contact an AudioCodes representative.
Version 4.8
CallProgressTonesFilename - The name (and path) of the file containing the

Call Progress and User-Defined Tones definition.
"PrerecordedTonesFileName" - The name (and path) of the file containing the

Prerecorded Tones. This file should be constructed using the "TrunkPack
Conversion Utility" supplied as part of the software package on the CD
accompanying the Mediant 3000
CASFileName_0CASFileName_7 (or CASFileName) - The names (and

path names) of the files containing the CAS protocol configuration. It is possible
to use 1 to 8 files. The CASFileName name is still supported and can be used
instead of the enumerated names when using only one CAS protocol file.
97
January 2006
Mediant 3000
6.4.3
CASTablesNum - Indicates how many CAS protocol configuration files are

loaded. Its range is 1-8. It should match the number of CASFileName_X fields.
CASTableIndex_TrunkNum (TrunkNum should be an integer) - This field is a

CAS protocol file index. It indicates the CAS protocol file to use in a specific
Trunk. The index value corresponds to the number in the field CASFileName_X.
SaveConfiguration - (default = 1 = enabled) This parameter replaces the following

parameters: BlastCallProgressSetupFile, BlastCASProtocolSetupFile,
BlastVoicePromptsFile. When enabled, all configuration and downloadable files
are stored in non-volatile memory.
Automatic Update Facility

The Mediant 3000 is capable of automatically downloading updates to the ini file,
auxiliary files and firmware image. Any standard Web server, FTP server or NFS
server may be used to host these files.
The Automatic Update processing is performed:
Upon Mediant 3000 start-up (after the Mediant 3000 is operational)
At a configurable time of day, e.g., 18:00 (disabled by default)
At fixed intervals, e.g., every 60 minutes (disabled by default)
The Automatic Update process is entirely controlled by configuration parameters in the

ini file. During the Automatic Update process, the Mediant 3000 contacts the external
server and requests the latest version of a given set of URLs. An additional benefit of
using HTTP (Web) servers is that configuration ini files would be downloaded only if
they were modified since the last update.
The following is an example of an ini file activating the Automatic Update facility.
# DNS is required for specifying domain names in URLs
DnsPriServerIP = 10.1.1.11
# Load extra configuration ini file using HTTP
INIFILEURL = 'http://webserver.corp.com/AudioCodes/inifile.ini'
# Load call progress tones using HTTPS
CPTFILEURL = 'https://10.31.2.17/usa_tones.dat'
# Load voice prompts, using user "root" and password "wheel"
VPFILEURL = 'ftps://root:wheel@ftpserver.corp.com/vp.dat'
# Update every day at 03:00 AM
AutoUpdatePredefinedTime = '03:00'
Notes on Configuration URLs:
User's Manual
Additional URLs may be specified, as described in the ''System Parameters'

table' on page 316.
Updates to non-ini files are performed only once. To update a previously-loaded

binary file, you must update the ini file containing the URL for the file.
To provide differential configuration for each of the devices in a network, add the
string "<MAC>" to the URL. This mnemonic is replaced with the hardware (MAC)
address of the Mediant 3000.
To update the firmware image using the Automatic Update facility, use the
CMPFILEURL parameter to point to the image file. As a precaution (in order to
98
User's Manual

protect the Mediant 3000 from an accidental update), you must also set
AUTOUPDATECMPFILE to 1.
The following example illustrates how to utilize Automatic Updates for deploying
devices with minimum manual configuration.
To utilize Automatic Updates for deploying the Mediant 3000 with

minimum manual configuration, take these 6 steps:
1.
Set up a Web server (in this example it is http://www.corp.com/) where all the
configuration files are to be stored.
2.
On each device, pre-configure the following setting: (DHCP/DNS are assumed)
INIFILEURL = 'http://www.corp.com/master_configuration.ini'
3.
Create a file named master_configuration.ini, with the following text:
# Common configuration for all devices

# -----------------------------------CptFileURL = 'http://www.corp.com/call_progress.dat'
# Check for updates every 60 minutes
AutoUpdateFrequency = 60
# Additional configuration per device
# ----------------------------------# Each device will load a file named after its MAC address,
# e.g. config_00908F033512.ini
IniFileTemplateURL = 'http://www.corp.com/config_<MAC>.ini'
# Reset the device after configuration has been updated.
# The device will reset after all files were processed.
RESETNOW = 1
4.
You may modify the master_configuration.ini file (or any of the config_<MAC>.ini
files) at any time. The Mediant 3000 queries for the latest version every 60
minutes, and applies the new settings immediately.
5.
For additional security, usage of HTTPS and FTPS protocols is recommended.

The Mediant 3000 supports HTTPS (RFC2818) and FTPS using the AUTH TLS
method ((RFC4217) for the Automatic Update facility.
6.
To download configuration files from an NFS server, the file system parameters
should be defined in the configuration ini file. The following is an example of a
configuration ini file for downloading files from NFS servers using NFS version 2:
# Define NFS servers for Automatic Update
[ NFSServers ]
FORMAT NFSServers_Index = NFSServers_HostOrIP, NFSServers_RootPath,
NFSServers_NfsVersion;
NFSServers 1 = 10.31.2.10, /usr/share, 2 ;
NFSServers 2 = 192.168.100.7, /d/shared, 2 ;
[ \NFSServers ]
CptFileUrl = 'file://10.31.2.10/usr/share/public/usa_tones.dat'
VpFileUrl =
'file://192.168.100.7/d/shared/audiocodes/voiceprompt.dat'
Version 4.8
99
January 2006
Mediant 3000
6.5
Backup Copies of ini and Auxiliary Files

Be sure to separately store a copy of the ini file and all auxiliary files, as well as a note
of the software version for use should a board require replacement.
6.6
Upgrading Mediant 3000 Software

To upgrade the Mediant 3000's firmware, load the upgraded firmware cmp file into the
Mediant 3000 (and optionally burn it into integral non-volatile memory) using:
1.
Embedded Web Server - For a complete description of this option refer to'
'Software Upgrade Wizard'' on page 266.
2.
BootP/TFTP Server - By using the -fb BootP command line switch, the user can
direct the board to burn the firmware on the non-volatile memory. The board
thereby downloads the specified firmware name via TFTP and also burns the
firmware on the non-volatile memory. Refer to the Appendix, ''BootP/TFTP
Server'' on page 307.
Note: Upgrading the Mediant 3000's firmware requires reloading the ini file and
reburning the configuration files. A Software Upgrade Key may be required if
the new firmware's version is greater than that listed in the Software
Upgrade Key menu (refer to ''Software Upgrade Wizard'' on page 266.).
6.7
Initializing the Mediant 3000 System in High

Availability Mode
For the Mediant 3000 system to be set up for High Availability, the following
installation phases must be carried out:
6.8
Hardware configuration setup as described in 'Cabling the Mediant 3000' on page

61. The system can be set up initially with only one TP-6310 board and one
SA/M3K board, however, High Availability mode is only functional with a second
TP-6310 board and SA/M3K board is added.
The feature key includes the Mediant 3000 high availability feature and is
installed on both of the TP-6310 boards. Refer to 'Software Upgrade Key - Web
Sever' on page 273. (If the High Availability feature was specified at the time the
system was purchased, then it is already included on both of the boards).
The M3KGlobalIpAddr board parameter is set (burned to flash or received by the

ini file) in the active board to a valid IP address that is different than the local IP
address of the TP-6310 boards, but with the same subnet. Refer to 'Assigning the
Mediant 3000 IP Address' on page 81.
Mediant 3000 System Initilization Process

Each TP-6310 board is initialized as Active or Redundant according to its placement in
the chassis and the status of the SDH/ATM interfaces. Refer to 'Mediant 3000
Chassis' on page 30.
User's Manual
100
User's Manual
An Active TP-6310 board is identified by a green light in ACT led on the TP-6310 front
panel. Refer to the 'TP-6310 Board Diagram ' on page 34 and 'TP-6310 Board Panel
LED Indicators' on page 36.
Synchronization between active and redundant TP-6310 boards can take several
minutes in which the active TP-6310 board forwards to the redundant TP-6310 board,
all its current configuration data, including files such as voice prompt, call progress
tone and even its software (cmp file). If necessary, a second boot of the redundant
TP-6310 board is issued in order to apply the new configuration.
After the synchronization has ended, the redundant TP-6310 board is identified by a
blinking yellow light in ACT led. Refer to the 'TP-6310 Board Diagram ' on page 34
and 'TP-6310 Board Panel LED Indicators' on page 36.
The redundant TP-6310 board is disconnected from the external network and has an
internal connection with the activeTP-6310 board only. This means that the user does
not interact directly with the redundant TP-6310 board.
6.9
Special Mediant 3000 System Specific Behavior
6.9.1
Rebooting the Redundant TP-6310 Board

To assure that the Redundant TP-6310 board is operating with the same software
version and configuration it received from the active TP-6310 board, the Redundant
TP-6310 board is set to reboot only from its flash and not from the BootP/DHCP.
6.9.2
High Availability and SysLog

All High Availability main operations and events are printed to the SysLog with the
prefix: "M3K_HA".
All SysLog messages and events of the redundant TP-6310 board are printed to the
SysLog by the active TP-6310 board with the appropriate message prefix.
6.10
Actions upon Detecting Board Failure
6.10.1
Failure in Active Board

In the event that an Active board fails, the Redundant (Standby) board issues a
switch-over operation. As part of this switch-over operation, the failed board is reset
and the initially Redundant (Standby) board become the Active board in non-High
Availability mode, until a redundant board is detected.
If the failure in the active board is fixed after reset, it is initialized as the redundant
board and the Mediant 3000 system returns to High Availability mode.
Version 4.8
101
January 2006
Mediant 3000
6.10.2
Failure in a Redundant Board

In the event that an Redundant board fails, the Active board resets the redundant
board and move itself to non-High Availability mode until the redundant board is
returned to functional operation.
If the failure in the redundant board is fixed after reset, it is initialized as the redundant
board again and the Mediant 3000 system returns to High Availability mode..
User's Manual
102
User's Manual
7. Standard Control Protocols
Standard Control Protocols

Mediant 3000 can be controlled from a Media Gateway Controller (MGC)/Call Agent
using standard MGCP (Media Gateway Control Protocol), MEGACO (Media Gateway
Control) protocol and AudioCodes proprietary VoPLib API (over PCI or over TPNCP.
For information on TPNCP, refer to the section on TPNCP in VoPLib Application
Developer's Manual, Document #: LTRT-844xx).
7.1
MGCP Control Protocol
7.1.1
MGCP Overview
MGCP (Media Gateway Control Protocol) is a standards-based network control
protocol (based on the IETF RFC 3435 and RFC 3660 located on the IETF web site).
MGCP assumes a call control architecture where the call control intelligence is outside
the Mediant 3000 and handled by an external Call Agent. MGCP is a master/slave
protocol, where the Mediant 3000 is expected to execute commands sent by the Call
Agent.
Since this is a standards-based control protocol, AudioCodes does not provide any
special software library to enable users to construct their own Call Agent. The user is
able to choose any one of many such stacks available in the market.
Note: MGCP and MEGACO protocols cannot co-exist on the same Mediant
3000.
Devices that support the <XPCI> interface can be operated in different hybrid
modes. For example, the device can be configured using the regular acOpenBoard()
function (used from an application running in the same host machine in which the
device is installed). Users can start to control it from a remote application using
MGCP.
7.1.2
MGCP Operation
7.1.2.1
Executing MGCP Commands

MGCP commands, received from an external Call Agent through the IP network, are
decoded and executed in the Mediant 3000. Commands can create new connections,
delete connections, or modify the connection parameters.
Several commands support the basic operations required to control the Mediant 3000:
Version 4.8
Connection commands - Allow the application to create new connections, delete

existing connections inside the Mediant 3000, and modify connection parameters.
Notify commands - Using notifications, the Mediant 3000 can inform the Call
Agent of events occurring on one or more of the Endpoints. Notify commands can
also generate signals on the Endpoints.
103
January 2006
Mediant 3000
7.1.3
Audit commands - These commands are used to query the Mediant 3000 about
Endpoint configuration and state. This information helps in managing and
controlling the Mediant 3000.
MGCP Call Agent Configuration

There are two alternative methodologies to configure the Call Agents IP address:
1.
Resolving the host name FQDN address through the DNS server - The DNS
server can return a single IP address or a list of up to 10 IP addresses
If the host name is set as the Call Agent, the restart procedure is complete only if
the DNS returns the DNS query successfully, in which resolving the host name
succeeds and the Gateway has the IP address.
If resolving the host name fails, the Gateway keeps trying to resolve it until the
DNS returns the resolution successfully and a valid IP address is issued.
If first IP address in the DNS list stops responding, the retransmission mechanism
continues trying to send its commands to next IP address in the DNS list.
The DNS look up methodology ini file configuration:
CallAgentDomainName = 'domain name'

DNSPRISERVERIP = IP address
DNSSECSERVERIP = IP address
CallAgentPort = Port number
The CallAgentIP and RedundantAgentIP parameters are ignored

2.
Configuring primary and secondary IP addresses - If the primary IP stops

responding, the retransmission mechanism tries sending its commands to the
secondary IP (if the secondary IP is configured).
The IP addresses methodology ini file configuration:
CallAgentDomainName = '' (two single commas mentioning this is an

empty string)
CallAgentIP = IP address A
RedundantAgentIP = IP address B
CallAgentPort = Port A
RedundantAgentPort = Port B
7.1.4
Configuration and Update of the Endpoint's Notified Entity

All endpoints used by the same gateway can hold up to 20 different FQDN addresses.
All commands containing the twenty-first or higher FQDN are rejected using the error
code 502. If an IP address is used to identify notified entities, the number of IP
addresses is limited to the number of endpoints, e.g., each endpoint may hold a
different IP address of its notified entity.
The notified entity configuration is done using the N: line in accordance with RFC
3435.
User's Manual
104
User's Manual
7.1.5
MGCP KeepAlive Mechanism

The KeepAlive mechanism maintains a constant connection with the Call Agent. In
case of a Call Agent failure, the Mediant 3000 will enter into a disconnected state and
will switch over to its redundant Call Agent. Moreover, since constant transportation is
running between the Call Agent and the Mediant 3000, using the KeepAlive
mechanism gives VoIP networks the ability to work with NAT machines.
While the KeepAlive mechanism is enabled, the Mediant 3000 sends an RSIP
command when it detects a time interval without commands received from the Call
Agent.
The KeepAlive mechanism deactivates itself when the Mediant 3000 loses connection
with the Call Agent. KeepAlive messages are sent immediately following the
reestablishment of the connection and when no other commands are received during
the KeepAlive interval.
KeepAlive ini file parameters:
KeepAliveEnabled = 1 (on) or 0 (off, by default) - This parameter can be used to
enable a KeepAlive message (NOP ServiceChange).
KeepAliveInterval = 12 by default - This parameter is used to define the interval in
seconds of a KeepAlive message
KeepAlive examples:
While working in endpoint naming conventions:
RSIP 2200 *@audiocodes.com MGCP 1.0
RM: X-KeepAlive
While working in trunk naming conventions:
RSIP 2420 ds/tr/*/*@audiocodes.com MGCP 1.0
RM: X-KeepAlive
7.1.6
MGCP Piggy-Back Feature

The RFC 3435 and PacketCable specifications define a piggy-backing mechanism
that group commands according to their destination and send them as a single UDP
command.
This feature is set via the EnablePiggyBacking ini file parameter (default = ON, e.g.,
EnablePiggyBacking = 1).
If the piggy-back feature is active, all out going commands are kept in a buffer
according to its destination. Every 30 msec, all occupied buffers are cleared and all
commands held in the buffers are piggy-backed and sent according to the FIFO
methodology.
7.1.7
SDP Support in MGCP

MGCP supports basic SDP (Session Description Protocol), as defined in RFC 2327. It
also supports SDP-ATM, as defined in RFC 3108. However, the only supported
attributes in the SDP are:
Version 4.8
RTPMAP
Used for dynamic payload mapping, to map the number to the coder. The format
is:
105
January 2006
Mediant 3000
a=rtpmap: 97 G723/8000/1
Where:
97 is the payload number to be used
G723 is the codec name
8000 is the clock rate (optional)
1 is the number of channels (optional)
FMTP
Used for dynamic payload mapping, to define coder specific parameters. The
format is:
a=fmtp:
97 bitrate=5.3
Where:
Bitrate is a parameter of the G.723 coder.
Other supported parameters are:
mode-set - Defines which mode is used for the AMR and the XNETCODER
coder (0-7)
annexa - Refers to G.723 if silence suppression is on (yes or no)
annexb - Refers to G.729 if silence suppression is on (yes or no)
Note: Additional extensions to the SDP are also supported.
7.1.8
MGCP Fax
7.1.8.1
MGCP Fax Configuration

MGCP offers the following Fax configurations.
MGCP Fax package
Proprietary change-fax-transport type in the local connection options (refer to'

'Fax Transport Type Setting with Local Connection Options'' on page 109)
enables changing the fax transport type without using the T.38 fax package.
MGCP Fax profile Display Fax Port on Second SDP M Line (refer to ''MGCP
Profiling'' on page 109). enables negotiating the T.38 fax port without using the
T.38 fax package.
Table 7-1: MGCP Fax Package Gateway Mode

Gateway CH 0
Call Agent
Gateway CH 1
200 17501 OK
RQNT 17501
ACgw0@[10.4.4.129] MGCP
1.0
X: 12
S: L/dl
R: D/X(D)
D: 2xxx
NTFY 2075
User's Manual
200 2075 OK
106
User's Manual

Gateway CH 0
Call Agent
Gateway CH 1
ACgw0@[10.4.4.129] MGCP 1.0

X: 12
O: 2580
200 17502 OK
I: 34
CRCX 17502
ACgw0@[10.4.4.129] MGCP
1.0
C: 1
v=0
o=- 767771419 0 IN IP4
10.4.4.129
s=c=IN IP4 10.4.4.129
L: a:PCMA , fxr/fx:gw
M: recvonly
X: 12
R: fxr/gwfax
t=0 0
m=audio 4000 RTP/AVP 8
CRCX 17503
ACgw1@[10.4.4.129] MGCP
1.0
200 17503 OK
I: 35
C: 1
L: a:PCMA , fxr/fx:gw
v=0
o=- 1973242229 0 IN IP4
10.4.4.129
M: sendrecv
X: 12
s=-
R: fxr/gwfax
c=IN IP4 10.4.4.129

t=0 0
v=0
c=IN IP4 10.4.4.129

a=sqn: 0
a=cdsc: 1 audio RTP/AVP 8
a=cdsc: 22 image udptl t38
200 17504 OK
v=0
o=- 767771419 1 IN IP4
10.4.4.129
s=c=IN IP4 10.4.4.129
t=0 0
MDCX 17504
ACgw0@[10.4.4.129] MGCP
1.0
C: 1
I: 34
X: 12
R: fxr/gwfax
L: a:PCMA
M: sendrecv
Version 4.8
107
January 2006
Mediant 3000

Gateway CH 0
Call Agent
Gateway CH 1

v=0
c=IN IP4 10.4.4.129
a=sqn: 0
a=cdsc: 1 audio RTP/AVP 8
200 17505 OK
RQNT 17505
ACgw0@[10.4.4.129] MGCP
1.0
X: 12
R: fxr/gwfax
200 2076 OK
NTFY 2076
ACgw1@[10.4.4.129] MGCP 1.0
X: 12
O: FXR/gwfax(start)
RQNT 17506
ACgw1@[10.4.4.129] MGCP
1.0
200 17506 OK
X: 12
R: fxr/gwfax
NTFY 2077
ACgw0@[10.4.4.129] MGCP 1.0
200 2077 OK
X: 12
O: FXR/gwfax(start)
NTFY 2078
ACgw0@[10.4.4.129] MGCP 1.0
200 2078 OK
X: 12
O: FXR/gwfax(stop)
200 2079 OK
NTFY 2079
ACgw0@[10.4.4.129] MGCP 1.0
X: 12
O: FXR/gwfax(stop)
250 17507 OK
User's Manual
DLCX 17507
ACgw0@[10.4.4.129] MGCP
1.0
108
User's Manual

Gateway CH 0
7.1.9
Call Agent
Gateway CH 1
DLCX 17508
ACgw1@[10.4.4.129] MGCP
1.0
250 17508 OK
Fax Transport Type Setting with Local Connection Options

In addition to the T.38 Fax package described in ''Fax Package Definition - FXR'' on
page 130, the parameter, x-faxtranstype can set the Fax Transport Type of each
connection to either Transparent, Relay or Transparent with Events. If this parameter
is not placed in the Local Connection Options, (LCO) command, then the default value
configured by the ini file parameter is set.
Table 7-2: Fax Transport Type

Fax Mode
Description
x-faxtranstype:transparent
Fax events are ignored
x-faxtranstype:relay
Faxes are transmitted on T.38
x-faxtranstype:transparentwithevents
Fax is transmitted in-band and fax events are detected
7.1.9.1
Display Fax Port on Second M Line

This feature enables users to negotiate the T.38 fax port without using the T.38 fax
package. To set this feature, the FaxTransportType parameter in the ini file should be
configured to relay T.38. Avoid setting the fax transport type through the MGCP local
connects options field (such as in 'Fax Transport Type Setting with Local Connection
Options' above).
When this feature is enabled, an SDP response includes an additional media line such
as:
m=image 4342 udptl t38
This example indicates the T.38 fax port 4342 is used.
7.1.10
MGCP Profiling
MGCP uses profiles for saving backward compatibility and certain modes of MGCP
behavior. A MGCP profile can be set through the ini file MGCPCompatibilityProfile
parameter . Different profiles will be presented below. For further profiling information
please contact AudioCodes support personnel.
Version 4.8
109
January 2006
Mediant 3000
7.1.11
TGCP Compatibility
To use Trunking Gateway Control Protocol (TGCP) conventions, the user must set the
Mediant 3000 to the TGCP profile, e.g., adding MGCPCompatibilityProfile = 32 to the
Mediant 3000's ini file.
The following lists the supported TGCP additions:
7.1.12
Endpoint Naming Scheme - Supports wild card and Endpoint naming

conventions.
Endpoint Name Retrieval - Wild-carded Audit endpoint command supports

MaxEndPointIDs, and NumEndPoints parameters.
Supported Versions - The RestartInProgress response and the AuditEndpoint

command have been extended with a VersionSupported parameter to enable
Media Gateway controllers and Mediant 3000s to determine which protocol
versions each supports.
Error Codes - Supports 532 and 533 error codes.
Support of specific TGCP packages.
Electronic Surveillance (CALEA)

Electronic Surveillance enables the conduct of lawfully-authorized electronic
surveillance.
While Electronic Surveillance is activated, both bi-directional connection RTP streams
are duplicated and sent to the LEA server.
The connection sides are not affected while Electronic Surveillance is performed.
The feature is described in the PacketCable specification, Appendix H of
http://www.packetcable.com/downloads/specs/PKT-SP-TGCP-I10-050812.pdf
Activating this feature requires the BCT\CALEA Feature key.
If the CALEA is activated on a call, and, due to lack of board resources, CALEA is not
supported by the Mediant 3000, the call does not fail and appropriate error messages
are issued notifying that call was established without CALEA (error codes 211-214).
For more information, refer to the specification mentioned above.
The following is an example of a CRCX command with electronic surveillance
parameters:
CRCX 1204 ACgw0@AudioCodes.com MGCP 1.0
C: 1
L: p:20, a:PCMU, es-cci:123456, es-ccd:[1.2.3.4]:9000
M: recvonly
X: 1234
The following is an example of a MDCX command with electronic surveillance

parameters:
MDCX 1206 ds ACgw0@AudioCodes.com MGCP 1.0
C: 1
I: 21
L: p:20, a:PCMU, es-cci:123456, es-ccd:[1.2.3.4]:9000
User's Manual
110
User's Manual
M: sendrecv
X: 1234
7.1.13
RTP Media Encryption RFC 3711 Secured RTP

The SRTP (RFC 3711) media encryption standard is partially supported.
RFC 3711 defines a new media profile RTP/SAVP which is used when working in
secured streams. (The old profile is RTP/AVP).
The SRTP defines how to encrypt the media, but does not define how to negotiate the
encryption keys on the control level. The method used to negotiate the encryption
keys is defined at http://www.ietf.org/internet-drafts/draft-ietf-mmusic-sdescriptions12.txt.
This draft defines a cryptographic attribute for SDP to be used for media encryption.
There is no official definition for how to use this in MGCP. Therefore, rules were
developed for the Mediant 3000 and detailed below.
7.1.13.1
Supported Suites
SRTP implementation in DSP is limited to AES_CM_128_HMAC_SHA1_32,
AES_CM_128_HMAC_SHA1_80. All other suites are ignored.
While SRTP suite may hold many keys and key parameters, the Mediant 3000
supports a single key or no key parameters. Suites that are provided with many keys
or keys parameters are ignored and marked as not valid. A suite that contains extra
parameters is rejected even if it is a suite that is a supported suite.
7.1.13.2
Configuration and Activation

The following defines the encryption support level:
1.
DSP template - Template 0 supports SRTP.
2.
Feature Key Defines if media encryption is enabled on the board.
3.
ini file parameter The parameter EnableMediaSecurity defines SRTP

support when set to Enable, e.g., EnableMediaSecurity = 1.
The local descriptor may contain more parameters regarding the encryption, and
these are described in the following paragraphs.
7.1.13.3
SRTP Local Connection Option Format

Use of SRTP LCO parameters is described below, in Secured Connection
Negotiation.
Table 7-3: SRTP ABNF Parameter Description

Parameter
Description
LocalOptionValue=
("srtp" ":" EncryptionAlgorithm) Or

("x-srtp" ":" EncryptionAlgorithm)
Version 4.8
111
January 2006
Mediant 3000
Table 7-3: SRTP ABNF Parameter Description

Parameter
Description
EncryptionAlgorithm=
algorithmName 0*(";" algorithmName)
algorithmName =
AES_CM_128_HMAC_SHA1_32,
AES_CM_128_HMAC_SHA1_80
F8_128_HMAC_SHA1_32
SRTP_SUITE_NULL
7.1.13.4
SDP Definition
The following attribute is defined in http://www.ietf.org/internet-drafts/draft-ietf-mmusicsdescriptions-12.txta=crypto:<tag> <crypto-suite> <key-params> [<session-params>]
The fields tag, crypto-suite, key-params, and session-params are described below.
An example of the crypto attribute for the "RTP/SAVP" transport is provided, i.e., the
secure RTP extension to the Audio/Video Profile [srtp].
In the following, new lines are included for formatting reasons only:
a=crypto:1AES_CM_128_HMAC_SHA1_80
inline:PS1uQCVeeCFCanVmcjkpPywjNWhcYD0mXXtxaVBR|2^20|1:32
All mandatory and optional fields in SRTP crypto attribute are parsed, but attribute
lines that use session-parameters or multiple key parameters are ignored by the
SRTP negotiation algorithm.
Valid SRTP attribute line format:
a=crypto:1AES_CM_128_HMAC_SHA1_80
inline:PS1uQCVeeCFCanVmcjkpPywjNWhcYD0mXXtxaVBR
Endpoint Capability
While SRTP is enabled, upon auditing the endpoints, all supported SRTP suites will
be returned. Refer to the example below:
Audit Endpoint
AUEP 15959 ds/tr0/1@[10.4.4.129] MGCP 1.0
F: A
Audit redpond
200 15959 OK
A: nt:IN , v:G;D;T;L;R;A;M;MS;DT;MD;MO;BL;FXR;FM;IT,
a:PCMA;PCMU;G726_16;G726_24;G726_32;G726_40;G727_16;G727_24_16;G727
_24;G727_32_16;G727_32_24;G727_32;G727_40_16;G727_40_24;G727_40_32;
G723;G723Low;G729A;G728;Transparent;G729E;Telepone-Event;RED;CN;noop;image/t38,m:sendonly;recvonly;sendrecv;inactive;netwloop, xsrtp:AES_CM_128_HMAC_SHA1_32;AES_CM_128_HMAC_SHA1_80;SRTP_SUITE_N
ULL
User's Manual
112
User's Manual
7.1.13.5
Secured Connection Negotiation

The examples below show the creation of a secured connection via CRCX and MDCX
commands.
7.1.13.5.1
SRTP Negotiation
1.
If the User\ Call Agent does not provide LCO SRTP information or SDP line
attributes, the Gateway returns the supported suites.
Simple create connection.

CRCX 15936 ds/tr0/1@[10.4.4.129] MGCP 1.0
C: 1
L: a:PCMA
M: recvonly
All supported packages are provided in local connection options.

200 15936 OK
I: 22
v=0
o=- 1147873153 0 IN IP4 10.4.4.129
s=c=IN IP4 10.4.4.129
t=0 0
a=rtcp-xr:
a=crypto:1 AES_CM_128_HMAC_SHA1_32
inline:MKHEBFC/PMKHEB+CJfvspnkheifcZW
inline:9630xvspsqnkhecZEC/8520xurolpm
Terminated side gets originated side information.

CRCX 15938 ds/tr0/2@[10.4.4.129] MGCP 1.0
C: 1
L: a:PCMA
M: sendrecv
v=0
o=- 1147873153 0 IN IP4 10.4.4.129
s=c=IN IP4 10.4.4.129
t=0 0
a=rtcp-xr:
Version 4.8
113
January 2006
Mediant 3000
Terminated response with its local information.

200 15938 OK
I: 23
v=0
o=- 294810044 0 IN IP4 10.4.4.129
s=c=IN IP4 10.4.4.129
t=0 0
a=rtcp-xr:
inline:EbYVSPNKNLIFC/966j030xvspmjheh
Originating side gets termination side information.

MDCX 15940 ds/tr0/1@[10.4.4.129] MGCP 1.0
C: 1
I: 22
L: a:PCMA
M: sendrecv
v=0
o=- 294810044 0 IN IP4 10.4.4.129
s=c=IN IP4 10.4.4.129
t=0 0
a=rtcp-xr:
inline:EbYVSPNKNLIFC/966j030xvspmjheh
Update succeeded.
200 15940 OK
2.
LCO Only
Selection of a specific package.

CRCX 15963 ds/tr0/1@[10.4.4.129] MGCP 1.0
C: 1
L: a:PCMA,x-SRTP:AES_CM_128_HMAC_SHA1_32
M: recvonly
200 15963 OK
I: 21
v=0
o=- 377373126 0 IN IP4 10.4.4.129
s=c=IN IP4 10.4.4.129
t=0 0
a=rtcp-xr:
User's Manual
114
User's Manual
inline:NLIFC/QNKHEB/8520tqtrolifcaXnk
Selection of a valid package

CRCX 15964 ds/tr0/2@[10.4.4.129] MGCP 1.0
C: 1
L: a:PCMA,x-SRTP:F8_128_HMAC_SHA1_32;AES_CM_128_HMAC_SHA1_32
M: recvonly
200 15964 OK
I: 22
v=0
o=- 1862533257 0 IN IP4 10.4.4.129
s=c=IN IP4 10.4.4.129
t=0 0
a=rtcp-xr:
inline:pA9631yvspnkhebZKPMJGEB+OLJGDA
7.1.13.5.2
Negotiation Errors
7.1.13.5.3
If LCO was provided with no valid SRTP suites, a 532 error will be returned.
If SDP was provided with no valid SRTP suites,a 505 error will be returned.
If both local connection and remote connection SRTP were provided and no
match was found, a 506 error will be returned.
SDP Crypto Grammar

(For more information on ABNF, refer to http://www.ietf.org/internet-drafts/draft-ietfmmusic-sdescriptions-12.txt.)
e ABNF grammar for the generic crypto attribute is listed below, followed by the ABNF
grammar for the SRTP specific use of the crypto attribute.
The ABNF grammar for the crypto attribute is defined below:
"a=crypto:" tag 1*WSP crypto-suite 1*WSP key-params
*(1*WSP session-param)
tag
crypto-suite
= 1*9DIGIT
= 1*(ALPHA / DIGIT / "_")
key-params
key-param
key-method
key-method-ext
key-info
characters
=
=
=
=
=
session-param
characters
= 1*(VCHAR)
Version 4.8
key-param *(";" key-param)

key-method ":" key-info
"inline" / key-method-ext
1*(ALPHA / DIGIT / "_")
%x21-3A / %x3C-7E ; visible (printing)
115
; except semi-colon
; visible (printing)
January 2006
Mediant 3000
where WSP, ALPHA, DIGIT, and VCHAR are defined in [RFC2234].

SRTP "Crypto" Attribute Grammar
Below is an Augmented BNF [RFC2234] grammar for the SRTP-specific use of the
SDP crypto attribute:
crypto-suite
= srtp-crypto-suite
key-method= srtp-key-method
key-info
= srtp-key-info
session-param = srtp-session-param
srtp-crypto-suite
= "AES_CM_128_HMAC_SHA1_32" /
"F8_128_HMAC_SHA1_32" /
"AES_CM_128_HMAC_SHA1_80" /
srtp-crypto-suite-ext
srtp-key-method= "inline"
srtp-key-info
= key-salt ["|" lifetime] ["|" mki]
key-salt
= 1*(base64)
; binary key and salt values

; concatenated together, and
then
; base64 encoded [section 6.8 of
; RFC2046]
lifetime
mki
mki-value
mki-length
= ["2^"] 1*(DIGIT)
; see section 5.1 for "2^"
= mki-value ":" mki-length
= 1*DIGIT
= 1*3DIGIT
; range 1..128.
srtp-session-param
kdr
= kdr /
"UNENCRYPTED_SRTP" /
"UNENCRYPTED_SRTCP" /
"UNAUTHENTICATED_SRTP" /
fec-order /
fec-key /
wsh /
srtp-session-extension
= "KDR=" 1*2(DIGIT)
; range 0..24, power of two
fec-order = "FEC_ORDER=" fec-type

fec-type = "FEC_SRTP" / "SRTP_FEC"
fec-key
= "FEC_KEY=" key-params
wsh
base64
= "WSH=" 2*DIGIT
; minimum value is 64
= ALPHA / DIGIT / "+" / "/" / "="
srtp-crypto-suite-ext = 1*(ALPHA / DIGIT / "_")

srtp-session-extension = ["-"] 1*(VCHAR) ;visible chars
[RFC2234]
; first character must not be dash
("-")
User's Manual
116
User's Manual
7.1.14
MGCP Coder Negotiation
7.1.14.1
General Background
Control protocols such as MGCP and MEGACO use a special protocol to define the
stream characteristics. This protocol is called SDP Simple Session Description
Protocol and it is defined in RFC 2327. The SDP defines (among other things) the
IP address and port for the session (or ATM address in case of an ATM session), the
media type (audio for voice, data for fax), and codecs to be used for this session.
Every codec is represented with the encode method and payload number.
There are two kinds of RTP payloads:
The first type is the fixed payload that was assigned to a known codec. When this
kind of payload is used, there is no need for further data, as the number is world wide
accepted. Refer to the Appendix, ''RTP/RTCP Payload Types'' on page 421 for the
complete list of fixed coders.
The second type is the dynamic payload, and it is used to define any codec. The
range of the dynamic payloads is 96 to 127. When defining a dynamic payload, extra
data is needed to map the number to a known codec. This data can be found in the
MIME registration of each codec. Currently, the dynamic payloads are not handled in
the control protocols, therefore its implementation is described here.
Since MGCP does not have local SDP, it uses Local Connection Options to handle the
Dynamic Payload type and uses the advanced coder features.
7.1.14.2
MGCP Coder Negotiation (RFC 3435)

RFC 3435 defines three coder lists for coder negotiation:
Internal coders list this list contains the coders supported by the gateway.
LCO list list supplied by the Call Agent.
RCO list list supplied by the remote side.
Note: Refer to RFC 3435, Section 2.6, 'Use of Local Connection Options and
Connection Descriptors'.
While negotiating coders, the gateway must use the following methodology:
Version 4.8
1.
If the Call Agent supplies an LCO list, the media gateway takes an intersection of
the LCO and the internal coders lists.
If no match is found, an Error 534 is returned indicating a coder negotiation error.
2.
If the Call Agent supplies both an LCO and an RCO, the media gateway takes an
intersection of the list from step a (above) and the RCO list.
If no match is found, an Error 534 is returned indicating a coder negotiation error.
3.
If a match is found, e.g., coders are supported by the board and appear in both
lists, the media gateway uses the first voice coder. This coder appears first in the
SDP responce.
4.
If the RCO list is supplied, an intersection is made between the RCO list and
internal list.
117
January 2006
Mediant 3000
If no match is found, an Error 505 is returned, indicating an unsupported remote
connection descriptor error.
5.
If no LCO list and no RCO list were provided, the media gateway responds with
all of its supported coder list i.e., Internal coder list.
The default coder configured in the ini file is the first in list.
MGCP and SDP RFCs distinguish between two type of coders: voice coders (G.711,
G.729, GSM, etc.) and non-voice coders (RFC 2833, Comfort noise, etc.). Coder
negotiation fails if no voice coder is found during the coder negotiation process.
If several voice coders and non-voice coders are supplied. In the SDP response,
voice coder are first in list and non-voice coders are next in list. Coder negotiation is
performed on both voice coders and non-voice coders.
7.1.14.3
Coder Negotiation Configurations

The default coder can be modified in the ini file parameter, 'MGCPDefaultCoder'. An
example is: MGCPDefaultCoder='G726'.
Users can load the device with a pre-defined coder table (see 'Coder Table File' on
page 418). The coder table allows the user to define per each coder its payload type,
textual representation in the MGCP messages and desired packetization period.
According to coder negotiation scheme above, if no coder is reported in the LCO, the
default coder is used and all supported coders are reported in the SDP response.
When the parameter 'UseNewFormatCoderNegotiation' is set to 1 (default), the
internal coder list is reported. To prevent the gateway from sending this list, set the
parameter to 0 in the ini file.
7.1.14.4
Mapping of Payload Numbers to Coders

The table below shows the default mapping between payload numbers and coders,
when the dynamic payload assignment is not used. Coders are supported according
to selected DSPVersion templates - DSPVersionTemplateNumber ini file parameter.
Table 7-4: MGCP Mapping of Payload Numbers to Coders

Coder
Encoding Name
AMR (10.2)
AMR_10_2, AMR1020
70
AMR (12.2)
AMR_12_2,AMR1220
71
AMR (4.75)
AMR_4_75,AMR475
64
AMR (5.15)
AMR_5_15 , AMR515
65
AMR (5.9)
AMR_5_9 ,AMR590
66
AMR (6.7)
AMR_6_7, AMR670
67
AMR (7.4)
AMR_7_4, AMR740
68
AMR (7.95)
AMR_7_95, AMR795
69
Comfort Noise
CN, COMFORT-NOISE
13
EVRC
"EVRC"
60
User's Manual
Default Payload Number
118
User's Manual

Coder
Encoding Name
EVRC (TFO)
"X-EVRC_TFO"
81
EVRC (TTY)
"X-EVRC_TTY"
85
G.711 law
PCMU, G711, G.711,G.711U,

G.711MULAW, G711MULAW
G.726_32
"G726_32"
G.729E
"G729E",G.729E
63
G.711 A law_64
"PCMA", G.711A,G.711ALAW
G.723 (High)
"G723" G.723 , G723, G723HIGH
G.723 (Low)
G723LOW
80
G.726_16
"G726_16"
35
G.726_24
"G726_24"
36
G.726_40
"G726_40"
38
G.727_16
"X-G727_16", G727
39
G.727_24
"X-G727_24"
41
G.727_24_16
"X-G727_24_16"
40
G.727_32
"X-G727_32"
44
G.727_32_16
"X-G727_32_16"
42
G.727_32_24
"X-G727_32_24"
43
G.727_40_16
"X-G727_40_16"
45
G.727_40_24
"X-G727_40_24"
46
G.727_40_32
"X-G727_40_32"
47
G.728
"G728"
15
G.729
"G729","G.729","G729A"
18
GSM
"GSM"
GSM-EFR
GSM-EFR
84
NetCoder_4_8
"X-NETCODER_4_8", NETCODER_4_8
49
NetCoder_5_6
"X-NETCODER_5_6",NETCODER_5_6
50
NetCoder_6_4
"X-NETCODER_6_4", NETCODER_6_4
51
NetCoder_7_2
52
NetCoder_8
"X-NETCODER_8",NETCODER_8
53
NetCoder_8_8
54
Version 4.8
119
January 2006
Mediant 3000

Coder
Encoding Name
NetCoder_9_6
55
QCELP_13
"QCELP"
62
QCELP_13_TFO
"X-QCELP_TFO"
83
QCELP_8
"X-QCELP_8"
61
QCELP_8_TFO
"X-QCELP_8_TFO"
82
Redundancy per RFC

2198
RED
104
RFC 2833
telephone-event
96
T.38 Fax
IMAGE/T38
Transparent
"X-CCD", TRANSPARENT
No Payload
56
Note: NetCoder vocoders is not supported in the current version of Mediant 3000.
7.1.14.5
Supported MGCP Packages

Events and signals are grouped in packages. Each package supports several events
and signals. The TrunkPack series MGCP client supports LINE, DTMF, Fax Package
Definition, Media Format Parameter Package, Extended line package, Announcement
package, Trunk, Hand Set Emulation and Generic packages.
Note that not all commands/events listed below are applicable to all TrunkPack series
devices. For example, hu, hd, hf (all related to on/off hook transitions) are applicable
only to devices containing an analog PSTN interface.
Notes for all MGCP Package tables:
R:
An x appears in this column if the event can be requested by the Call Agent.
S:
If nothing appears in this column for an event, then the event cannot be
signaled on command by the Call Agent.
Otherwise, the following symbols identify the type of event:
User's Manual
OO signal:
The On/Off signal is turned ON until commanded by the Call Agent to

switch it OFF, and vice versa.
TO signal:
The Timeout signal lasts for a given duration unless it is superseded

by a new signal.
BR signal:
The Brief signal event has a short, known duration.
Duration:
Specifies the duration of TO signals. Signal duration can be changed

by adding time out parameter to signal e.g. L/dl(to=18000) , time units
are 1 msecs.
120
User's Manual
7.1.14.6
Generic Media Package - G
Table 7-5: Generic Media Package - G

Symbol
Definition
Duration
mt
Modem detected
ft
Fax tone detected
rt
Ring back tone
TO
Ring back on connection
TO
rbk
7.1.14.7
180 sec
DTMF Package - D
Table 7-6: DTMF Package - D

Symbol
Definition
Duration
DTMF 0
BR
DTMF 1
BR
DTMF 2
BR
DTMF 3
BR
DTMF 4
BR
DTMF 5
BR
DTMF 6
BR
DTMF 7
BR
DTMF 8
BR
DTMF 9
BR
DTMF #
BR
DTMF *
BR
DTMF A
BR
DTMF B
BR
DTMF C
BR
DTMF D
BR
Inter-digit Timer
Wildcard, match any digit 0 to

9
Version 4.8
121
4 sec
January 2006
Mediant 3000
Table 7-6: DTMF Package - D

Symbol
of
Definition
Report Failure
7.1.14.8
Duration
Line Package - L
Table 7-7: Line Package - L

Symbol
Definition
0-9, #, *, a,b,c,d
DTMF tones
Duration
BR
hd*
Off hook transition
hu*
On hook transition
hf
Flash hook
bz
Busy tone
ft
Fax tone event
mt
Modem tones
dl
TO
30 sec
Dial tone
TO
16 sec
ro
Reorder tone
TO
30 sec
rt
Ring back tone
TO
180 sec
rg
Ringing
TO
180 sec
cf
Confirmation tone
BR
oc
Report on completion of
TO
wt, wt1,
wt2,wt3,wt4
Call waiting tones
ci (ti,nu,na)
Caller ID (ci(time,
number, name)
Time = MM/DD/HH/MN
BR
sup(addr(digits DTMF dialing

)
BR
of
Report Failure
lsa
line side answer

supervision
osi
network disconnect
vmwi
User's Manual
Visual Message Waiting

Indicator
BR
122
to
infinite
to
900 ms
OO
User's Manual
* Persistence Events
Note: Caller ID is to be supported in the next applicable release.
7.1.14.9
Handset Emulation Package - H
Table 7-8: Handset Emulation Package - H

Symbol
Definition
Duration/Comment
hd
Off hook transition
OO
hu
On hook transition
OO
hf
Flash hook
bz
Busy tone
Call waiting tones
Dial tone (350 Hz & 440 Hz)
Network busy (fast cycle

busy)
rg
Ringing
ro
Reorder tone
oc
Report on completion
ot
Off hook warning tone
wt, wt1,
wt2,wt3,wt4
dl
nbz
BR
sup(addr
(digits))
DTMF dialing
of
Report Failure
lsa
line side answer supervision
osi
Network Disconnect
Version 4.8
123
BR
BR
Example:
Supp(addr(2,3,5))
to
infinite
TO
900 ms
January 2006
Mediant 3000
7.1.14.10
Trunk Package - T
Table 7-9: Trunk Package - T

Symbol
Definition
Duration/Comment
co1
Continuity tone
TO
2 sec
co2
Continuity test
TO
2 sec
Supported via 'Connection
Mode'
lb
Loopback
OO
om
Old milliwatt tone
OO
nm
New milliwatt tone
OO
ro
Reorder tone
TO
of
Report failure
7.1.14.11
30 sec
PacketCable (NCS) Line Package - L
Table 7-10: PacketCable (NCS) Line Package - L

Symbol
Definition
Duration/Comment
0-9,*,#,a,b,c,d
DTMF tones
aw
Answer tone
bz
Busy tone
TO
cf
Confirmation tone
BR
Caller ID
BR
ci(ti, nu,na)
BR
30 sec
ti denotes time
nu denotes number
na denotes name
dl
Dial tone
ft
Fax tone
hd
Off-hook transition
hf
Flash hook
hu
On-hook transition
mt
Modem tones
mwi
User's Manual
TO
x
P,S
P
P,S
x
Message waiting indicator
TO
124
16 sec
User's Manual
Table 7-10: PacketCable (NCS) Line Package - L

Symbol
Definition
oc
Operation complete
of
Operation failure
ot
Off-hook warning tone
r0, r1, r2, r3, r4,

r5, r6 or r7
Duration/Comment
Time-out = infinite
Distinctive ringing (0...7)
TO
rg
Ringing
TO
180 sec
ro
Reorder tone
TO
180 sec
rt
Ring back tone
TO
30 sec
sl
Stutter dial tone
C,TO
180 sec
wt, wt1, wt2,

wt3, wt4
x
osi
vmwi
7.1.14.12
Call waiting tones
DTMF tones wildcard
BR
Matches any of the digits
0-9
network disconnect
to
Visual Message Waiting

Indicator
900 ms
OO
Announcement Package - A
Table 7-11: Generic Media Package - A

Symbol
ann
(index)
Definition
Play an announcement
oc
Report on completion
of
Report failure
Version 4.8
Duration/Comment
TO
Variable
125
January 2006
Mediant 3000
7.1.14.13
RTP Package - R
Table 7-12: RTP Package - R

Symbol
Definition
Duration/Comment
co1
Continuity Tone (single or

return tone)
TO
2 sec
co2
Continuity Test (go tone, in

dual tone procedures)
TO
2 sec
ma
Media Start
rto
RTP/RTCP Timeout
RTP/RTCP Timeout (rto(<timeout>,st=<start-time>)):
time out - optional parameter, increase in 100 msec steps. Maximum value is
12800 msec.
start-time - optional parameter, default value is "ra".
If the user does not utilize the event parameters, defaults could be set through ini file:
timeout - "BrokenConnectionEventTimeOut". Default value is 300 msec.

Parameter can be changed in 100 msec steps.
Start-time - "BrokenConnectionEventActivationMode". Default value is 1 - starts

after first incoming RTCP packet. While set to zero the timer starts at once.
The following is an Event example:

RQNT 2001 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 1
R: r/rto(N)
In this case a notification occurs if there is a period of time when no RTP or RTCP
packets have been received for BrokenConnectionEventTimeOut*100.
The resulting NTFY with observed events would be as shown in this example:
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 1
O: r/rto(300)
Another option could be:
RQNT 2001 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
X: 1
R: r/rto(N)(4000,st=im)
In case no RTP is received 4 seconds from the time the event was received, remote
disconnected event is generated:
NTFY 3002 ds/ds1-3/6@gw-o.whatever.net MGCP 1.0
User's Manual
126
User's Manual
X: 1
O: r/rto(300)
Continuity Test (go tone, in dual tone procedures) and Continuity Tone (single or
return tone):
Continuity tone generation/detection is configuration dependent. To generate
continuity tones and allow for their detection (if desired), they must be defined by
adding the following to the ini file :
ForceEchoOff=0
ENABLECONTINUITYTONES = 1
USERDEFINEDTONEDETECTORENABLE = 1
The tones should also be defined as part of the call progress tone file loaded into the
device.
7.1.14.14
CAS Packages
7.1.14.14.1
CAS Package - MS
Table 7-13: CAS Package - MS

Symbol
ans
Definition
Duration/Comment
Call answer
BR
bl
Block
BR
bz
Busy Tone
TO
inf
Information Digits
oc
Operation complete
of
Operation fail
rel
Release call
BR
res
Resume call
BR
rlc
Release complete
P,S
BR
ro
Reorder tone
TO
rt
Ring back tone
TO
P,S
TO
BR
sup
Call setup
sus
Suspend call
Version 4.8
127
January 2006
Mediant 3000
7.1.14.14.2
CAS Package - DT
Table 7-14: CAS Package - DT

Symbol
Definition
Duration/Comment
Call answer
BR
bl
Block
BR
bz
Busy tone
TO
dl
Dial tone
TO
oc
Operation complete
of
Operation fail
rel
Release call
BR
res
Resume call
BR
rlc
Release complete
P,S
BR
ro
Reorder tone
TO
rt
Ring back tone
TO
P,S
TO
BR
ans
sup
Call setup
sus
Suspend call
7.1.14.15
ISUP Trunk Package - IT
Table 7-15: ISUP Trunk Package - IT

Symbol
Definition
Duration/Comment
co1
Continuity tone 1
TO
Time-out = 2 sec
co2
Continuity tone 2
TO
Time-out = 2 sec
ft
Fax tone
ma
Media start
mt
Modem tone
oc
Operation complete
of
Operation failure
ro
Reorder tone
TO
Time-out = 30 sec
rt
Ring back tone
TO,C
Time-out = 180 sec
User's Manual
128
User's Manual
7.1.14.16
Media Format Parameter Package - FM

Supported FMTP Formats
According to the Media Format Parameter Package, AudioCodes supports the
following FMTP formats:
L:a:codec1;codec2, fmtp:"codec1 formatX", fmtp:"codec2 formatY"
L:a:codec1;codec2, fmtp:"codec1 formatX";"codec2 formatY"
L:a:codec1;codec1, fmtp:"codec1 formatX"
L:a:codec1;codec1, fmtp:"codec1:2 formatX"
Redundancy
fmtp red codername1/codername2/./codernameN
AMR Family
fmtp: AMR mode-set=0 (bitrate=4.75)
G.723 Family
fmtp: G723 bitrate=5.3 Low
fmtp: G723 bitrate=6.3 High
fmtp: G723 annexb=yes VAD on - Voice Activity Detection on
fmtp: G723 annexb=no VAD off - Voice Activity Detection off
NetCoder Family
fmtp: NETCODER mode-set=0 (bitrate=4.75)
G.729 Family
Version 4.8
fmtp: G729 annexb=yes (VAD on - Voice Activity Detection on)

129
January 2006
Mediant 3000
7.1.14.17
fmtp: G729 annexb=no (VAD off - Voice Activity Detection off)
Fax Package Definition - FXR
Table 7-16: Fax Package Definition - FXR

Symbol
Definition
Duration/Comment
gwfax
Gateway controlled fax
Device controlled fax

handling (See below)
nopfax
No special fax handling
No special fax handling

upon fax (See below)
t38
T.38 fax relay
Call Agent controlled T.38

fax relay (See below)
Supported events parameters
Device Controlled Fax (gwfax) - Device controlled fax handling. The device
handled fax event is parameterized with one of the following:
start - device handled fax was initiated
stop - device handled fax ended normally
failure - the procedure ended abnormally
No Special Fax Handling (nopfax) - The no special fax handling event is

parameterized with one of the following:
7.1.14.18
Start no special fax handling was in place O: fxr/nopfax(start)
T.38 fax relay (t38) Call Agent controlled T.38 fax relay - The Call Agent
controlled T.38 fax relay event is parameterized with one of the following:
start - Call Agent controlled T.38 fax relay was initiated
stop - Call Agent controlled T.38 fax relay
failure - Call Agent controlled T.38 fax relay ended abnormally
V5 Package Definition X-v5
Table 7-17: V5 Package Definition

Symbol
Definition
prp
Wink signal
rp
Line polarity reversal
User's Manual
S
x
Duration/Comment
BR
TO
130
Infinite
User's Manual
7.1.14.19
Signal List Package - SL

The Signal List package allows the playing of more than one brief or timeout signal at
a time. The package is defined in RFC 3660.
Table 7-18: Signal List Package Definition

Symbol
Definition
oc
Operation complete
of
Operation failed
s(list)
Signal List
7.1.15
MGCP Endpoint Map
Duration/Comment
TO
variable
The Endpoint Name is a combination of an EndpointPrefix, (a string of up to 19

characters) followed by a TrunkName, (a string of up to 19 characters) followed by the
Trunk Number representing the Trunk in the range 0 to7 (optionally 1 to 8), together
with the EndpointPrefix, (a string of up to 19 characters) followed by a number
representing the B-channel number in the range 0 to 31 for E1, or 1 to 24 for T1/J1.
The notation is shown as: EndPointPrefix/TrunkName X/Y
For example: TS/Trunk#2/31
Where, in this example, EndpointPrefix=TS and TrunkName=Trunk#
Note:
7.1.16
J1 is to be supported in the next applicable release.
Compression Coders
MGCP supports the compression Coders listed in the 'Coder Table File' on page 418
section.
The following table lists potential coders (actual coder support depends on the specific
DSP template version set on the device) and their default textual representation in
MGCP (textual representation may be changed via Coder Table file).
Table 7-19: Compression Coders

Coder
MGCP Textual Name
AMR (10.2)
AMR_10_2, AMR1020
AMR (12.2)
AMR_12_2,AMR1220
AMR (4.75)
AMR_4_75,AMR475
Version 4.8
131
January 2006
Mediant 3000

Coder
MGCP Textual Name
AMR (5.15)
AMR_5_15 , AMR515
AMR (5.9)
AMR_5_9 ,AMR590
AMR (6.7)
AMR_6_7, AMR670
AMR (7.4)
AMR_7_4, AMR740
AMR (7.95)
AMR_7_95, AMR795
Comfort Noise
CN, COMFORT-NOISE
EVRC
"EVRC"
EVRC (TFO)
"X-EVRC_TFO"
EVRC (TTY)
"X-EVRC_TTY"
G.711
PCMU, G711, G.711,G.711U, G.711MULAW,

G711MULAW
law
G.726_32
"G726_32"
G.729E
"G729E",G.729E
G.711 A law_64
"PCMA", G.711A,G.711ALAW
G.723 (High)
"G723" G.723 , G723, G723HIGH
G.723 (Low)
G723LOW
G.726_16
"G726_16"
G.726_24
"G726_24"
G.726_40
"G726_40"
G.727_16
"G727_16", G727
G.727_24
"G727_24"
G.727_24_16
"G727_24_16"
G.727_32
"G727_32"
G.727_32_16
"G727_32_16"
G.727_32_24
"G727_32_24"
G.727_40_16
"G727_40_16"
G.727_40_24
"G727_40_24"
G.727_40_32
"G727_40_32"
G.728
"G728"
G.729
"G729","G.729","G729A"
GSM
"GSM"
User's Manual
132
User's Manual

Coder
MGCP Textual Name
GSM-EFR
GSM-EFR
NetCoder_4_8
"X-NETCODER", NETCODER_4_8
NetCoder_5_6
"X-NETCODER",NETCODER_5_6
NetCoder_6_4
"X-NETCODER", NETCODER_6_4
NetCoder_7_2
NetCoder_8
"X-NETCODER",NETCODER_8
NetCoder_8_8
NetCoder_9_6
QCELP_13
"QCELP",QCELP_13
QCELP_13_TFO
"QCELP_TFO"
QCELP_8
"QCELP_8"
QCELP_8_TFO
"QCELP_8_TFO"
Redundancy per RFC 2198
RED
RFC 2833
telephone-event
T.38 Fax
IMAGE/T38
Transparent
"X-CCD", TRANSPARENT,CCD
iLBC13
iLBC13
iLBC15
iLBC15
BV16
BV16
NOOP
no-op
The following is an example of creating a connection command with G.711 coders:

CRCX 10060 Acgw0@[10.1.37.5]
C: 35
L: a:G.711
7.1.17
STUN - Simple Traversal of User Datagram Protocol

An AudioCodes Gateway residing in a Local Area Network can discover the presence
and types of NATs (Network Address Translator) and firewalls between it and the
public internet using the STUN (Simple Traversal of User Datagram) protocol as
described in RFC 3489. STUN is a client server protocol where the gateway is the
STUN client and requires a STUN server running on the public internet.
Version 4.8
133
January 2006
Mediant 3000
STUN enables a gateway residing inside a LAN to provide a public internet address to
its signaling and media ports although it resides in a LAN behind a NAT/firewall..
Using STUN, a gateway will display its signaling address (upon RSIP, etc) as the
address which appears to the public internet. Media addresses will also be displayed
as well as public addresses in the appropriate SDP field.
To use STUN a user should specify the following parameters in the ini file:
ENABLESTUN = 1
STUNSERVERPRIMARYIP = primary server IP address
STUNSERVERSECONDARYIP = secondary server IP address; may be omitted
NATBINDINGDEFAULTTIMEOUT = binding default timeout, use 20 for default
Because the signaling connection goes through a NAT of some kind, it is necessary to
keep this connection a live. Therefore, when using STUN, the keep alive mechanism
described in 1.3.2.2 will be automatically activated.
7.2
MEGACO (Media Gateway Control) Protocol
7.2.1
MEGACO Overview
MEGACO (MEdia GAteway COntrol) Protocol is a standards-based network control
protocol (based on IETF RFC 3015 and ITU-T H.248 V1). MEGACO assumes a call
control architecture where the call control intelligence is outside the Mediant 3000 and
handled by an external Media Gateway Controller (MGC). MEGACO is a master/slave
protocol, where the Mediant 3000 is expected to execute commands sent by the Call
Agent (another name for MGC).
The connection is handled using two elements: Terminations and Contexts.
Termination is the basic element of the call. There is a physical Termination
representing a physical entity (e.g., B-channel), and an ephemeral Termination
representing the generated stream. To create a connection, a Context is used. A
Context contains one or more Terminations, and describes the topology between the
Terminations. A typical connection creation command creates a new Context and
adds into it one physical Termination and one new (ephemeral) Termination. The
ephemeral Termination parameters describe the media type and the stream direction
(SendReceive, SendOnly or ReceiveOnly).
Since this is a standards-based control protocol, AudioCodes does not provide any
special software library to enable users to construct their own Call Agent. (Users can
choose any of many such stacks are available in the market.)
Note: MGCP and MEGACO protocols cannot coexist on the same Mediant 3000.
User's Manual
134
User's Manual
7.2.2
Operation
7.2.2.1
Executing MEGACO Commands

MEGACO commands, received from an external Call Agent through the IP network,
are decoded and executed in the Mediant 3000. Both text encoding and binary
encoding are supported. Commands can create new connections, delete connections,
or modify the connection parameters.
Several commands that support the basic operations required to control a Mediant
3000:
Status change command - The command ServiceChange allows changing the

status of one or more Terminations. When used with a special Termination, called
the ROOT Termination, it affects the entire Mediant 3000.
Connection commands - The commands Add, Move, Modify and Subtract allow
the creation and deletion of a call connection inside the Mediant 3000. These
commands allow the application to create new connections, delete existing
connections, and modify the connection parameters.
Notify command - The Notify command is used by the Mediant 3000 to inform the
Call Agent of events occurring on one of the Terminations.
Audit commands - The AuditCapabilities and AuditValue commands are used to

query the Mediant 3000 about Termination configuration and state. This
information helps in managing and controlling the Mediant 3000.
A MEGACO-configured Mediant 3000 starts by sending a ServiceChange command

to its primary MGC. If no response is received from it, the gateway goes on to the next
MGC in its list. When an MGC accepts the Mediant 3000 registration, the session can
start. Subsequently, the Mediant 3000 responds to MGC commands. Event
notifications are sent only if the MGC requests them specifically.
7.2.2.2
KeepAlive Notifications From the Gateway

The Keep Alive notifications from the gateway to the MGC are implemented either
using an AudioCodes proprietary mechanism via a NOP ServiceChange command
(controlled by ini file parameters), or using the standard inactivity timer package
(H.248.14).
For the AudioCodes proprietary mechanism via a NOP ServiceChange command
there are two parameters:
KeepAliveEnabled - activates or de-activate the Keep Alive function
KeepAliveInterval - defines the inactivity period in seconds
If the KeepAlive mechanism is enabled, the Mediant 3000 sends a NOP

ServiceChange command when it detects a defined period without commands from
the MGC (the default period is 12 sec.) If no response is received from the MGC, the
retransmission mechanism is initiated and eventually causes a new ServiceChange
command to be sent to the next available MGC.
For the standard inactivity timer package (H.248.14) Inactivity detection is fully
supported. The activation is by requesting the 'it/ito' event on the root termination. The
'mit' parameter of this event defines the inactivity period in 10 millisecond units. Note
that this function is not set by configuration. The Call Manager must send a request
for this event.
Version 4.8
135
January 2006
Mediant 3000
7.2.2.3
Setting MEGACO Call Agent IP Address and Port

Users can provide the Mediant 3000 with up to 5 IP addresses of the MEGACO Call
Agents
using
the
parameters,
ProvisionedCallAgents
and
ProvisionedCallAgentsPorts.
The first Call Agent in the list is the primary one. In the case of a loss of connection,
the Mediant 3000 tries to connect with the next on the list, and it continues trying until
one of the Call Agents accepts the registration request. If the current connection is
with a secondary MGC, the Mediant 3000 starts again from the primary MGC. The
current Call Agent can override this setting by sending a ServiceChange command
with a new IP address (not necessarily in the original list) and a HandOff method. If no
CallAgent IP address exists, MEGACO does not become operational.
Instead of defining an IP address, users can use a domain name for the Call Agent
using the CallAgentDomainName parameter. When using it, define also the
DNSPRIServerIP and DNSSECServerIP parameters. When using a domain name, the
Mediant 3000 resolves the name on each disconnection, allowing the user to switch to
another Call Agent.
7.2.2.4
Authorization Check of Call Manager IP Addresses

While the MEGACO specification specifies that only one Call Manager can send
commands to the gateway at a time, AudioCodes gateways handle the Authorization
Check in either of these modes:
1.
No authorization check is performed. This mode specifies that every command is

accepted and executed.
2.
The IP address of the Call Manager sending the incoming command is checked
against the list of provisioned Call Managers. If it matches one on the list, the
command is executed. If The Call Manager' IP Address is not found on the list, an
error message is sent. This mode is set as the default.
These
two
modes
are
controlled
by
the
ini
'MEGACOCheckLegalityOfMGC', for which the default value is 1.
7.2.2.5
file
parameter
Light Virtual Media Gateway

Currently the application does not support the standard virtual media gateway. In
order to achieve some of the functionally, however, the following support is included:
The above authorization enables the gateway to reply to more than one MGC.
Notifications are sent to the MGC that requested them by sending a command
with the events descriptor to the board.
Note: The serviceChange commands are sent ONLY to the controlling MGC. This
implies that if one of the non-controlling MGC stopped responding, a
disconnection service change is sent to the controlling MGC after
retransmission timer expiration.
User's Manual
136
User's Manual
7.2.2.6
Support of DiffServ Capabilities

The DiffServ value of the IP header can be set for both the control path and the media
path. The range of the DiffServ parameter is between 0 and 63. It enables routers to
differentiate between different streams. The values are set via SNMP, Web or ini file
parameter. Note, that changing the value of the control path requires the Gateway to
be reset.
The value of the control path is now controlled by an ini file parameter called
'PremiumServiceClassControlDiffServ', with the default value of 46. If this parameter is
not set, and the old parameter 'ControlDiffServ' is, the old parameter is used.
The value for the media path is now set via the ini file parameter
'PremiumServiceClassMediaDiffServ', with the default value of 46. If this parameter is
not set, and the old parameter 'IPDiffServ' is, the old parameter is used '.
7.2.2.7
Handling Events
Events are declared in an EventsDescriptor that has an ID and a list of events on
which the Call Agent requires notification. Up to 16 events can be defined in the
descriptor. Wildcards are permitted in the events names. For example, if the list
includes dd/*, and the user presses the number 1, the Call Agent receives notification
when the digit starts (dd/std{tl=d1}) and when it ends (dd/etd{tl=d1}). The event dd/d1
is not sent, as it is included in the other two. An event can have parameters, for
example, the KeepActive flag. When the event having the KeepActive flag is received,
it does not stop the currently played signals.
An event can have an embedded descriptor in it. It can be a SignalsDescriptor (refer
to "Playing Signals" below), a new EventDescriptor, or both. The embedded descriptor
replaces the current descriptor.
7.2.2.8
Playing Signals
Signals in MEGACO reside in a SignalsDescriptor. Only one signal is allowed in the
descriptor as the Mediant 3000s cannot play more than one signal at a time. However,
this one signal can be of the SignalList type. In which case, there can be up to 30
signals in the list, and they are played sequentially until the list ends or the execution
is interrupted.
Interrupting the execution can be one of the following:
Event - Only events required by the Call Agent stop the execution, and only if
they do not have the KeepActive flag.
New Signals Descriptor - Stops the execution, unless the same signal is received,
and it has a KeepActive flag. If the old signal and the new signal are both signal
lists and have the same ID, the new signal is ignored.
Subtracting the termination from the call
When a signal is ended, a signal completion notification is sent only if:
The signal has the NotifyCompletion parameter and the completion reason
(TimeOut, Interrupted by Signal, Interrupted by Event) matches one of the
NotifyCompletion parameters.
The events descriptor contains the signal completion event (g/sc).
The notification includes the ID of the signal that was ended and the signal list ID if it
was a signal list.
Version 4.8
137
January 2006
Mediant 3000
Signal duration (For timeout signals only) can be defined as a parameter in the signal.
If omitted, a default value is used (refer to the package's description in the beginning
of this section).
Call Progress Tones must be defined by the user in a Call Progress Tones (CPT ID)
file. An off-line utility is supplied to convert this file to a binary file. Each tone has a
toneId in the file, used by MEGACO when playing the signal. For the correlation
between signal names and CPT file IDs, refer to the column, Map to CPT File of the
table, ''Generic Media Package - G'' on page 121.
When a CPT file is missing, the Mediant 3000 defines default values only for the
following signals:
Dial tone
Ringing tone
Busy tone
Announcements should also be prepared offline by users.

The following example shows a command that plays a list of announcements. When
the list is finished, a notify command is sent:
MEGACO/1 [172.16.8.88]
T=207{
C = 1 {
Modify = gws0c1 {
SG{SL=1234{an/apf{an=2},an/apf{an=3},an/apf{an=1,NC={TO,IBS}}}},
E=1001 {g/sc}}}}
And the Notify request:
MEGACO/1 [10.2.229.18]:2944
T=2015{
C = 1 {
O-N=gws0c1{
OE=1001{19700101T00003542: g/sc{
Meth=TO,SigId=an/apf,SLID=1234}}}}}
7.2.2.9
Mediation
Mediation in MEGACO connects two ephemeral terminations. This operation can be
used by a Call Agent to connect users with different coders or to connect two types of
users, such as ATM and RTP. The mediation operation requires up to two DSPs
according to the following rules:
When both users use the same coder, no DSP is allocated.
When both users use different coders, two DSPs are allocated.
When one side uses RFC 2833 and the other does not, or the payloads of RFC
2833 are different, two DSPs are allocated.
The mediation is created with a simple MEGACO ADD command, with two ephemeral
terminations, as shown in the following example:
MEGACO/1 [10.10.0.70]; Connect the streams,
Transaction = 2 {
Context = $ {
Add = $ {
User's Manual
138
User's Manual
Media {
LocalControl {
Mode = SendReceive,
rtp/jit=70 },
Local {
v=0
m=audio $ RTP/AVP 0
c=IN IP4 $
},
Remote {
v=0
c=IN IP4 10.2.229.19
}
}
},
Add = $ {
Media {
LocalControl {
Mode = SendReceive,
rtp/jit=70 },
Local {
v=0
m=audio $ RTP/AVP 4
c=IN IP4 $
},
Remote {
v=0
c=IN IP4 10.2.229.19
}}}}}
This example connects two RTP streams, one uses the G.711 coder and the other
uses the G.723 coder.
7.2.2.10
CAS/R2 Support in MEGACO
Note: Contact your Mediant 3000 representative for more information on support of
this feature.
The CAS/R2 trunk protocols are supported in MEGACO by using the 'bcas' package
defined in H.248.25, the 'icas' and 'casblk' packages defined in H.248.28 and 'icasc'
package defined in H.248.29
Using these packages, the Mediant 3000 converts from the MFC-R2 protocol, which is
a PSTN protocol, to the MEGACO protocol, thereby bridging the PSTN world with the
IP world.
When MEGACO and MFC-R2 protocols share control of a channel, their timings are
synchronized so that MEGACO commands do not cause damage to the MFC-R2
protocol's negotiation. For example, MFC-R2 protocol must work with the Echo
Canceler in OFF state or else Multiple Frequency (MF) is not received correctly. Thus,
if MEGACO protocol receives a command to open a channel with the Echo Canceler
ON and MFC-R2 protocol's negotiation is not yet finished, the entire negotiation could
be damaged. To avoid this problem, the MEGACO does not change the echo
canceler state until the call was accepted by the answering side.
Version 4.8
139
January 2006
Mediant 3000
The actual call should start only after the accept signal is finished. (See the call flow of
call start).
The application supports a special option called re-answer. In this option, the
answering side can put down the phone, and pick it up again. The phone close will
result with the 'icas/cb' event, but if the phone is taken up again, the 'bcas/ans' event
is be sent. The timing of this action is defined by the MGC. It is the MGC responsibility
to decide when the call should be disconnected by sending the 'icas/cf' signal. (refer to
the figures below for the call flow of the call disconnect for the use of these signals
and events). Note that even though the re-answer timer is controlled by the MGC, the
Mediant 3000 still keeps its own timer (currently hard-coded to be 256 seconds), so
that it does not get stuck in case of command loss.
Blocking the Bchannel is done by using the 'casblk' package. The 'blk' and 'ublk'
events are reported only if the action was done by the remote side. The reason for
this is that the local side already knows its status. Unfortunately, sometimes the MGC
loses the state and needs to synchronize with the current status. The recommended
command for this is to send the 'bcas/idle' signal, and ask for the 'bcas/idle' and
'casblk/blk' events. This results in idling the line in case of a partial call, and getting the
current state of the line: Idle (After idling completed) or Blocked (If blocked by the
other side).
User's Manual
140
User's Manual
Figure 7-1: MEGACO-R2 Call Disconnect Flow Diagram

Terminator Disconnects
MFCR2
H.248
Outgoing MG
H.248
MGC
MFCR2
Incoming MG
Clear back
NOTIFY(OE=77{icas/cb})
Wait for
Disconnect
timer
MODIFY(SG{icas/cb},
E=88{icas/cf})
Clear back
Clear forward
NOTIFY(OE=88{icas/cf})
MODIFY(SG{ibcas/cf},
E=99{icas/rlg})
Clear forward
Release guard
NOTIFY(OE=99{icas/rlg})
MODIFY(SG{icas/rlg},
E=99{bcas/idle})
Release guard
Idle
NOTIFY(OE=99{bcas/idle})
MODIFY(SG{bcas/idle})
Idle
Note: The disconnection from the originator side looks the same. It only starts
from the Clear forward line signal. Also, even though the idle notification is
sent regardless of the bcas/idle signal, this signal is still required for the
internal state machine.
Version 4.8
141
January 2006
Mediant 3000
7.2.2.11
RFC 2833 Support

DTMF Transport Type can be set to use RFC 2833 through configuration or
dynamically through MEGACO commands.
Note: RFC 2833 support is only applicable when running Voice Over IP traffic. It
is not relevant on Voice over ATM.
Configuration is performed through the ini file (the DTMFTransportType=3 parameter),

or through the Web. This value is used by MEGACO as the default value, but
commands can override it.
To enable RFC 2833 via a command, add a payload type in the media line of the SDP
and define this payload type to be RF 2833 according to the following example:
v=0
c= IN IP4 $
m=audio $ RTP/AVP 0 97
a=rtpmap:97 telephone-event 0-15
'telephone-event' is the name defined in RFC 2833, and 97 is used as the payload
number (any number from the dynamic range can be used).
Negotiation is performed according to the following rules:
If the remote side does not specify the 'telephone-event' in the SDP, the Mediant
3000 uses the default value as the transport type.
If the local and remote payload types are different, the remote payload number is
used.
Therefore, if a user needs to activate the RFC 2833 only when both sides agree on it,
users should configure the default value to be different to RFC 2833 (e.g.,
Transparent).
7.2.2.12
Silence Suppression Support

Silence suppression can be enabled in two ways:
1. Configure it to ON through one of the configuration tools. This is a static way, and
applies to all calls.
2. Use the SDP attribute a=silencesupp:on both for the local and remote side. This is
done on a per call basis.
Silence suppression can be disabled by:
1. Setting it to OFF in the ini file. This is a static way, and applies to all calls.
2. For G.729 or G.723 - If the remote descriptor contains the a=fmtp line with
annexb=no (G.729) or annexa=no (G.723). Note that the default for the annex fields in
the SDP is Yes. Therefore, if this line is omitted, the assumption is that this side
supports the silence suppression according to the annex.
3. Using the SDP attribute a=silencesupp:off in the local or remote side. This is
performed on a per call basis. Note that the silencesupp attribute is specified only in
User's Manual
142
User's Manual

RFC 3108 (SDP for ATM). However, as parsers ignore fields they do not recognize, it
is legal to use it for IP also, assuming that the call manager is capable of doing it.
4. In all other cases, the Mediant 3000 default value is used.
The table below summarizes the operation of silence suppression:
Table 7-20: Silence Suppression Operation

CONFIG G.711
Setting
OFF
ON
G.723
G.729
ON only if:
ON only if:
ON only if:
- a=silencesupp:on
- a=silencesupp:on
a=silencesupp:on
AND
AND
AND
- payload 13 was
offered on both sides
- remote SDP does not contain - remote SDP does not contain
the line
the line
a=fmtp:4 annexa=no
a=fmtp:18 annexb=no
OFF only if:
OFF only if:
OFF only if:
- a=silencesupp:off
- a=silencesupp:off
- a=silencesupp:off
OR
OR
- remote SDP contains the line
- remote SDP contains the line
a=fmtp:4 annexa=no
a=fmtp:18 annexb=no
7.2.2.13
Fax T.38 and Voice Band Data Support (Bypass Mode)
7.2.2.13.1
Support of Fax and modem type by default parameters

Previous loads supported T.38 without MEGACO interference, if the Mediant 3000
was configured to support T.38:
FaxTransportType should be configured to T.38 Relay.
Fax redundancy can be controlled using the configuration parameter

FaxRelayRedundancyDepth. This parameter controls only non-V21 packets. For
V21 packets that carry important data, the redundancy depth is hard-coded to be
4.
The fax port is assumed to be the RTP port + 2, both for the local and remote
side.
Following these rules, transition to T.38 is performed automatically upon detection.

Bypass (VBD) mode is also supported by using ini file parameters:
Version 4.8
FaxTransportType should be configured to be Bypass.
VxModemTransportType (x stands for 21, 22, 23, 32, 34) should be configured to
Bypass.
The packetization period is configured by the parameter

FaxModemBypassBasicRTPPacketInterval.
143
January 2006
Mediant 3000
7.2.2.13.2
The payload to be used is configured by the parameter FaxBypassPayLoadType

and ModemBypassPayloadType.
Negotiating Fax and Modem type via SDP

Support of the Fax type (T.38, Bypass or Transparent) and modem type (Bypass,
Transparent) was added to the SDP according to the following rules:
If the Call Manager wants this call to support T.38, it should send an additional
line in the local SDP to the Mediant 3000, as in the following example:
v=0
c= IN IP4 $
m=audio $ RTP/AVP 0
m=image $ udptl t38
The first three lines describe the voice stream, and can differ according to the user's
requirements. Attributes to the voice ('a' lines) should be added after the first 'm' line.
The 'm=image' line, however, is mandatory, and should appear in the identical format
to the above.
The Mediant 3000 returns a fully specified line with the local port used for the T.38.
Fax redundancy can be requested by including the following attribute line after
the 'm=image' line:
a=T38FaxUdpEC:T38UdpRedundancy
This parameter is only applicable for non-V21 packets. For V21 packets, the
redundancy is hard coded 4.
Two modes of fax support are available. The modes are chosen by the value of bit 2
(value 4) of the MEGACO profiling parameter MGCPCompatibilityProfile. If this bit is
not set, the Mediant 3000 uses a positive negotiation:
If the 'm=image' line is not received both in local AND in remote descriptors, the
Mediant 3000 works with the defaults defined in the Mediant 3000. For example,
if the Mediant 3000 is configured to work with T.38 (default setting) and the
'm=image' line is received in the local description only, the Mediant 3000 still
works with T.38.
If the fax redundancy attribute line does not appear both in local and remote
descriptors, the Mediant 3000 uses the default value.
The modems transport type and payload will be set according to the configuration
defaults as before.
However, if bit 2 is set, the negotiation rules are as follows:
User's Manual
If the 'm=image' line is not received both in local AND remote descriptors, T.38 is
NOT used.
If the local SDP "m=audio" line contains the G.711 coder in addition to another
voice coder, the fax (if not set previously to T.38) and modem mode is Bypass
(VBD), and the G.711 payload type is used for the fax and modem. Note that this
is a proprietary way to define a VBD coder. This can be avoided by using the
V.152 VBD attribute (See next section).
144
User's Manual
7.2.2.14
If the additional G.711 coder is not offered in the local SDP the Fax (if not set to
T.38) and modem Transport Type is Transparent.
descriptors, redundancy for non-V21 packets is NOT used.
Digits Collection Support

The following methods for digit collection are supported:
7.2.2.15
One by one collection using the single events in the 'dd' package (e.g., dd/d3).
Note that if the wildcarded format is used (dd/*), we will report the stat digit and
end digit events (e.g dd/std{tl=d1} and dd/etd{tl=d1}) and not the specific digit
event (e.g. dd/d1).
Collection according to digit map. This includes the basic collection dd/ce event
defined in the basic package and the xdd/xce and edd/mce, both defined it
H.248.16. The maximal pattern length is 150 bytes, and the maximal collected
number is 30 digits. For the extended digit collection, the buffering of type ahead
digits continues up to the limit of 30 digits. New digits after that are lost.
Reporting Fax Events

Some of the Fax events can be reported using the packages from H.248.2: "CTYP"
and "IPFAX". The only Fax events reported by the "CTYP" package are the "V21flag"
and cng, using the "ctyp/dtone" event.
The reported Fax states are "CONNECTED" and "EOF". "CONNECTED" is reported
when the MEGACO application gets "EVENT_DETECT_FAX" from the board. "EOF"
is reported when the MEGACO application gets "EVENT_END_FAX" from the board.
The number of Fax pages is reported in the statistics descriptor when this descriptor is
requested. The number of Fax pages can also be audited during the Fax.
7.2.3
SDP Support in MEGACO

MEGACO supports basic SDP, as defined in RFC 2327. It also supports SDP-ATM,
as defined in RFC 3108. The SDP parser can receive all lines defined in the RFC, but
it ignores all but the following lines: v, c, m, a.
In addition to the above four lines, the outgoing SDP can contain the t s o lines,
which are mandatory in some non-MEGACO applications. This option is controlled by
the ini file parameter MGCPCompatibilityProfile, by adding the number 8 to the
current value (2). For the SDP to have these lines, set the ini file parameter to 10.
In the a line, the general supported attributes in SDP are:
SILENCESUPP:VAL
(VAL=on or off) - To turn silence suppression on or off (defined in RFC 3108)
RTPMAP
Used for dynamic payload mapping, to map the number to the coder. The format
is:
a=rtpmap: 97 G723/8000/1
Where:
Version 4.8

G723 is the encoding name
145
January 2006
Mediant 3000
ATMMAP
Used for dynamic payload mapping in ATM networks, to map the number to the
coder. The format is:
a=atmmap:
97 AMR/8000/1
Where:
a=fmtp:

AMR is the encoding name
FMTP
Defines the dynamic payload mapping for the session. For example for where 97
is the payload number to be used and the bitrate is a G.723 coder parameter, the
following line should be used:
97 bitrate=5.3
Other supported parameters are:
mode-set - Defines for the AMR and the X-NETCODER coder,
which mode is: used (0-7)
annexa - Defines for G.723 if silence suppression is on (yes or no)
annexb - Defines for G.729 if silence suppression is on (yes or no)
PTIME
Defines the packetization time for the session. For example for setting
packetization time to 20 msec, the following line should be used:
a=ptime: 20
Other attributes are supported according to specific feature required (see below).
7.2.3.1
SDP Support Profiling

While adding support for new SDP features, the old behavior must be retained. This is
carried out by adding a new ini/Web parameter cpSDPProfile. This parameter is a
bit map, which currently allows for the following:
7.2.3.2
Bit 0 (Value 1) defines when set the support of RFC 3407 (Simple capabilities)
Bit 1 (Value 2) defines when set the support of V.152 (Voice Band Data).
Selecting a Coder or Ptime Using an Under-Specified Local

Descriptor
Before the current version, the supported under-specified fields in the SDP had been:
IP address
Port
Payload
Added from the version 4.8, the Profile and Ptime are also supported, as in the
following example:
User's Manual
c=IN IP4 $
m=audio $ $ $
a=ptime:$
146
User's Manual
The reply is a list of all supported coders.
7.2.3.3
RFC 3407 Support Simple Capabilities

RCF 3407 defines a minimal and backward-compatible capability declaration feature
in SDP by defining a set of new SDP attributes. Together, these attributes define a
capability set, which consists of a capability set sequence number followed by one or
more capability descriptions.
Each capability description in the set contains
information about supported media formats, but the endpoint is not required to use
any of these. In order to actually use a declared capability, session negotiation must
be carried out by the call manager.
Example 1
The following call flows example illustrates the usage of this capability:
MEGACO/1 [10.2.1.228]:2944
Transaction = 10264 {
Context = $ {
Add = $ {Media {
LocalControl {
Mode = Receiveonly
},
Local {
v=0
c=IN IP4 $
m=audio $ RTP/AVP 0
m=image $ UDPTL t38
},
Remote {
v=0
c=IN IP4 10.4.4.46
}}}}}
The reply to this is:
MEGACO/1 [10.4.4.46]:2944
P=10264{
C=2{
A = gwRTP/1{
M{
L{
v=0
c=IN IP4 10.4.4.46
a=sqn: 0
a=cpar: a=T38FaxMaxBuffer:1024
a=cpar: a=T38FaxMaxDatagram:238
a=ptime:20
a=silencesupp:off - - - }}}}}
In this case, the local was requested to use both audio and image, but the remote
supports only the audio. The reply will return the image as a capability, in the session
level.
Example 2
Version 4.8
147
January 2006
Mediant 3000
In this example the capabilities are displayed both in the session and in the media
level:
MEGACO/1 [10.2.1.228]:2944
Transaction = 10265 {
Context = $ {
Add = $ {Media {
LocalControl {
Mode = Receiveonly
},
Local {
v=0
c=IN IP4 $
m=audio $ RTP/AVP 0 18 4
m=image $ UDPTL t38
},
Remote {
v=0
c=IN IP4 10.4.4.46
}}}}}
The reply to this is:

MEGACO/1 [10.4.4.46]:2944
P=10265{
C=3{
A = gwRTP/2{
M{
L{
v=0
c=IN IP4 10.4.4.46
a=sqn: 0
a=cpar: a=T38FaxMaxBuffer:1024
a=cpar: a=T38FaxMaxDatagram:238
a=ptime:20
a=silencesupp:off - - - a=cdsc: 2 audio RTP/AVP 0 18 4
a=cpar: a=fmtp:18 annexb=yes
a=cpar: a=rtpmap:4 G723/8000/1
a=cpar: a=fmtp:4 bitrate=6.3;annexa=yes
a=cpar: a=ptime:20
a=cpar: a=silencesupp:off - - - }}}}}
In Example 2, the local was requested to use both audio and image, but the remote
supports only the audio and parts of the coders. The reply returns the image as a
capability in the session level and the fully supported coders in the media level.
7.2.3.4
Fax T.38 and Voice Band Data Support (Bypass Mode)
7.2.3.4.1
Support of Fax and modem type by default parameters

Previous loads supported T.38 without MEGACO interference, if the Mediant 3000
was configured to support T.38:
User's Manual
148
User's Manual
FaxTransportType should be configured to T.38 Relay.
Fax redundancy can be controlled using the configuration parameter

FaxRelayRedundancyDepth. This parameter controls only non-V21 packets. For
V21 packets that carry important data, the redundancy depth is hard-coded to be
4.
The fax port is assumed to be the RTP port + 2, both for the local and remote
side.
Following these rules, transition to T.38 is performed automatically upon detection.

Bypass (VBD) mode is also supported by using ini file parameters:
7.2.3.4.2
FaxTransportType should be configured to be Bypass.
VxModemTransportType (x stands for 21, 22, 23, 32, 34) should be configured to
Bypass.
The packetization period is configured by the parameter

FaxModemBypassBasicRTPPacketInterval.
The payload to be used is configured by the parameter FaxBypassPayLoadType

and ModemBypassPayloadType.
Negotiating Fax and Modem type via SDP

Support of the Fax type (T.38, Bypass or Transparent) and modem type (Bypass,
Transparent) was added to the SDP according to the following rules:
If the Call Manager wants this call to support T.38, it should send an additional
line in the local SDP to the Mediant 3000, as in the following example:
v=0
c= IN IP4 $
m=audio $ RTP/AVP 0
m=image $ udptl t38
The first three lines describe the voice stream, and can differ according to the user's
requirements. Attributes to the voice ('a' lines) should be added after the first 'm' line.
The 'm=image' line, however, is mandatory, and should appear in the identical format
to the above.
The Mediant 3000 returns a fully specified line with the local port used for the T.38.
Fax redundancy can be requested by including the following attribute line after
the 'm=image' line:
a=T38FaxUdpEC:T38UdpRedundancy
This parameter is only applicable for non-V21 packets. For V21 packets, the
redundancy is hard coded 4.
Two modes of fax support are available. The modes are chosen by the value of bit 2
(value 4) of the MEGACO profiling parameter MGCPCompatibilityProfile. If this bit is
not set, the Mediant 3000 uses a positive negotiation:
Version 4.8
If the 'm=image' line is not received both in local AND in remote descriptors, the
Mediant 3000 works with the defaults defined in the Mediant 3000. For example,
149
January 2006
Mediant 3000
if the Mediant 3000 is configured to work with T.38 (default setting) and the
'm=image' line is received in the local description only, the Mediant 3000 still
works with T.38.
descriptors, the Mediant 3000 uses the default value.
The modems transport type and payload will be set according to the configuration
defaults as before.
However, if bit 2 is set, the negotiation rules are as follows:
7.2.3.5
If the 'm=image' line is not received both in local AND remote descriptors, T.38 is
NOT used.
If the local SDP "m=audio" line contains the G.711 coder in addition to another
voice coder, the fax (if not set previously to T.38) and modem mode is Bypass
(VBD), and the G.711 payload type is used for the fax and modem. Note that this
is a proprietary way to define a VBD coder. This can be avoided by using the
V.152 VBD attribute (See next section).
If the additional G.711 coder is not offered in the local SDP the Fax (if not set to
T.38) and modem Transport Type is Transparent.
descriptors, redundancy for non-V21 packets is NOT used.
Support of RFC 3264

The terms, oferrer and answerer used her, are originally defined in RFC 3264. This
RFC is currently partially supported. The Mediant 3000 can receive a media line with
port number 0, and treat it as a statement that this is not supported.
7.2.3.5.1
Support of V.152 - VBD Attribute

The V.152 defines a way to declare support of VBD (Voice Bond Data), and define
which coder and payload will be used for it. This is done by using a new SDP attribute
'gpmd'. (See http://www.ietf.org/internet-drafts/draft-rajeshkumar-mmusic-gpmd-03.txt
for more information about this General Purpose Media Description attribute.
The below is an example from V.152. It shows how we define the VBD support using
the new attribute:
m=audio 3456 RTP/AVP 18 0 13 96 98 99
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15, 34, 35
a=rtpmap:98 PCMU/8000
a=gpmd:98 vbd=yes
a=rtpmap:99 G726-32/8000
a=gpmd:99 vbd=yes
In the example the sender supports voice on G729 and PCMU, and VBD data on both
PCMU with payload 98, and G726-32 with payload 99. This new attribute enables the
use of the same coder but with two different payload types.
The behavior of the board will depend on a new bit in the SDP profile parameter (See
above). If the profile is off, the behavior stays as before, with the following additions:
User's Manual
If we get only under specified local descriptor from the MGC (Oferrer), and it
contains a VBD attribute, our answer will include it.
150
User's Manual
If we get both local and remote descriptors (Answerer), and the remote contains a
VBD attribute, our answer will include it if the negotiation succeeds.
When the profile bit is turned on, the behavior will be as follows:
If we get only under specified local descriptor from the call manager (Oferrer), we
will include the VBD attribute if the G.711 coder existed in the request (for
backward compatibility) or a VBD was specified in the request. In the first case
(only G.711), we will return the G.711 as a normal voice coder, but also add a
new dynamic payload with the same G.711 coder to indicate that we support VBD
for it. (See example 1 below)
If we get both local and remote descriptors (Answerer), and the local contains
G.711, and the remote contains this G.711 and VBD, we will adopt the payload of
the remote for our VBD. (See example 2 below)
Example 1:
The received SDP:
Local{
v=0
c=IN IP4 $
}
The reply for this will be:
Local{
v=0
c=IN IP4 10.4.4.46
m=audio 4000 RTP/AVP 18 0 104
a=gpmd:104 vbd=yes
}
Example 2:
The received SDP:
Local{
v=0
c=IN IP4 $
},
remote{
v=0
c=IN IP4 10.4.4.46
a=gpmd:104 vbd=yes
}
The reply for this will be:
Local{
v=0
c=IN IP4 10.4.4.46
a=gpmd:104 vbd=yes
}
Version 4.8
151
January 2006
Mediant 3000
7.2.3.6
Media Encryption (SRTP) using RFC 3711

SRTP (RFC 3711) details the media encryption standard. The Mediant 3000 partially
implements it. RFC 3711 defines a new media profile RTP/SAVP for use in secured
streams. (The non-secured profile is RTP/AVP).
SRTP defines how to encrypt the media, but does not define how to negotiate the key.
For negotiation with the key, the method used is defined in http://www.ietf.org/internetdrafts/draft-ietf-mmusic-sdescriptions-09.txt.
is draft defines a cryptographic attribute for SDP to use for media encryption.
There is no official definition for how to use this in MEGACO, therefore, the following
describes the implementation.
7.2.3.6.1
Supported Suites
The
Mediant
3000
SRTP
implementation
is
limited
to
AES_CM_128_HMAC_SHA1_32, AES_CM_128_HMAC_SHA1_80. All other suites
are ignored.
The SRTP suite may hold many keys and key parameters. The Mediant 3000
supports a single key and no key parameters, suites that are provided with many keys
or key parameters are ignored, and marked as not valid. A suite that contains extra
parameters is rejected even if it is a suite that is supported.
7.2.3.6.2
Configuration and Activation

The Mediant 3000 supports two packages of media encryption, TGCP and SRTP.
MEGACO, however, supports only SRTP.
The following defines the encryption support level:
1.
DSP template - Templates 0 and 2 support SRTP and template 3 supports

TGCP.
2.
Feature Key Enables/Disables media encryption on the board.
3.
ini file parameter The parameter, EnableMediaSecurity, defines SRTP

support when set to Enable.
Even if the board is configured to support encryption, the actual activation must be
done on a per command basis. Activation of a secured connection is done by sending
to the board a local descriptor in which the transport method is RTP/SAVP (defined
in RFC 3711). The local descriptor may contain more parameters regarding the
encryption as described below.
7.2.3.6.3
SDP Definition
The following attribute is defined in http://www.ietf.org/internet-drafts/draft-ietf-mmusicsdescriptions-09.txt
a=crypto:<tag> <crypto-suite> <key-params> [<session-params>]
The fields tag, crypto-suite, key-params, and session-params are described in the
sub-sections below, and an example is provided of the crypto attribute for the
"RTP/SAVP" transport, i.e., the secure RTP extension to the Audio/Video Profile [srtp].
In the following, new lines are included for formatting purposes only:
User's Manual
152
User's Manual
inline:PS1uQCVeeCFCanVmcjkpPywjNWhcYD0mXXtxaVBR|2^20|1:32
In MEGACO, the following fields are allowed to be under specified:
Tag If the tag is under specified, the rest of the line can be omitted. This
means that the gateway returns all the supported suites. for the Mediant 3000,
the following is expected when sending a=crypto:$:
crypto-suite If the crypto suite is under specified, the gateway may chose one
of the supported suites. In this case, however, the key params field should also
exist and contain $. The answer to a=crypto:1 $ $ is, for example:
key-params When the key param is under specified, it means that the sender
wants a specific suite, and wants the gateway to produce the key. an example of
the request is:
a=crypto:1 AES_CM_128_HMAC_SHA1_80 $
and the reply:
7.2.3.6.4
Connection Negotiation
The examples below show the creation of a secured connection via the ADD
command. This can also be done by the Modify command. In this case, the
connection starts in a non-secured mode and updated to a secured mode. (The
opposite is also possible to start with secured mode and move to a non-secured
mode).
Simple Offerer for Secured Connection
In this example, the call manager sends an under specified SDP, and requests a
secured connection. Note that there are no attribute lines for SRTP, and this is
considered as if a=crypto:$ was received: (Refer to the previous section, item 1).
The MGC sends:
MEGACO/1 [10.2.1.228]:2944
Transaction = 1 {
Context = $ {
Add = $ {Media {LocalControl {
Mode = Receiveonly},
Local {
v=0
c=IN IP4 $
m=audio $ RTP/SAVP 0
a=ptime:20
}}}}}
Version 4.8
153
January 2006
Mediant 3000
The Gateway answers:

MEGACO/1 [10.4.4.46]:2944
P = 1 {
C = $ {
A = $ {M {O {
MO = Receiveonly},
L {
v=0
c=IN IP4 10.4.4.46
m=audio 4000 RTP/SAVP 0
a=ptime:20
}}}}}
Simple Offerer for Both Secured and Non-Secured Connection

In this example, the call manager sends an under specified SDP, but this time
requests both secured and non-secured connections. This is the more general
scenario, as the MGC must make sure that if the remote side does not support SRTP,
the call does not fail (assuming that there is no request for a secured only call).
Note that there are no attribute lines for SRTP, and this is considered as if
a=crypto:$ was received: (Refer to the previous section, item 1).
The MGC sends:
MEGACO/1 [10.2.1.228]:2944
Transaction = 2 {
Context = $ {
Local {
v=0
c=IN IP4 $
m=audio $ RTP/AVP 0
a=ptime:20
}}}}}

MEGACO/1 [10.4.4.46]:2944
P = 2{
C = 2 {
A = GWRTP/2 {M {O {
MO = Receiveonly},
L {
v=0
c=IN IP4 10.4.4.46
User's Manual
154
User's Manual
a=ptime:20
}}}}}
Oferrer Choosing One Suite

In this example, the MGC wants the Gateway to choose one suite. The Gateway
chooses the suite and also the key.
The MGC sends:
MEGACO/1 [10.2.1.228]:2944
Transaction = 3 {
Context = $ {
Local {
v=0
c=IN IP4 $
a=crypto:1 $ $
a=ptime:20
}}}}}

MEGACO/1 [10.4.4.46]:2944
P = 3 {
C = 3 {
A = GWRTP/3 {M {O {
MO = Receiveonly},
L {
v=0
c=IN IP4 10.4.4.46
a=ptime:20
}}}}}
Oferrer Suite is Defined

In the example, the MGC wants the Gateway to work with a specific suite and produce
the key. The Gateway returns the chosen key:
The MGC sends:
MEGACO/1 [10.2.1.228]:2944
Transaction = 4 {
Context = $ {
Local {
v=0
c=IN IP4 $
a=crypto:1 AES_CM_128_HMAC_SHA1_32 $
Version 4.8
155
January 2006
Mediant 3000
a=ptime:20
}}}}}

MEGACO/1 [10.4.4.46]:2944
P = 4 {
C = 4 {
A = GWRTP/4 {M {O {
MO = Receiveonly},
L {
v=0
c=IN IP4 10.4.4.46
a=ptime:20
}}}}}
Answerer Local Parameters Not Defined

In this example, the MGC sends the basic SDP to the local side and the offered data
from the remote side. The Gateway negotiates the data and returns the result:
The MGC sends:
MEGACO/1 [10.2.1.228]:2944
Transaction = 4 {
Context = $ {
Local {
v=0
c=IN IP4 $
a=ptime:20
},
Remote {
v=0
c=IN IP4 10.4.4.46
a=ptime:20
}}}}}

MEGACO/1 [10.4.4.46]:2944
P = 4 {
C = 5 {
A = GWRTP/5 {M {O {
MO = Receiveonly},
L {
v=0
User's Manual
156
User's Manual
c=IN IP4 10.4.4.46

inline:8375hrytsqnkhecPOE/8732xurnrtd
a=ptime:20
}}}}}
Error Cases
The negotiation results in an error if there is no supported SDP at the end of it. This
can be caused by one of the following:
7.2.4
1.
The MGC requests a secured connection ONLY, but the Gateway does not
support it.
2.
The Gateway supports SRTP, but not the suite requested by the MGC.
3.
The remote side sends SDP with a secured connection ONLY and the Gateway
does not support it.
4.
The suites sent by the remote side are not supported by the Gateway.
5.
The suite (sent by MGC or remote side) is supported, but there are session
parameters that are not support or contains more than one key.
Mapping Payload Numbers to Coders

The table below shows the default mapping between payload numbers and coders
when the dynamic payload assignment is not used. Note that this is a general table
and only the DSP template that is loaded to a Mediant 3000 defines which coder is
supported on this Mediant 3000.
These values can be overridden by the external CoderTbl.
Table 7-21: Table 32: MEGACO Mapping Payload Numbers to Coders

Default Payload
Number
Encoding Name
Coder
PCMU
G711Mulaw
"G726-32"
G726_32
"GSM"
GSM
84
GSM-EFR
GSM-EFR
"G723"
G723 (High)
80
"G723"
G723 (Low)
"PCMA"
G711Alaw_64
15
"G728"
G728
18
"G729"
G729
35
"G726-16"
G726_16
36
"G726-24"
G726_24
Version 4.8
157
January 2006
Mediant 3000

Default Payload
Number
Encoding Name
Coder
38
"G726-40"
G726_40
39
"X-G727-16"
G727_16
40
"X-G727-24-16"
G727_24_16
41
"X-G727-24"
G727_24
42
"X-G727-32-16"
G727_32_16
43
"X-G727-32-24"
G727_32_24
44
"X-G727-32"
G727_32
45
"X-G727-40-16"
G727_40_16
46
"X-G727-40-24"
G727_40_24
47
"X-G727-40-32"
G727_40_32
49
"X-NETCODER"
NetCoder_4_8
50
"X-NETCODER"
NetCoder_5_6
51
"X-NETCODER"
NetCoder_6_4
52
"X-NETCODER"
NetCoder_7_2
53
"X-NETCODER"
NetCoder_8
54
"X-NETCODER"
NetCoder_8_8
55
"X-NETCODER"
NetCoder_9_6
56
"X-CCD"
Transparent
60
"EVRC0"
EVRC0
81
"X-EVRC-TFO"
EVRC (TFO)
61
"X-QCELP-8"
QCELP_8
82
"X-QCELP-8-TFO"
QCELP_8_TFO
62
"QCELP"
QCELP_13
83
"X-QCELP-TFO"
QCELP_13_TFO
63
"G729E"
G.729E
64
"AMR"
AMR (4.75)
65
"AMR"
AMR (5.15)
66
"AMR"
AMR (5.9)
67
"AMR"
AMR (6.7)
68
"AMR"
AMR (7.4)
User's Manual
158
User's Manual

Default Payload
Number
Encoding Name
Coder
69
"AMR"
AMR (7.95)
70
"AMR"
AMR (10.2)
71
"AMR"
AMR (12.2)
100
iLBC
iLBC (13)
101
iLBC
iLBC (15)
102
BV16
BV16
96
telephone-event
RFC 2833
104
RED
Redundancy per RFC 2198
13
CN
Comfort Noise
Note: When using dynamic payloads, do not use the Mediant 3000 default
payloads for RFC 2833 (96) and RFC 2198 (104). If these values must be
used, the default values for the two RFCs should be changed in the ini file.
7.2.5
Supported MEGACO Packages

Events, signals, properties and statistics are grouped in packages. A package can be
extended by a new package. In this case, the basic package becomes a part of the
new package.
The TrunkPack series MEGACO protocol supports the basic set of packages as
defined in Annex E of RFC 3015 (Refer to the document at www.letf.org/rfc/, 'RFC
Index'.), according to the device type. For example, the Analog Line package is
supported only for analog devices.
Note: Unlike MGCP, for MEGACO, the MGC must define ALL events for which it
requires notification. There are NO persistent events in MEGACO.
7.2.5.1
Generic Media Package - G

Symbol
Definition
cause
Version 4.8
Type
General failure report
159
Event
January 2006
Mediant 3000

Symbol
Definition
sc
Type
Signal completion
Event
Notes are for all MEGACO Package tables:
7.2.5.2
S:
The signal type; the following symbols identify the type of signal:
OO signal:
The ON/OFF signal is turned ON until commanded by the Call Agent

to turn it OFF, and vice versa.
TO signal:
The Timeout signal lasts for a given duration unless it is superseded

by a new signal.
BR signal:
The Brief signal event has a short, known duration.
Duration:
Specifies the duration of TO signals. The specified number is used

only if no other duration is given in the command or in the CPT file.
Base Root Package - ROOT
Table 7-23: Base Root Package - ROOT

Symbol
Definition
maxNumberOfContexts
Maximum number of Contexts in the

device
Property
maxTerminationsPerContext
Maximum Terminations in a Context
Property
normalMGExecutionTime
Timer for Retransmission
Property
normalMGCExecutionTime
Property
MGProvisionalResponseTimerValue
Property
MGCProvisionalResponseTimerValue
Property
7.2.5.3
Type
Tone Generator Package - ToneGen
Table 7-24: Tone Generator Package - ToneGen

Symbol
pt
User's Manual
Definition
Plays audio tone
Type
S
Signal
160
Duration
TO
User's Manual
7.2.5.4
Tone Detection Package - ToneDet
Table 7-25: Tone Detection Package - ToneDet

Symbol
Definition
Type
std
Detects the start of a tone
Event
etd
Detects the end of a tone
Event
ltd
Detects a long tone
Event
7.2.5.5
DTMF Generator Package - DG (Extends ToneGen)
Table 7-26: DTMF Generator Package - DG

Symbol
Definition
Type
Duration
d0
DTMF 0
Signal
BR
d1
DTMF 1
Signal
BR
d2
DTMF 2
Signal
BR
d3
DTMF 3
Signal
BR
d4
DTMF 4
Signal
BR
d5
DTMF 5
Signal
BR
d6
DTMF 6
Signal
BR
d7
DTMF 7
Signal
BR
d8
DTMF 8
Signal
BR
d9
DTMF 9
Signal
BR
ds
DTMF *
Signal
BR
do
DTMF #
Signal
BR
da
DTMF A
Signal
BR
db
DTMF B
Signal
BR
dc
DTMF C
Signal
BR
dd
DTMF D
Signal
BR
Version 4.8
161
January 2006
Mediant 3000
7.2.5.6
DTMF Detection Package - DD (Extends ToneDet)
Table 7-27: DTMF Detection Package - DD

Symbol
Definition
Type
ce
DigitMap Completion Event
Event
d0
DTMF 0
Event
d1
DTMF 1
Event
d2
DTMF 2
Event
d3
DTMF 3
Event
d4
DTMF 4
Event
d5
DTMF 5
Event
d6
DTMF 6
Event
d7
DTMF 7
Event
d8
DTMF 8
Event
d9
DTMF 9
Event
ds
DTMF *
Event
do
DTMF #
Event
da
DTMF A
Event
db
DTMF B
Event
dc
DTMF C
Event
dd
DTMF D
Event
7.2.5.7
Call Progress Tones Generator Package - CG (Extends ToneGen)
Table 7-28: Call Progress Tones Generator Package - CG

Symbol
Definition
Type
Duration
Map to CPT File
dt
Dial tone
Signal
TO
180 sec
rt
Ringing tone
Signal
TO
180 sec
bt
Busy tone
Signal
TO
180 sec
ct
Congestion tone
Signal
TO
180 sec
User's Manual
162
User's Manual
Table 7-28: Call Progress Tones Generator Package - CG

Symbol
Definition
Type
Duration
Map to CPT File
sit
Special Information
tone
Signal
BR
2 sec
wt
Warning tone
Signal
BR
1sec
pt
Payphone
Recognition tone
Signal
TO
180 sec
38
cw
Call Waiting tone
Signal
BR
1 sec
cr
Caller Waiting tone
Signal
TO
180 sec
15
7.2.5.8
Call Progress Tones Detection Package - CD (Extends ToneDet)
Table 7-29: Call Progress Tones Detection Package - CD

Symbol
Definition
Type
dt
Dial tone
Event
rt
Ringing tone
Event
bt
Busy tone
Event
ct
Congestion tone
Event
sit
Special Information tone
Event
wt
Warning tone
Event
pt
Payphone Recognition tone
Event
cw
Call Waiting tone
Event
cr
Caller Waiting tone
Event
7.2.5.9
Network Package - NT
Table 7-30: Network Package - NT

Symbol
Definition
jit
netfail
Version 4.8
Type
Maximal jitter buffer size
Property
Network failure
Event
163
January 2006
Mediant 3000
Table 7-30: Network Package - NT

Symbol
Definition
qualert
Type
Quality alert - Not supported
Event
dur
Termination's InContext duration
Statistics
os
Octets sent
Statistics
or
Octets received
Statistics
7.2.5.10
RTP Package - RTP (Extends - NT)
Table 7-31: RTP Package - RTP

Symbol
Definition
pltrans
Type
PayLoad Transition - Not supported
Event
ps
Packets sent
Statistics
pr
Packets received
Statistics
pl
Packet loss
Statistics
jit
Current inter-arrival jitter value
Statistics
Current packets propagation delay
Statistics
delay
7.2.5.11
ATM Package - ATM (Extends - NT)

The ATM package supports only the properties and statistics inherited from the base
Network package. The special events and statistics of this package are not supported.
7.2.5.12
Generic Announcement Package - AN
Table 7-32: Generic Announcement Package

Symbol
Definition
Type
Supported Parameters
apf
Initiates the play of a fixed

announcement
Signal
An - Announcement number
Di - The direction of the announcement
Noc - Number of cycles
apv
Initiates the play of a

variable announcement
Signal
Handled in the same manner as apf
User's Manual
164
User's Manual
7.2.5.13
Expanded Call Progress Tones Generator Package - XCG

(Extends - ToneGen)
Table 7-33: Expanded Call Progress Tones Generator Package - XCG

Symbol
Definition
Type
Duration
Map to CPT File
cmft
Comfort tone
Signal
TO
180 sec
18
roh
Off-hook warning tone
Signal
TO
180 sec
16
nack
Negative
Acknowledgement
Signal
TO
180 sec
19
vac
Vacant Number tone
Signal
TO
180 sec
20
spec
Special Conditions dial

tone
Signal
TO
180 sec
21
7.2.5.14
Basic Service Tones Generation Package - SRVTN

(Extends - ToneGen)
Table 7-34: Basic Service Tones Generation Package - SRVTN

Symbol
rdt
conf
ht
mwt
7.2.5.15
Definition
Type
Duration
Map to CPT File
Recall dial tone
Signal
TO
180 sec
22
Confirmation tone
Signal
BR
1 sec
Held tone
Signal
TO
180 sec
23
Message Waiting tone
Signal
TO
180 sec
17
Expanded Services Tones Generation Package - XSRVTN

(Extends - ToneGen)
Table 7-35: Expanded Services Tones Generation Package - XSRVTN

Symbol
xferdt
cft
Version 4.8
Definition
Type
Duration
Map to CPT File
Call Transfer Dial

Tone
Signal
TO
180 sec
24
Call Forward Tone
Signal
BR
1 sec
25
165
January 2006
Mediant 3000
Table 7-35: Expanded Services Tones Generation Package - XSRVTN

Symbol
Definition
Type
Duration
Map to CPT File
ccst
Credit Card Service

Tone
Signal
BR
1 sec
26
srdt
Special Recall Dial

Tone
Signal
TO
180 sec
27
7.2.5.16
Basic CAS Package - BCAS
Table 7-36: Basic CAS Signal/Events

Symbol
Definition
Type
Duration
Map to CPT File Symbol
sz
Seizure
Signal/Event
BR
None
sza
Seizure ack
Signal/Event
BR
None
ans
Answer
Signal/Event
BR
None
idle
idle
Signal/Event
BR
None
casf
CAS failure
Event
None
7.2.5.17
International CAS Package ICAS (Extends BCAS)
Table 7-37: International CAS Signal/Events

Symbol
Definition
Type
Duration
Map to CPT File Symbol
sls
Subscriber
line status
Signal/Event
BR
None
cf
Clear forward
Signal/Event
BR
None
cb
Clear back
Signal/Event
BR
None
casf
CAS failure
Event
None
rlg
Release
Guard
Signal/Event
Cng
Congestion
Signal/Event
User's Manual
None
BR
166
None
User's Manual
7.2.5.18
CAS Blocking Package - CASBLK
Table 7-38: CAS Blocking Signal/Events

Symbol
Definition
Type
blk
Seizure
Signal/Event
BR
ublk
Answer
Event
7.2.5.19
Duration
Map to CPT File
Symbol
None
None
International CAS compelled Package - ICASC
Table 7-39: ICASC Signal/Events Table

Symbol
Definition
Type
addr
Address
Signal/Event
TO
None
casf
CAS failure
Event
BR
None
cprs
Called party
reachability
status
Signal/Event
TO
None
cng
Congestion
Signal/Event
TO
7.2.5.20
Duration
Map to CPT File
Note
MF Generator Package - MFG (Extends - ToneGen)
Table 7-40: MF Generator Package - MFG

Symbol
Definition
Type
Duration
mf0
MF 0
Signal
BR
mf1
MF 1
Signal
BR
mf2
MF 2
Signal
BR
mf3
MF 3
Signal
BR
mf4
MF 4
Signal
BR
mf5
MF 5
Signal
BR
mf6
MF 6
Signal
BR
mf7
MF 7
Signal
BR
Version 4.8
167
January 2006
Mediant 3000

Symbol
Definition
Type
Duration
mf8
MF 8
Signal
BR
mf9
MF 9
Signal
BR
mfa
MF A
Signal
BR
mfb
MF B
Signal
BR
mfc
MF C
Signal
BR
mfd
MF D
Signal
BR
mfe
MF E
Signal
BR
mff
MF F
Signal
BR
mfg
MF G
Signal
BR
mfh
MF H
Signal
BR
7.2.5.21
MF Detection Package - MFD (Extends - ToneDet)

Symbol
Definition
Type
mf0
MF 0
Event
mf 1
MF 1
Event
mf 2
MF 2
Event
mf 3
MF 3
Event
mf 4
MF 4
Event
mf 5
MF 5
Event
mf 6
MF 6
Event
mf 7
MF 7
Event
mf 8
MF 8
Event
mf 9
MF 9
Event
mfa
MF A
Event
mfb
MF B
Event
mfc
MF C
Event
mfd
MF D
Event
mfe
MF E
Event
User's Manual
168
User's Manual

Symbol
Definition
Type
mff
MF F
Event
mfg
MF G
Event
mfh
MF H
Event
7.2.5.22
Inactivity Timer Package - IT
Table 7-42: Inactivity Timer Package - IT

Symbol
Definition
ito
7.2.5.23
Type
Detects that inactivity timer has

expired
Event
Basic Call Progress Tones Generator with Directionality Package BCG (Extends ToneGen)
Table 7-43: Basic Call Progress Tones Generator with Directionality Package - BCG
Symbol
Definition
Type
Duration
Map to CPT
File
bdt
Dial tone
Signal
TO
180 sec
brt
Ringing tone
Signal
TO
180 sec
bbt
Busy tone
Signal
TO
180 sec
bct
Congestion tone
Signal
TO
180 sec
bsit
Special Information
tone
Signal
BR
2 sec
bwt
Warning tone
Signal
BR
1 sec
bpt
Payphone
Recognition tone
Signal
TO
180 sec
38
bcw
Call Waiting tone
Signal
BR
1 sec
bcr
Caller Waiting tone
Signal
TO
180 sec
15
bpy
Pay tone
Signal
TO
180 sec
Not supported
Version 4.8
169
January 2006
Mediant 3000
7.2.5.24
Extended Digit Collection Package - XDD (Extends DD)
Table 7-44: Extended digit collection Package - XDD

Symbol
Definition
xce
7.2.5.25
Type
Extended Digitmap Completion Event
Event
Enhanced Digits Collection Package - EDD
Table 7-45: Enhanced Digits Collection Package - EDD

Symbol
Definition
mce
7.2.6
Type
Matched Digitmap Completion Event
Event
MEGACO Profiling
Profiling of various MEGACO features is controlled via the ini file parameter
MGCPCompatibilityProfile. Initially, only value 2 has been supported. (Values 0 is
obsolete). Value 1 and 2 are the same and are for supporting MEGACO version 1.
Value 2 is the default value. Additional features are:
7.2.7
Bit 2 (Value 4) -Controls the type of support for the Fax T.38 negotiation. (Refer'
to 'Fax T.38 & Voice Band Data Suppo'rt' on page 143)
Bit 3 (Value 8) - Enables the extra lines in the outgoing SDP ('t' 's' 'o' lines).'
(Refer to 'SDP Support i'n MEGACO' on page 145.)
Bit 4 (Value 16) - Enables the following features:
In the serviceChange request, the Timestamp parameter is omitted.
The audit command on ROOT termination with packages descriptor returns

the total supported packages for the Mediant 3000.
The default packetization period (ptime) for the transparent coder is 10

milliseconds. Using the SDP attribute ptime can change this.
The packetization period for Bypass Fax mode is the same as the
packetization period used for voice. If this bit is not set, the packetization
period for the Fax Bypass is taken from the ini file.
When sending a notification transaction request, the Mediant 3000 does not
mark it as optional.
MEGACO Termination Naming

The basic entities controlled by MEGACO protocol are called Terminations. Physical
Terminations represent a physical entity and ephemeral Terminations represent the
User's Manual
170
User's Manual

stream. Ephemeral Terminations exist only during a connection. From version 4.4, the
terminations names are defined by a new set of pattern parameters, as described in
the next section. Backward Compatibility is kept for the previous Terminations. (Refer
to ''Backward Compatibility'' on page 172.)
7.2.7.1
Termination Name Patterns

Each termination type name is defined by an ini file or SNMP parameter. The pattern
may contain acceptable characters as defined in MEGACO. The '*' character is used
to represent the place where a digit should be. Therefore, it can not be part of the
name itself. All other characters, including slash, are considered text.
For example: The pattern "gws*c*" matches the termination name "gws0c1" and also
"gws10c20". The trunk numbers, in this case, are 0 and 10 and the channels are 1
and 20.
PHYSTERMNAMEPATTERN - Pattern of the physical terminations.
LOGICALRTPTERMPATTERN - Pattern for ephemeral terminations based on

RTP stream.
LOGICALATMTERMPATTERN - Pattern for ephemeral terminations based on

ATM stream.
The starting number of each level can be controlled by a set of parameters:
7.2.7.2
EP_NUM - Controls the numbering of the physical terminations name pattern
EP_NUM_0 - Defines the starting trunk number
EP_NUM_1 - Defines the starting channel number
RTP_NUM - Defines the starting number for the RTP terminations. (The default is
0)
ATM_NUM - Defines the starting number for the ATM terminations. (The default
is 0)
Old Termination Naming Method

Physical Termination names have up to three components: Gateway (in this case the
Mediant 3000) name, Trunk name and Endpoint name (for non-trunking gateways, the
trunk field does not exist).
Ephemeral Termination names have two components: The gateway name and a
constant string - 'RTP/' for RTP terminations and 'ATM/' for ATM terminations. So
assuming that the Mediant 3000 name is 'gw', if the first ephemeral Termination is of
RTP type, it is called 'gwRTP/1', and if it is of ATM type, it is called 'gwATM/1'.
Set the name parts using the following ini file parameters (the last two are used only
for physical Terminations):
'GatewayName', 'TrunkName', 'EndpointName'.
Note that the '/' (the forward slash) should be part of the name used. It is not added
automatically.
Note also that for trunking gateways, the 'TrunkName' can NOT be null. The default
values for the Termination name parts for Trunking boards is the default gateway
name, 'tgw/'; the default trunk name is 's' and the default Endpoint name is '/c'. So the
Termination that represents B-channel 1 of trunk 0 is 'tgw/s0/c1'.
Version 4.8
171
January 2006
Mediant 3000
PSTN Interface - mapping Trunk/B-channel pairs to Endpoints is hardware-specific

(refer to the table, ''MEGACO EndPoint Names'' on page 172.) Note that the number
of supported terminations per Mediant 3000 is equal to the channel density of the
Mediant 3000.
LOGICALRTPTERMPATTERN = "gwrtp/*"
7.2.7.3
Backward Compatibility
The connection between the old naming parameters and the new ones is done by
creating the name pattern from the old name parameters. Let's assume for example
that the old name parameters are:
GATEWAYNAME = "gw"
TRUNKNAME = "s"
ENDPOINTNAME = "chan"
This is equivalent to the following new name parameters:
PHYSTERMNAMEPATTERN = "gws*chan*"
LOGICALRTPTERMPATTERN = "gwrtp/*"
LOGICALATMTERMPATTERN = "gwatm/*"
7.2.7.4
Termination Mapping to a PSTN Interface

The table below describes the mapping between Endpoints and channels for a PSTN
interface, according to the interface type used. The table below assumes the following
initial values:
Channel density - 60
Gateway name = 'Acgw/'
Trunk name = 'T'
Endpoint name = '/C',
The table below lists only the names for a two trunks unit.
Table 7-46: MEGACO Endpoint Names
Endpoint Name
Acgw/T0/C1
Trunk#0/TS1
Trunk#0/TS1
Trunk#0/TS1
Trunk#0/TS1
Acgw/T0/C2
Trunk#0/TS2
Trunk#0/TS2
Trunk#0/TS2
Trunk#0/TS2
Acgw/T0/C3
Trunk#0/TS3
Trunk#0/TS3
Trunk#0/TS3
Trunk#0/TS3
Acgw/T0/C4
Trunk#0/TS4
Trunk#0/TS4
Trunk#0/TS4
Trunk#0/TS4
Acgw/T0/C5
Trunk#0/TS5
Trunk#0/TS5
Trunk#0/TS5
Trunk#0/TS5
Acgw/T0/C6
Trunk#0/TS6
Trunk#0/TS6
Trunk#0/TS6
Trunk#0/TS6
Acgw/T0/C7
Trunk#0/TS7
Trunk#0/TS7
Trunk#0/TS7
Trunk#0/TS7
User's Manual
E1 Transparent 62
T1/J1 - CAS
T1/J1 Transparent
E1 - PRI/CAS
E1 - Transparent
172
T1/J1 - PRI
User's Manual
Endpoint Name
Acgw/T0/C8
Trunk#0/TS8
Trunk#0/TS8
Trunk#0/TS8
Trunk#0/TS8
Acgw/T0/C9
Trunk#0/TS9
Trunk#0/TS9
Trunk#0/TS9
Trunk#0/TS9
Acgw/T0/C10
Trunk#0/TS10
Trunk#0/TS10
Trunk#0/TS10
Trunk#0/TS10
Acgw/T0/C11
Trunk#0/TS11
Trunk#0/TS11
Trunk#0/TS11
Trunk#0/TS11
Acgw/T0/C12
Trunk#0/TS12
Trunk#0/TS12
Trunk#0/TS12
Trunk#0/TS12
Acgw/T0/C13
Trunk#0/TS13
Trunk#0/TS13
Trunk#0/TS13
Trunk#0/TS13
Acgw/T0/C14
Trunk#0/TS14
Trunk#0/TS14
Trunk#0/TS14
Trunk#0/TS14
Acgw/T0/C15
Trunk#0/TS15
Trunk#0/TS15
Trunk#0/TS15
Trunk#0/TS15
Acgw/T0/C16
N/A
Trunk#0/TS16
Trunk#0/TS16
Trunk#0/TS16
Acgw/T0/C17
Trunk#0/TS17
Trunk#0/TS17
Trunk#0/TS17
Trunk#0/TS17
Acgw/T0/C18
Trunk#0/TS18
Trunk#0/TS18
Trunk#0/TS18
Trunk#0/TS18
Acgw/T0/C19
Trunk#0/TS19
Trunk#0/TS19
Trunk#0/TS19
Trunk#0/TS19
Acgw/T0/C20
Trunk#0/TS20
Trunk#0/TS20
Trunk#0/TS20
Trunk#0/TS20
Acgw/T0/C21
Trunk#0/TS21
Trunk#0/TS21
Trunk#0/TS21
Trunk#0/TS21
Acgw/T0/C22
Trunk#0/TS22
Trunk#0/TS22
Trunk#0/TS22
Trunk#0/TS22
Acgw/T0/C23
Trunk#0/TS23
Trunk#0/TS23
Trunk#0/TS23
Trunk#0/TS23
Acgw/T0/C24
Trunk#0/TS24
Trunk#0/TS24
N/A (D-channel)
Trunk#0/TS24
Acgw/T0/C25
Trunk#0/TS25
Trunk#0/TS25
Acgw/T0/C26
Trunk#0/TS26
Trunk#0/TS26
Acgw/T0/C27
Trunk#0/TS27
Trunk#0/TS27
Acgw/T0/C28
Trunk#0/TS28
Trunk#0/TS28
Acgw/T0/C29
Trunk#0/TS29
Trunk#0/TS29
Acgw/T0/C30
Trunk#0/TS30
Trunk#0/TS30
Acgw/T0/C31
Trunk#0/TS31
Trunk#0/TS31
Acgw/T1/C1
Trunk#1/TS1
Trunk#1/TS1
Trunk#1/TS1
Trunk#1/TS1
Acgw/T1/C3
Trunk#1/TS2
Trunk#1/TS2
Trunk#1/TS2
Trunk#1/TS2
Acgw/T1/C3
Trunk#1/TS3
Trunk#1/TS3
Trunk#1/TS3
Trunk#1/TS3
Acgw/T1/C4
Trunk#1/TS4
Trunk#1/TS4
Trunk#1/TS4
Trunk#1/TS4
Acgw/T1/C5
Trunk#1/TS5
Trunk#1/TS5
Trunk#1/TS5
Trunk#1/TS5
Acgw/T1/C6
Trunk#1/TS6
Trunk#1/TS6
Trunk#1/TS6
Trunk#1/TS6
Version 4.8
E1 Transparent 62
T1/J1 - CAS
T1/J1 Transparent
E1 - PRI/CAS
E1 - Transparent
173
T1/J1 - PRI
January 2006
Mediant 3000
Endpoint Name
Acgw/T1/C7
Trunk#1/TS7
Trunk#1/TS7
Trunk#1/TS7
Trunk#1/TS7
Acgw/T1/C8
Trunk#1/TS8
Trunk#1/TS8
Trunk#1/TS8
Trunk#1/TS8
Acgw/T1/C9
Trunk#1/TS9
Trunk#1/TS9
Trunk#1/TS9
Trunk#1/TS9
Acgw/T1/C10
Trunk#1/TS10
Trunk#1/TS10
Trunk#1/TS10
Trunk#1/TS10
Acgw/T1/C11
Trunk#1/TS11
Trunk#1/TS11
Trunk#1/TS11
Trunk#1/TS11
Acgw/T1/C12
Trunk#1/TS12
Trunk#1/TS12
Trunk#1/TS12
Trunk#1/TS12
Acgw/T1/C13
Trunk#1/TS13
Trunk#1/TS13
Trunk#1/TS13
Trunk#1/TS13
Acgw/T1/C14
Trunk#1/TS14
Trunk#1/TS14
Trunk#1/TS14
Trunk#1/TS14
Acgw/T1/C15
Trunk#1/TS15
Trunk#1/TS15
Trunk#1/TS15
Trunk#1/TS15
Acgw/T1/C16
N/A
Trunk#1/TS16
Trunk#1/TS16
Trunk#1/TS16
Acgw/T1/C17
Trunk#1/TS17
Trunk#1/TS17
Trunk#1/TS17
Trunk#1/TS17
Acgw/T1/C18
Trunk#1/TS18
Trunk#1/TS18
Trunk#1/TS18
Trunk#1/TS18
Acgw/T1/C19
Trunk#1/TS19
Trunk#1/TS19
Trunk#1/TS19
Trunk#1/TS19
Acgw/T1/C20
Trunk#1/TS20
Trunk#1/TS20
Trunk#1/TS20
Trunk#1/TS20
Acgw/T1/C21
Trunk#1/TS21
Trunk#1/TS21
Trunk#1/TS21
Trunk#1/TS21
Acgw/T1/C22
Trunk#1/TS22
Trunk#1/TS22
Trunk#1/TS22
Trunk#1/TS22
Acgw/T1/C23
Trunk#1/TS23
Trunk#1/TS23
Trunk#1/TS23
Trunk#1/TS23
Acgw/T1/C24
Trunk#1/TS24
Trunk#1/TS24
N/A (D-channel)
Trunk#1/TS24
Acgw/T1/C25
Trunk#1/TS25
Trunk#1//TS25
Acgw/T1/C26
Trunk#1/TS26
Trunk#1/TS26
Acgw/T1/C27
Trunk#1/TS27
Trunk#1/TS27
Acgw/T1/C28
Trunk#1/TS28
Trunk#1/TS28
Acgw/T1/C29
Trunk#1/TS29
Trunk#1/TS29
Acgw/T1/C30
Trunk#1/TS30
Acgw/T1/C31
Trunk#1/TS31
Note:
User's Manual
E1 Transparent 62
T1/J1 - CAS
T1/J1 Transparent
E1 - PRI/CAS
E1 - Transparent
T1/J1 - PRI
J1 is to be supported in the next applicable release.
174
User's Manual
8. VoATM Media Server Support
VoATM Media Server Support

The Mediant 3000 technology includes Asynchronous Transfer Mode (ATM) network
connectivity, which supports either the ATM Adaptation Layer 1 (AAL1) or ATM
Adaptation Layer 2(AAL2) protocols used in support of bearer network traffic.
The physical interfaces necessary for ATM support used for voice bearer path support
is accomplished utilizing single-mode fiber with either OC-3c or STM-1 interface
speeds.
The technology on which the VoATM media server is based is capable of
distinguishing an AAL1 and AAL2 ATM call request by various aspects of the SDP
when the media gateway controller generates a create connection message.
However, a configuration parameter (ATMApplicationType) is provided to set a default
AAL type to be used should an AAL type not be specified in the call control message.
The AAL type, if included in the call control message, takes precedence over the value
provided by the AALApplicationTypeMask configuration parameter.
For ATM AAL1 networks, VoATM Media Server support for Switched Virtual
Connections (SVCs) is provided. For ATM AAL2 networks, VoATM Media Server
support is provided for both Permanent Virtual Connections (PVCs) and SVCs.
ATM ports on the AudioCodes VoATM media server can have their ATM addresses
automatically configured using the Interim Local Management Interface (ILMI) or, for
AAL2 PVC deployments, they can be manually configured. While the VoATM media
server provides multiple optical interfaces, only one ATM optical interface is used and
supported.
8.1
Related Standards
Table 8-1: Related Standards
Standard
I.366.2 (11/00)
af-vtoa-0089.000
Description
AAL2 type 2 service specific convergence sub-layer for
narrowband services
ATM Trunking using AAL1 for Narrowband Services
Support for Annex C.2 only (no support for Annex C.2.4)
Support for Annex D timing
af-vtoa-0113.000
ATM Trunking Using AAL2 for Narrowband Services

Support for Annex C.1 only, with the exception of section C.1.1
af-sig.0061.000
ATM User-Network (UNI) Signaling Specification Version 4.0

Point to Multi-point is not supported
af-vtoa-0078.000
Circuit Emulation Service (CES) Interoperability Specification

Version 2.0
Support for unstructured DS1/E1 only
No support for CES MIB (section 8.4)
Version 4.8
175
January 2006
Mediant 3000
Table 8-1: Related Standards

Standard
Description
I.363.1 (08/96)
B-ISDN ATM Adaptation Layer specification : Type 1 AAL
I.363.2 (11/00)
B-ISDN ATM Adaptation Layer specification : Type 2 AAL
af-vtoa-0078.000
Circuit Emulation Service (CES) Interoperability Specification

Version 2.0
Support for unstructured DS1/E1 only
RFC-3108
Conventions for the use of the Session Description Protocol

(SDP) for ATM Bearer Connections
Partial support
af-ilmi-0065.000
ILMI Specification Version 4.0

Support for Registration only
I.366.1 (06/98)
Segmentation and Reassembly Service Specific Convergence

Sub-layer for the AAL2 type 2
8.2
ATM AAL1
8.2.1
SVC Access (ATM AAL1)

The VoATM media servers Bearer path connection to an ATM AAL1 based gateway
requires the use of AAL1 SVCs. Of critical importance to the establishment of this
connection is the need to exchange the end-to-end connection identifier (eecid), a 32
bit value, with the AAL1 gateway. The AAL1 bearer path is correlated with the control
plane via the use of the eecid, which is encoded in the Generic Identifier Transport
(GIT) information element during the signaling/setup of the AAL1 SVC. This
information is encoded according to the standard af-sig-0061.00 (ATM UNI Signaling
Specification Version 4.0).
Table 8-2: GIT Information Element Encoding of EECID

Octet
Value
Description
UxEU
Coding standard (ATM forum)
UxUA
Identifier related standard/applications (proprietary)
UxUA
Identifier type (proprietary)
6.1
UxUA
Identifier length
6.2-6.5
EECID value with most significant byte encoded in 6.2

sport protocol supported for the bearer traffic between the AAL1 gateway and the
VoATM media server is AAL1/ATMF 0 (G.711) for -law and AAL1/ATMF 8 (G.711)
for A-law.
User's Manual
176
User's Manual
8.3
ATM AAL2
The VoATM AAL2 implementation provides support of both SVC and PVC
connections.
8.3.1
Bearer Path Selection

For AAL2 PVCs and SVCs and the support of the media services, it is important to
note that there is a specific order in the selection of the bearer path. The selection of
the AAL2 bearer path is based upon the availability of PVCs, as well as SVCs, and is
based upon the following criteria:
8.3.2
PVCs if they exist are selected first. From this, the PVC with the least busy CIDs
is selected first.
Outgoing SVCs from which the one with the busiest CIDs is selected next.
Incoming SVCs from which the one with the busiest CIDs is selected next.
If none of the earlier criteria was satisfied, a new SVC is established.
Voice Profile Selection

The codec negotiation for AAL2 PVCs and SVCs is accomplished using either the
AAL2 ITU 1 or AAL2 ITU 2 voice profiles or through a custom voice profile, Custom
200, as described in the following tables:
Table 8-3: ITU 1 Call Profile

Attribute
G.711 PCM, 64 kbits/s
Payload Length
UUI
40 bytes
Content Duration
0..15
5 msec
Table 8-4: ITU 2 Call Profile

Attribute
Payload Length
UUI
Content Duration
1or 40 bytes
0..15
5 msec
Generic SID (silence)
40 bytes
0..15
5 msec
Table 8-5: Custom 200 Call Profile

Attribute
Payload Length
UUI
Content Duration
40 bytes
0..7
5 msec
G.726 ADPCM, 32 kbps
40 bytes
8..15
10 msec
Version 4.8
177
January 2006
Mediant 3000
Table 8-5: Custom 200 Call Profile

Attribute
Payload Length
UUI
Content Duration
30 bytes
8..15
10 msec
20 bytes
8..15
10 msec
Silence indication
1 byte
0..15
5 msec
8.3.3
PVC Access
Several pieces of critical information are required to access an ATM bearer network
from edge PVCs located on the AudioCodes VoATM media server.
ATM Addresses of the far end AAL2 gateway
The Virtual Path Identifier (VPI) and Virtual Channel Identifier (VCI) of the Virtual
Connection (VC) at the AudioCodes VoATM media server end.
The Virtual Channel Connection Identifier (VCCI) for the VC
This information must be provisioned for the AudioCodes VoATM media server to
account for every AAL2 gateway that it is required to inter-work with over the ATM
network using AAL2 PVCs.
The VCCI range for AAL2 PVCs is 1 to 4095. The VCCI for an AAL2 PVC must be
provisioned with the same value on both the AudioCodes VoATM media server as well
as the far end gateway.
Also of importance is the Channel Identifier (CID), which is negotiated between the
endpoints at call processing time. CID values are selected by the terminating gateway
when a call is initiated over an AAL2 ATM VC. The AudioCodes VoATM media server
is capable of transmission on 247 CID values (9 to 255).
Note that for UMTS
configurations the range of valid CID values is 8 to 255 for 248 CID values and that
the AudioCodes VoATM media server will accept 8 as a valid CID if it has been
selected by the far end gateway.
User's Manual
178
User's Manual
8.3.4
SVC Access (ATM AAL2)

The interconnection of an VoATM media server to an AAL2 based remote gateway via
a single-mode fiber OC3c link using AAL2 based SVCs can be accomplished as
illustrated in the following figure. Note that the GIT information element is used to
convey the VCCI, which is a 13 bit value ranging from 4096 to 8191 as specified in the
standard af-vtoa-0113 (ATM Trunking Using AAL2 for Narrowband Services). Also
note that UNI 4.0 is used for AAL2 SVC establishment signaling.
Figure 8-1: SVC (AAL2) Access to VoATM Media Server
Media Gateway
Controller
H.248
H.248
Gateway
1 fiber port
AudioCodes
VoATM Media
Server
ES
Gateway
ES
ES
ES = Edge Switch
= ATM SVC (Bearer)
= IP signaling channel
ATM Network
Gateway
All AAL2 SVCs are set up according to a unique profile, which specifies the following
AAL2 SVC attributes that can be modified through one of the provisioning interfaces
and are described in Table 88. These attributes are used in the establishment of an
AAL2 ATM SVC. The currently supported media transport protocols between the
AAL2 VoATM based media server and the AAL2 remote gateway are the same as
those mentioned in ''PVC Access'' on page 178. Note that the SVC profile can be
changed and is applied to all subsequently established SVCs.
Table 8-6: SVC Traffic Profile

Value Range
Maximum number of CIDs
Persistence
Default
1 - 247
0 - 600 seconds
180 seconds
This is the number of seconds

that the AAL2 SVC can stay idle
before being released beyond
the end of the dropping of the
Version 4.8
179
January 2006
Mediant 3000
Table 8-6: SVC Traffic Profile

Value Range
Default
last connection.
ATM service category
CBR or rtVBR
rfVBR
Peak cell rate
Integer
200 * (Maximum number of CIDs)
Sustained cell rate
Integer
200 * (Maximum number of CIDs)
Maximum burst size
Integer
8.4
Hairpinning of ATM Connections

The Mediant 3000's functionality includes hairpinning of AAL1 and/or AAL2 ATM
connections. A hairpin connection is a connection that has been established from the
media server back to itself. It is sometimes considered as a loopback connection.
This ability is useful for activities such as doing digit collection on a Bearer Channel
Tandeming (BCT) type connection in which one of the BCT replica streams is
hairpinned back to the media server for the purpose of DTMF collection.
The VoATM hairpin method can be set to one of the following configurations:
None
Under this configuration ATM hairpinning is not supported and any attempt to
loopback a call from the media server back to is denied.
User's Manual
Looped virtual paths (VPs)
180
User's Manual
This is the default configuration to which each port comes configured. However,
provisioning is still required on the edge switch (ES) in order for this configuration to
work. Under this configuration the media server uses a loop VP as shown in the
following figure. The looped VP is setup on the edge switch connected to the media
server. When hairpinning connections are required, the media server automatically
assigns internal SVCs on the looped VPs. These SVCs are used to lop cells out of
the media server and back into the media server via the edge switch.
Figure 8-2: Looped Virtual Path between VoATM Media Server and Edge Switch
1 fiber port
AudioCodes
VoATM
Media
Server
ES
Outbound VP
Inbound VP
ES = Edge Switch
UNI loopback
Under this configuration the media server uses the edge switch to setup an SVC
connection from/to itself. The edge switch is required to support UNI loop (i.e. support
of SVCs originating and terminating to the same interface/port).
Version 4.8
181
January 2006
User's Manual
9. Mediant 3000 Management
Mediant 3000 Management

Two types of Mediant 3000 management are detailed in this section:
9.1
SNMP-Based Client Program - Refer to "Using SNMP" below
Web interface - Refer to ''Embedded Web Server'' on page 202
Using SNMP
Simple Network Management Protocol (SNMP) is a standards-based network control
protocol for managing elements in a network. The SNMP Manager (usually
implemented by a network Management System (NMS) or an Element Management
System (EMS)) connects to an SNMP Agent (embedded on a remote Network
Element (NE)) to perform network element Operation, Administration and
Maintenance (OAM).
Both the SNMP Manager and the NE refer to the same database to retrieve
information or configure parameters. This database is referred to as the Management
Information Base (MIB), and is a set of statistical and control values. Apart from the
standard MIBs documented in IETF RFCs, SNMP additionally enables the use of
proprietary MIBs, containing a non-standard information set (specific functionality
provided by the Network Element).
Directives, issued by the SNMP Manager to an SNMP Agent, consist of the identifiers
of SNMP variables (referred to as MIB object identifiers or MIB variables) along with
instructions to either get the value for that identifier, or set the identifier to a new value
(configuration). The SNMP Agent can also send unsolicited events towards the EMS,
called SNMP traps.
The definitions of MIB variables supported by a particular agent are incorporated in
descriptor files, written in Abstract Syntax Notation (ASN.1) format, made available to
EMS client programs so that they can become aware of MIB variables and their
usage.
The Mediant 3000 contains an embedded SNMP Agent supporting both general
network MIBs (such as the IP MIB), VoP-specific MIBs (such as RTP) and
AudioCodes' proprietary MIBs (AcBoard, acGateway, AcAlarm and other MIBs)
enabling a deeper probe into the inter-working of the Gateway. All supported MIB files
are supplied to Customers as part of the release.
9.1.1
SNMP Standards and Objects

Four types of SNMP messages are defined:
9.1.1.1
Version 4.8
SNMP Message Standard
Get - A request that returns the value of a named object.
Get-Next - A request that returns the next name (and value) of the "next" object
supported by a network device given a valid SNMP name.
Set - A request that sets a named object to a specific value.
Trap - A message generated asynchronously by network devices. It notifies the

183
January 2006
Mediant 3000
network manager of a problem apart from the polling of the device.
Each of these message types fulfills a particular requirement of network managers:
Get Request - Specific values can be fetched via the "get" request to determine
the performance and state of the device. Typically, many different values and
parameters can be determined via SNMP without the overhead associated with
logging into the device, or establishing a TCP connection with the device.
Get Next Request - Enables the SNMP standard network managers to "walk"
through all SNMP values of a device (via the "get-next" request) to determine all
names and values that a device supports.
Get-Bulk Extends the functionality of GETNEXT by allowing multiple values to

be returned for selected items in the request.
This is accomplished by beginning with the first SNMP object to be fetched,

fetching the next name with a "get-next", and repeating this operation.
Set Request - The SNMP standard provides a action method for a device (via the
"set" request) to accomplish activities such as disabling interfaces, disconnecting
users, clearing registers, etc. This provides a way of configuring and controlling
network devices via SNMP.
Trap Message - The SNMP standard furnishes a mechanism for a device to

"reach out" to a network manager on their own (via the trap" message) to notify
or alert the manager of a problem with the device. This typically requires each
device on the network to be configured to issue SNMP traps to one or more
network devices that are awaiting these traps.
The above message types are all encoded into messages referred to as "Protocol
Data Units" (PDUs) that are interchanged between SNMP devices.
9.1.1.2
SNMP MIB Objects

The SNMP MIB is arranged in a tree-structure, similar to a disk directory structure of
files. The top level SNMP branch begins with the ISO "internet" directory, which
contains four main branches:
The "mgmt" SNMP branch - Contains the standard SNMP objects usually
supported (at least in part) by all network devices.
The private" SNMP branch - Contains those "extended" SNMP objects defined
by network equipment vendors.
The "experimental" and "directory" SNMP branches - Also defined within the
"internet" root directory, are usually devoid of any meaningful data or objects.
The "tree" structure described above is an integral part of the SNMP standard, though
the most pertinent parts of the tree are the "leaf" objects of the tree that provide actual
management data regarding the device. Generally, SNMP leaf objects can be
partitioned into two similar but slightly different types that reflect the organization of the
tree structure:
User's Manual
Discrete MIB Objects - Contain one precise piece of management data. These
objects are often distinguished from "Table" items (below) by adding a .0" (dotzero) extension to their names. The operator must merely know the name of the
object and no other information.
Table MIB Objects - Contain multiple pieces of management data. These objects
are distinguished from "Discrete" items (above) by requiring a "." (dot) extension
to their names that uniquely distinguishes the particular value being referenced.
The "." (dot) extension is the "instance" number of an SNMP object. For
184
User's Manual

"Discrete" objects, this instance number is zero. For "Table" objects, this instance
number is the index into the SNMP table. SNMP tables are special types of
SNMP objects, which allow parallel arrays of information to be supported. Tables
are distinguished from scalar objects, such that tables can grow without bounds.
For example, SNMP defines the "ifDescr" object (as a standard SNMP object)
that indicates the text description of each interface supported by a particular
device. Since network devices can be configured with more than one interface,
this object can only be represented as an array.
By convention, SNMP objects are always grouped in an "Entry" directory, within an
object with a "Table" suffix. (The "ifDescr" object described above resides in the
"ifEntry" directory contained in the "ifTable" directory).
9.1.1.3
SNMP Extensibility Feature

One of the principal components of an SNMP manager is a MIB Compiler", which
allows new MIB objects to be added to the management system. When a MIB is
compiled into an SNMP manager, the manager is made "aware" of new objects that
are supported by agents on the network. The concept is similar to adding a new
schema to a database.
Typically, when a MIB is compiled into the system, the manager creates new folders
or directories that correspond to the objects. These folders or directories can typically
be viewed with a "MIB Browser", which is a traditional SNMP management tool
incorporated into virtually all network management systems.
The act of compiling the MIB allows the manager to know about the special objects
supported by the agent and access these objects as part of the standard object set.
9.1.2
Carrier-Grade Alarm System

The basic alarm system has been extended to a carrier-grade alarm system. A carriergrade alarm system provides a reliable alarm reporting mechanism that takes into
account element management system outages, network outages, and transport
mechanism such as SNMP over UDP.
A carrier-grade alarm system is characterized by the following:
The device allows an EMS to determine which alarms are currently active in the
device. That is, the device maintains an active alarm table.
The device allows an EMS to detect lost alarms and clear notifications.
[sequence number in trap, current sequence number MIB object]
The device allows an EMS to recover lost alarm raise and clear notifications
[maintains a log history]
The device sends a cold start trap to indicate that it is starting. This allows the
EMS to synchronize its view of the device's active alarms.
When the SNMP alarm traps are sent, the carrier-grade alarm system does not add or
delete alarm traps as part of the feature. This system provides the mechanism for
viewing of history and current active alarm information.
9.1.2.1
Active Alarm Table

The board maintains an active alarm table to allow an EMS to determine which alarms
are currently active in the device. Two views of the active alarm table are supported by
the agent:
Version 4.8
185
January 2006
Mediant 3000
acActiveAlarmTable in the enterprise AcAlarm
alarmActiveTable and alarmActiveVariableTable in the IETF standard AcAlarm

MIB (rooted in the MIB tree)
The acActiveAlarmTable is a simple, one-row per alarm table that is easy to view with
a MIB browser.
The Alarm MIB is currently a draft standard and therefore, has no OID assigned to it.
In the current software release, the MIB is rooted in the <ProcuctName> MIB subtree.
In a future release, after the MIB has been ratified and an OID assigned to it, it is to be
moved to the official OID.
9.1.2.2
Alarm History
The board maintains a history of alarms that have been raised and traps that have
been cleared to allow an EMS to recover any lost raise or clear traps. Two views of
the alarm history table are supported by the agent:
acAlarmHistoryTable in the enterprise AcAlarm
nlmLogTable and nlmLogVariableTable in the standard NOTIFICATION-LOGMIB
As with the acActiveAlarmTable, the acAlarmHistoryTable is a simple, one-row per

alarm table, that is easy to view with a MIB browser.
9.1.3
Cold Start Trap

Mediant 3000 technology supports a cold start trap to indicate that the unit is starting.
This allows the EMS to synchronize its view of the unit's active alarms. In fact, two
different traps are sent at start-up:
9.1.4
The standard coldStart trap - iso(1).org(3).dod(6).internet(1). snmpV2(6).

snmpModules(3). snmpMIB(1). snmpMIBObjects(1). snmpTraps(5). coldStart(1)
sent at system initialization.
The enterprise acBoardEvBoardStarted, which is generated at the end of system

initialization. This is more of an "application-level" cold start sent after all the
initializing process is over and all the modules are ready.
Performance Measurements
Performance Measurements are available for an element management system (EMS)
through an SNMP interface and can be polled at scheduled intervals by an external
poller or utility in the management server or other off board system.
The Mediant 3000 provides performance measurements in the form of two types:
1.
Gauges - Gauges represent the current state of activities on the media server.
Gauges unlike counters can decrease in value and like counters, can increase.
The value of a gauge is the current value or a snapshot of the current activity on
the media server at that moment.
2.
Counters - Counters always increase in value and are cumulative. Counters,

unlike gauges, never decrease in value unless the server is reset and then the
counters are zeroed.
The Mediant 3000 performance measurements are provided by several proprietary

MIBs (located under the "acPerformance" sub tree:
User's Manual
186
User's Manual
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).AudioCodes(5003).acPer
formance(10).
There are two formats of Performance Monitoring MIBs:
1. Older Format
Each MIB is made up of a list of single MIB objects, each relating to a separate
attribute within a gauge or counter. All counters and gauges give the current time
value only.
acPerfMediaGateway - a generic-type of PM MIB that covers:
Control protocol
RTP stream
System packets statistics
acPerfMediaServices - Media services devices specific performance MIB.
2. New Format - includes new MIBs.

They all have an identical structure, which includes two major subtrees:
Configuration sub tree - allows configuration of general attributes of the

MIB and specific attributes of the monitored objects.
Data sub tree
The monitoring results are presented in tables. There are one or two indices in
each table. If there are two - the first is a sub-set in the table (Example: trunk
number) and the second (or the single where there is only one) index represents
the interval number (present - 0, previous - 1 and the one before - 2).
The MIBs are:
acPMMedia - for media (voice) related monitoring such as RTP and DSP.
acPMControl - for Control Protocol related monitoring such as connections,

commands.
acPMPSTN - for PSTN related monitoring such as channel use, trunk

utilization.
acPMSystem - for general (system related) monitoring.
The log trap, acPerformanceMonitoringThresholdCrossing (non-alarm) is sent out

every time the threshold of a Performance Monitored object is crossed. The severity
field is 'indeterminate' when the crossing is above the threshold and 'cleared' when it
goes back under the threshold. The 'source' varbind in the trap indicates the object for
which the threshold is being crossed.
9.1.4.1
TrunkPack-VoP Series Supported MIBs

The TrunkPack-VoP Series contains an embedded SNMP Agent supporting the
following MIBs:
Version 4.8
The Standard MIB (MIB-2) - The various SNMP values in the standard MIB are
defined in RFC 1213. The standard MIB includes various objects to measure and
monitor IP activity, TCP activity, UDP activity, IP routes, TCP connections,
interfaces, and general system description.
187
January 2006
Mediant 3000
Note: In the ipCidrRouteIfIndex the IF MIB indices are not referenced. Instead, the
index used is related to one of the IP interfaces in the board - 1 - OAM, 2 Media, 3 - Control. (When there is only one interface then the only index is
OAM - 1. Refer to' Appendix - Getting Started with VLANs and IP
Separation' on page 553
RTP MIB - The RTP MIB is supported according to RFC 2959. It contains objects
relevant to the RTP streams generated and terminated by the board and to the
RTCP information related to these streams.
Note: The inverse tables are NOT supported.
Notification Log MIB - This standard MIB (RFC 3014 iso.org.dod.internet.mgmt.mib-2) is supported as part of AudioCodes'
implementation of Carrier Grade Alarms.
Alarm MIB - This IETF MIB (RFC 3877) is supported as part of the
implementation of Carrier Grade Alarms. This MIB is a new standard and
therefore is under the audioCodes.acExperimental branch.
SNMP Target MIB - This MIB (RFC 2273) allows for configuration of trap
destinations and trusted managers.
SNMP MIB This MIB (RFC 3418) allows support of the coldStart and
authenticationFailure traps.
SNMP Framework MIB (RFC 3411).
SNMP Usm MIB this MIB (RFC 3414) implements the user-based Security
Model.
SNMP Vacm MIB This MIB (RFC 3415) implements the view-based Access
Control Model.
SNMP Community MIB This MIB (RFC 3584). implements community string
management.
SONET MIB This MIB (RFC 3592) implements the following partial support:
In the SonetMediumTable, the following objects are supported:
SonetMediumType
SonetMediumLineCoding
SonetMediumLineType
SonetMediumCircuitIdentifier
In the SonetSectionCurrentTable, the SonetSectionCurrentStatus object

only.
In the SonetLineCurrentTable, the sonetLineCurrentStatus object only.
In addition to the standard MIBs, the complete product series contains proprietary
MIBs:
User's Manual
AC-TYPES MIB lists the known types defined by the complete product series.
This is referred to by the sysObjectID object in the MIB-II.
188
User's Manual
AcBoard MIB - This proprietary MIB is deprecated and used for the traps defined
in it only
(...audioCodes(5003).acProducts(9).acBoardMibs(10).acBoard(1).acTrap(21))
All configuration and statuses should be done via other MIBs (see bellow).
acControl MIB
acMedia MIB
acPSTN MIB
acSystem MIB - Includes IP separation support (a new subtree, acMultipleIp,

was added to the acSystem MIB). This allows SNMP users to configure the
device to work with more then one IP interface,, aswell as configure these
interfaces. The configuration results are visible in the ipForward MIB.
acSS7 MIB
Other proprietary MIBs are:
AcAlarm - This is a proprietary carrier-grade alarm MIB. It is a simpler

implementation of the notificationLogMIB and the IETF suggested alarmMIB (both
also supported in all AudioCodes boards).
The acAlarm MIB has the following groups:
ActiveAlarm - straight forward (single indexed) table listing all currently

active Alarms together with their bindings (the Alarm bindings are defined in
acAlarm. acAlarmVarbinds and also in acBoard.acTrap.
acBoardTrapDefinitions. oid_1_3_6_1_4_1_5003_9_10_1_21_2_0).
acAlarmHistory - straight forward (single indexed) table listing all recently

raised Alarms together with their bindings (the Alarm bindings are defined in
acAlarm. acAlarmVarbinds and also in acBoard.acTrap.
acBoardTrapDefinitions. oid_1_3_6_1_4_1_5003_9_10_1_21_2_0).
The
table
size
can
be
altered
via
notificationLogMIB.notificationLogMIBObjects.nlmConfig.nlmConfigGlobalEntryLimit or
notificationLogMIB.notificationLogMIBObjects.nlmConfig.nlmConfigLogTable.nlmConfi
gLogEntry.nlmConfigLogEntryLimit.
The table size can be any value between 50 and 1000 and the default is 500.
ATM MIB
The major components of this Enterprise MIB are described as follows:
Version 4.8
acAtmConfiguration
atmGeneralParams - This component enables the configuration of the

default application type (AAL1, AAL2 (based upon I.366.2), or AAL2 (for
UMTS) as well as the transmission mode (either SDH or Sonet).
atmPort - While there currently is only one ATM port supported, this list
component enables the definition of the ATM port characteristics.
Configurable component includes the port administrative state and the
administrative address (only for AAL2 PVC scenarios). Also, there are read
only items that include the operational state of the ATM port, the alarm
status, the port address mode (indicates the status/mode of the operational
address: No Address, manually input, or ILMI), and the port operational
address (which, if ILMI is enabled, is the registered address that is used).
atmRemoteGateway - This list component is used for AAL2 PVC

189
January 2006
Mediant 3000
provisioning for Media Server and UMTS and enables the description of the
remote gateway. For provisioning, this component includes the remote
gateway name, its ATM (NSAP) address, and, for wireless UMTS, the
ALCAP instance number.
aal2PVC - This list object enables provisioning of PVCs into the system.
atmPortLoopbackConfig - This list component enables configuring the

loopback interface. For provisioning, this component includes the peak and
sustained cell rate, the ATM port number, the type of loopback (a looped
virtual path, a UNI, or none), the inbound and outbound virtual path identifier
(if a looped virtual path exists), the first and last virtual channel identifier (if a
looped virtual path exists), and if the loopback is a PV loop, the service
category, peak and sustained cell rate, and maximum burst size.
atmSvcProfile - This list component enables configuring the SVC traffic

profiles in the system. Refer to the SVC Traffic Profile table in ''SVC Access
(ATL AAL2)'' on page 179 for details.
acAtmStatus
atmSvcConnection - This list component determins the current status of the

SVCs in the system. This component includes the AAL type (either AAL1 or
AAL2), direction (incoming or outgoing), the VCCI, the EECID (for AAL1),
the number of CIDs in use (only AAL2), as well as the virtual path and
channel identifiers.
Note 1: The following are special notes pertaining to MIBs:
A detailed explanation of each parameter can be viewed in the

MIB Description field.
Not all groups in the MIB are implemented. Refer to version

release notes.
MIB Objects which are marked as 'obsolete' are not

implemented.
When a parameter is SET to a new value via SNMP, the change

may affect board functionality immediately or may require that
the board be soft reset for the change to take effect. This
depends on the parameter type.
Note 2: The current (updated) board configuration parameters are programmed into
the board provided that the user does not load an ini file to the board after
reset. Loading an ini file after reset overrides the updated parameters.
Additional MIBs are to be supported in future releases.
Traps
Note: As of this version all traps are sent out from the SNMP port (default 161).
This is part of the NAT traversal solution.
Full proprietary trap definitions and trap Varbinds are found in AcBoard MIB and
AcAlarm MIB. For a detailed inventory of traps, refer to the Appendix, ''SNMP
Alarm Traps'' on page 571.
User's Manual
190
User's Manual
The following proprietary traps are supported in Mediant 3000:
Version 4.8
acBoardFatalError - Sent whenever a fatal board error occurs.
acBoardConfigurationError - Sent when a board's settings are illegal - the

trap contains a message stating/detailing/explaining the illegality of the
setting.
acBoardTemperatureAlarm - Sent when a board exceeds its temperature

limits.
acBoardEvResettingBoard - Sent after a board is reset.
acBoardEvBoardstarted - Sent after a board is successfully restored and

initialized following reset.
acFeatureKeyError - Development pending. Intended to relay Feature Key

errors etc. (To be supported in the next applicable release)
acgwAdminStateChange - Sent when Graceful Shutdown commences and

ends.
acBoardEthernetLinkAlarm - Ethernet Link or links are down.
acActiveAlarmTableOverflow - An active alarm could not be placed in the

active alarm table because the table is full.
acAtmPortAlarm - ATM Port Alarm.
acAudioProvisioningAlarm - Raised if the Mediant 3000 is unable to

provision its audio.
acOperationalStateChange - Raised if the operational state of the node

goes to disabled. Cleared when the operational state of the node goes to
enabled.
acKeepAlive part of the NAT traversal mechanism. If the STUN

application in the Mediant 3000 detects a NAT then this trap is sent out on a
regular time laps - 9/10 of the acSysSTUNBindingLifeTime object. The
AdditionalInfo1 varbind has the MAC address of the Mediant 3000.
acNATTraversalAlarm - When the NAT is placed in front a Mediant 3000, it

is identified as a symmetric NAT - this alarm is raised. It is cleared when a
non-symmetric NAT or no NAT replace the symmetric one.
acEnhancedBITStatus - This trap is used to for the status of the BIT (Built
In Test). The information in the trap contains board hardware elements being
tested and their status. The information is presented in the additional info
fields.
acPerformanceMonitoringThresholdCrossing - This log trap is sent out

for every time the threshold of a Performance Monitored object is crossed.
The severity field is 'indeterminate' when the crossing is above the threshold
and 'cleared' when it goes back under the threshold. The 'source' varbind in
the trap indicates the object for which the threshold is being crossed.
acSS7LinkStateChangeAlarm - This alarm is raised if the operational state

of the SS7 link becomes BUSY. The alarm is cleared when the operational
state of the link becomes -SERVICE or OFFLINE.
acSS7LinkInhibitStateChangeAlarm - This alarm is raised if the SS7 link

becomes inhibited (local or remote). The alarm is cleared when the link
becomes uninhibited - local AND remote. Note that this alarm is raised for
any change in the remote or local inhibition status.
191
January 2006
Mediant 3000
acSS7LinkBlockStateChangeAlarm - This alarm is raised if the SS7 link

becomes blocked (local or remote). The alarm is cleared when the link
becomes unblocked - local AND remote. Note that this alarm is raised for
any change in the remote or local blocking status.
acSS7LinkCongestionStateChangeAlarm - This alarm is raised if the SS7

link becomes congested (local or remote). The alarm is cleared when the link
becomes uncongested - local AND remote. Note that this alarm is raised for
any change in the remote or local congestion status.
acSS7LinkSetStateChangeAlarm - This alarm is raised if the operational

state of the SS7 linkset becomes BUSY. The alarm is cleared when the
operational state of the linkset becomes -SERVICE or OFFLINE.
acSS7RouteSetStateChangeAlarm - This alarm is raised if the operational

state of the SS7 routeset becomes BUSY. The alarm is cleared when the
operational state of the routeset becomes -SERVICE or OFFLINE.
acSS7SNSetStateChangeAlarm - This alarm is raised if the operational

state of the SS7 node becomes BUSY. The alarm is cleared when the
operational state of the node becomes IN-SERVICE or OFFLINE..
acSS7RedundancyAlarm - Raised when the SS7 redundancy degregated.
acHTTPDownloadResult log trap for the success or failures of the HTTP

Download action.
acFanTrayAlarm fault in the fan tray or fan tray missing.
acPowerSupplyAlarm - fault in one of the power supply modules or PS

module missing.
acPEMAlarm - fault in the one of the PEM modules or PEM module missing.
acSAMissingAlarm SA module missing or non operational.
acUserInputAlarm the alarm is raised when the input dry contact is short
circuited and cleared when the circuit is reopened.
acHASystemFaultAlarm for High Availability (HA) system only - the HA

system is faulty and therefore there is no HA.
acHASystemConfigMismatchAlarm for High Availability (HA) system

only - configuration to the modules in the HA system us uneven causing
instability.
acHASystemSwitchOverAlarm for High Availability (HA) system only - a

switch over from the active to the redundant module has occurred.
acDChannelStatus Non alarm trap sent at the establishment, reestablishment or release of LAPD link with its peer connection occurs.The
trap will be sent out with one of the following in the textual description:
D-channel synchronized
D-channel not-synchronized
acSonetSectionLOFAlarm - SONET section Loss of Frame alarm
acSonetSectionLOSAlarm - SONET section Loss of Signal alarm.
acSonetLineAISAlarm - SONET Line AIS alarm.
acSonetLineRDIAlarm - SONET Line RDI alarm.
In addition to the listed traps the Board also supports the following standard traps:
User's Manual
authenticationFailure
192
User's Manual
9.1.5
coldStart
dsx1LineStatusChange
dsx3LineStatusChange implementation pending.
SNMP Interface Details

This section describes details of the SNMP interface needed when developing an
Element Management System (EMS) for any of the TrunkPack-VoP Series products,
or to manage a device with a MIB browser.
SNMP can be encoded over IPSec. For more details, refer to the Appendix,' Security'
on page 451.
For ini file encoding, refer to the Appendix 'Utilities' on page 495.
9.1.5.1
SNMP Community Names

By default, the board uses a single, read-only community string of "public" and a
single read-write community string of "private".
Up to 5 read-only community strings and up to 5 read-write community strings, and a
single trap community string can be configured.
9.1.5.1.1
Configuring Community Strings via the ini File

SNMPREADONLYCOMMUNITYSTRING_<x> = '#######'
SNMPREADWRITECOMMUNITYSTRING_<x> = '#######'
Where <x> is a number between 0 and 4, inclusive. Note that the '#' character
represents any alphanumeric character. The maximum length of the string is 20
characters.
9.1.5.1.2
Configuring Community Strings via SNMP

To configure community strings, the EM must use the standard snmpCommunityMIB
and the snmpVacmMIB. To configure the trap community string, the EM must also use
the snmpTargetMIB.
To add a read-only community string, v2user, take these 2 steps:

1.
Add a new row to the snmpCommunityTable with CommunityName v2user.
2.
Add a row to the vacmSecurityToGroupTable for SecurityName v2user,

GroupName ReadGroup and SecurityModel snmpv2c.
To delete the read-only community string, v2user, take these 3

steps:
Version 4.8
1.
If v2user is being used as the trap community string, follow the procedure for
changing the trap community string. (See below.)
2.
Delete the snmpCommunityTable row with CommunityName v2user.
3.
Delete the vacmSecurityToGroupTable row for SecurityName v2user,

GroupName ReadGroup and SecurityModel snmpv2c.
193
January 2006
Mediant 3000
To add a read-write community string, v2admin, take these 2

steps:
1.
Add a new row to the snmpCommunityTable with CommunityName v2admin.
2.
Add a row to the vacmSecurityToGroupTable for SecurityName v2admin,

GroupName ReadWriteGroup and SecurityModel snmpv2c.
To delete the read-write community string, v2admin, take these 2

steps:
1.
If v2admin is being used as the trap community string, follow the procedure for
changing the trap community string. (See below.)
2.
Delete the srCommunityTable row with a CommunityName of v2admin and

GroupName of ReadWriteGroup.
To change the only read-write community string from v2admin to

v2mgr, take these 4 steps:
1.
Follow the procedure above to add a read-write community string to a row for
v2mgr.
2.
Set up the EM such that subsequent set requests use the new community string,
v2mgr.
3.
If v2admin is being used as the trap community string, follow the procedure to
change the trap community string. (See below.)
4.
Follow the procedure above to delete a read-write community name in the row for
v2admin.
To change the trap community string, take these 3 steps:

The following procedure assumes that a row already exists in the srCommunityTable
for the new trap community string. The trap community string can be part of the
TrapGroup, ReadGroup or ReadWriteGroup. If the trap community string is used
solely for sending traps (recommended), then it should be made part of the
TrapGroup.
1.
Add a row to the vacmSecurityToGroupTable with these values:

SecurityModel=2, SecurityName=the new trap community string,
GroupName=TrapGroup, ReadGroup or ReadWriteGroup. The SecurityModel
and SecurityName objects are row indices.
Note: You must add GroupName and RowStatus on the same set.
User's Manual
2.
Modify the SecurityName field in the appropriate row of the

snmpTargetParamsTable.
3.
Remove the row from the vacmSecurityToGroupTable with SecurityName=the

old trap community string.
194
User's Manual
9.1.5.2
Trusted Managers
By default, the agent accepts get and set requests from any IP address, as long as the
correct community string is used in the request. Security can be enhanced via the use
of Trusted Managers. A Trusted Manager is an IP address from which the SNMP
agent accepts and process get and set requests. An EM can be used to configure up
to 5 Trusted Managers.
Note: If Trusted Managers are defined, then all community strings works from all
Trusted Managers. That is, there is no way to associate a community string
with particular trusted managers.
9.1.5.2.1
Configuring Trusted Managers via ini File

To set the Trusted Mangers table from start up, write the following in the ini file:
SNMPTRUSTEDMGR_X = D.D.D.D
Where X is any integer between 0 and 4 (0 sets the first table entry, 1 sets the second
and so on), and D is an integer between 0 and 255.
9.1.5.2.2
Configuring Trusted Managers via SNMP

To configure Trusted Managers, the EM must use the SNMP-COMMUNITY-MIB and
snmpCommunityMIB and the snmpTargetMIB.
To add the first Trusted Manager, take these 3 steps:

This procedure assumes that there is at least one configured read-write community.
There are currently no Trusted Managers. The TransportTag for columns for all
snmpCommunityTable rows are currently empty.
1.
Add a row to the snmpTargetAddrTable with these values: Name=mgr0,

TagList=MGR, Params=v2cparams.
2.
Add a row to the snmpTargetAddrExtTable table with these values: Name=mgr0,

snmpTargetAddrTMask=255.255.255.255:0. The agent does not allow creation of
a row in this table unless a corresponding row exists in the
snmpTargetAddrTable.
3.
Set the value of the TransportTag field on each non-TrapGroup row in the
snmpCommunityTable to MGR.
To add a subsequent Trusted Manager, take these 2 steps:

There are currently one or more Trusted Managers. The TransportTag for columns for
all rows in the snmpCommunityTable are currently set to MGR. This procedure must
be done from one of the existing Trusted Managers.
Version 4.8
1.
Add a row to the snmpTargetAddrTable with these values: Name=mgrN,

TagList=MGR, Params=v2cparams, where N is an unused number between 0
and 4.
2.
Add a row to the snmpTargetAddrExtTable table with these values: Name=mgrN,

snmpTargetAddrTMask=255.255.255.255:0.
195
January 2006
Mediant 3000
An alternative to the above procedure is to set the snmpTargetAddrTMask column

while you are creating other rows in the table.
To delete a Trusted Manager (not the final one), take this step:
There are currently two or more Trusted Managers. The taglist for columns for all rows
in the snmpCommunityTable are currently set to MGR. This procedure must be done
from one of the existing trusted managers, but not the one that is being deleted.
Remove the appropriate row from the snmpTargetAddrTable.
The change takes affect immediately. The deleted trusted manager cannot access
the board. The agent automatically removes the row in the snmpTargetAddrExtTable.
To delete the final Trusted Manager, take these 2 steps:

There is currently only one Trusted Manager. The taglist for columns for all rows in the
snmpCommunityTable are currently set to MGR. This procedure must be done from
thefinal Trusted Manager.
1.
Set the value of the TransportTag field on each row in the snmpCommunityTable
to the empty string.
2.
The change takes affect immediately. All managers can now access the board. The
agent automatically removes the row in the snmpTargetAddrExtTable.
9.1.5.3
SNMP Ports
The SNMP Request Port is 161 and Trap Port is 162
These ports can be changed by setting parameters in the board ini file. The parameter
name is:
SNMPPort = <port_number>
Valid UDP port number; default = 161
This parameter specifies the port number for SNMP requests and responses.
Usually it should not be specified. Use the default.
9.1.5.4
Multiple SNMP Trap Destinations

An agent can send traps to up to five managers. For each manager the user needs to
set the manager IP and trap receiving port along with enabling the sending to that
manager.
9.1.5.4.1
Configuring Trap Manager via Host Name

A trap manager can be set using the manager's host name. This is currently supported
via ini file only, using the parameter name, SNMPTrapManagerHostName.
When this parameter value is set for this trap, the board at start up tries to resolve the
host name. Once the name is resolved (IP is found) the bottom entry in the trap
manager's table (and also in the snmpTargetAddrTable in the snmpTargetMIB) is
updated with the IP.
User's Manual
196
User's Manual
The port is 162 unless specified otherwise. The row is marked as 'used' and sending
is 'enabled').
When using 'host name' resolution, any changes made by the user to this row in either
MIBs are overwritten by the board when a resolving is redone (once an hour).
Note: Some traps may be lost until the name resolving is complete.
9.1.5.4.2
Configuring via the ini File

In the TP-6310 board ini file, parameters below can be set to enable or disable the
sending of SNMP traps. Multiple trap destinations can be supported on the media
server by setting multiple trap destinations in the ini file.
SNMPMANAGERTRAPSENDINGENABLE_<x> = 0 or 1 indicates if traps are to be
sent to the specified SNMP trap manager. A value of 1 means that it is enabled, while
a value of 0 means disabled.
Where <x> = a number 0, 1, 2 and is the array element index. Currently up to 5
SNMP trap managers can be supported.
Below is an example of entries in the board ini file regarding SNMP. The media server
can be configured to send to multiple trap destinations. The lines in the file below are
commented out with the ; at the beginning of the line. All of the lines below are
commented out since the first line character is a semi-colon.
; SNMP trap destinations
; The board maintains a table of trap destinations containing 5
; rows. The rows are numbered 0..4. Each block of 4 items below
; applies to a row in the table.
;
; To configure one of the rows, uncomment all 4 lines in that
; block. Supply an IP address and if necessary, change the port
; number.
;
; To delete a trap destination, set ISUSED to 0.
;
;
;SNMPMANAGERTABLEIP_0=
;SNMPMANAGERTRAPPORT_0=162
;SNMPMANAGERISUSED_0=1
;SNMPMANAGERTRAPSENDINGENABLE_0=1
;
;
;
;
Version 4.8
197
January 2006
Mediant 3000
The trap manager host name is configured via SNMPTrapManagerHostName. For

example:
;SNMPTrapManagerHostName = 'myMananger.corp.MyCompany.com'
Note: The same information that is configurable in the ini file can also be
configured via the acBoardMIB.
9.1.5.4.3
Configuring via SNMP

There are two MIB interfaces for the trap managers. The first is via the acBoard MIB
that has become obsolete and is to be removed from the code in the next applicable
release. The second is via the standard snmpTargetMIB.
1.
Using the acBoard MIB:

The following parameters, which are defined in the snmpManagersTable:
a.
snmpTrapManagerSending
b.
snmpManagerIsUsed
c.
snmpManagerTrapPort
d.
snmpManagerIP
When snmpManagerIsUsed is set to zero (not used) the other three
parameters are set to zero. (The intent is to have them set to the default
value, which means TrapPort is to be set to 162. This is to be revised in a
later release.)
snmpManagerIsUsed
Default = Disable(0)
The allowed values are 0 (disable or no) and 1 (enable or yes).
snmpManagerIp Default = 0.0.0.0

This is known as SNMPManagerTableIP in the ini file and is the IP
address of the manager.
snmpManagerTrapPort
Default = 162
The valid port range for this is 100-4000.
snmpManagerTrapSendingEnable
Default = Enable(1)
The allowed values are 0 (disable) and 1 (enable).

Note 1: Each of these MIB objects is independent and can be set regardless of the
state of snmpManagerIsUsed.
Note 2: If the IsUsed parameter is set to 1, then the IP address for that row should
be supplied in the same SNMP PDU.
2.
User's Manual
Using the SNMPTargetMIB:

198
User's Manual
To add a trap destination, take this step:
Add a row to the snmpTargetAddrTable with these values: Name=trapN,

TagList=AC_TRAP, Params=v2cparams, where N is an unused number between
0 and 4
All changes to the trap destination configuration take effect immediately.
To delete a trap destination, take this step:
To modify a trap destination, take this step:

You can change the IP address and or port number for an existing trap destination.
The same effect can be achieved by removing a row and adding a new row.
Modify the IP address and/or port number for the appropriate row in the
snmpTargetAddrTable.
To disable a trap destination, take this step:
Change TagList on the appropriate row in the snmpTargetAddrTable to the empty

string.
To enable a trap destination, take this step:
9.1.5.4.4
Change TagList on the appropriate row in the snmpTargetAddrTable to

"AC_TRAP".
SNMP Manager Backward Compatibility

With support of the Multi Manager Trapping feature, there is also a need to support
the older acSNMPManagerIP MIB object, which is synchronized with the first index in
the snmpManagers MIB table. This is translated in two new features:
9.1.6
SET/GET to either of the two; is for now identical.

i.e. OID 1.3.6.1.4.1.5003.9.10.1.1.2.7 is identical
to OID 1.3.6.1.4.1.5003.9.10.1.1.2.21.1.1.3 as far as the SET/GET are
concerned.
When setting ANY IP to the acSNMPManagerIP (this is the older parameter, not
the table parameter), two more parameters are SET to ENABLE.
snmpManagerIsUsed.0 and snmpManagerTrapSendingEnable.0 are both set to
1.
SNMP NAT Traversal

A NAT placed between a <product Name> and the element manager calls for
traversal solutions:
Version 4.8
Trap source port all traps are sent out from the SNMP port (default 161). A
manager receiving these traps can use the binding information (in the UDP layer)
to traverse the NAT back to the device.
The trap destination address (port and IP) are as configured in the
snmpTargetMIB.
199
January 2006
Mediant 3000
acKeepAliveTrap this trap is designed to be a constant life signal from the

device to the manager allowing the manager NAT traversal at all times. The
acBoardTrapGlobalsAdditionalInfo1 varbind has the devices serial number.
The destination port - the manager port for this trap - can be set to be different
than the port to which all other traps are sent. To do this, use the
acSysSNMPKeepAliveTrapPort object in the acSystem MIB or the
KeepAliveTrapPort ini file parameter.
The Trap is instigated in three ways:
Via an ini file parameter - 'SendKeepAliveTrap = 1'. This ensures that the
trap is continuously sent. The frequency is set via the 9/10 of the
NATBINDINGDEFAULTTIMEOUT (or MIB object acSysSTUNBindingLifeTime) parameter.
After the STUN client has discovered a NAT (any NAT).
If the STUN client can not contact a STUN server.
Note: The two latter options require the STUN client be enabled (ini file parameter
EnableSTUN).
Also, once the acKeepAlive trap is instigated it does not stop.
9.1.7
The manager can see the NAT type in the MIB:

audioCodes(5003).acProducts(9).acBoardMibs(10).acSystem(10).acSystemStatu
s(2).acSysNetwork(6).acSysNAT(2).acSysNATType(1)
The manger also has access to the STUN client configuration:

audioCodes(5003).acProducts(9).acBoardMibs(10).acSystem(10).acSystemConfi
guration(1).acSysNetworkConfig(3).acSysNATTraversal(6).acSysSTUN(21)
acNATTraversalAlarm - When the NAT is placed in front a device is identified as

a symmetric NAT - this alarm is raised. It is cleared when a non-symmetric NAT
or no NAT replace the symmetric one.
Systems
For the management of a system (a chassis with more then one type of module
running) the acSystem/acSystemChassis subtree in the acSystem MIB should be
used:
User's Manual
The first few objects are scalars that are read-only objects for the dry-contacts
state.
acSysModuleTable A table containing mostly status information that describes

the board modules in the system. IN addition, the table can be used to reset an
entire system, reset a redundant module or perform switchover when the system
is HA.
acSysFanTrayTable A status only table with the fan trays state. There are
objects in the table indicates the specific state of the individual fans with in the fan
tray.
acSysPowerSupplyTable A status only table with the states of the two power
supplies.
acSysPEMTable - A status only table with the states of the two PEMs (Power
Entry Modules).
200
User's Manual
The above tables are complemented by the following alarm traps (as defined in the
acBoard MIB. For more detailes, refer to the Appendix, 'SNMP Alarm Traps' on page
571):
9.1.8
acFanTrayAlarm fault in the fan tray or fan tray missing.
acPowerSupplyAlarm - fault in one of the power supply modules or PS module

missing.
acPEMAlarm - fault in the one of the PEM modules or PEM module missing.
acSAMissingAlarm SA module missing or non operational.
acUserInputAlarm the alarm is raised when the input dry contact is short
circuited and cleared when the circuit is reopened.
High Availability Systems

For the management of the HA systems use the acSysChassis MIB subtree (as in the
above section). The acSysModuleTable gives the HA state of the system. This
includes defining which modules are active and which are in standby mode
(redundant). The table also enables to read some of the statuses of the redundant
modules (such as SW version, HW version, temperature, license key list, etc).
Resetting the system, resetting the redundant module and performing switchover are
also done via this table.
Complementing the above are the following alarm traps (as defined in the acBoard
MIB and further detailed in the appendix):
acHASystemFaultAlarm the High Availability system is faulty and therefore

there is no HA.
acHASystemConfigMismatchAlarm configuration to the modules in the HA

system us uneven causing instability.
acHASystemSwitchOverAlarm a switch over from the active to the redundant

module has occurred.
9.1.9
Administrative State Control
9.1.9.1
Node Maintenance
Node maintenance for the Mediant 3000 is provided via an SNMP interface. The
acBoardMIB provides two parameters for graceful and forced shutdowns of the
Mediant 3000. (Refer to the note in "Graceful Shutdown" below.) These parameters
are in the acBoardMIB as acgwAdminState and acgwAdminStateLockControl.
The acgwAdminState is used either to request (set) a shutdown (0), undo shutdown
(2), or to view (get) the gateway condition (0 = locked, 1 = shutting down, 2 =
unlocked).
The acgwAdminStateLockControl is used to set a time limit for the shutdown (in
seconds) where 0 means shutdown immediately (forced), -1 means no time limit
(graceful) and x where x>0 indicates a time limit in seconds (timed limit is considered
a graceful shutdown).
The acgwAdminStateLockControl should be set first followed by the acgwAdminState.
Version 4.8
201
January 2006
Mediant 3000
9.1.9.2
Graceful Shutdown
acgwAdminState is a read-write MIB object. When a get request is sent for this object,
the agent returns the current board administrative state.
Note: Graceful shutdown is currently supported in MEGACO (H.248) only.
The possible values received on a get request are:
locked(0) - The board is locked
shuttingDown(1) - The board is in the process of performing a graceful lock
unlocked(2) - The board is unlocked
On a set request, the manager supplies the desired administrative state, either
locked(0) or unlocked(2).
When the board changes to either shuttingDown or locked state, an
adminStateChange alarm is raised. When the board changes to an unlocked state, the
adminStateChange alarm is cleared.
Before setting acgwAdminState to perform a lock, acgwAdminStateLockControl
should be set first to control the type of lock that is performed. The possible values
are:
9.2
1 = Perform a graceful lock. Calls are allowed to complete. No new calls are
allowed to be originated on this device.
0 = Perform a force lock. Calls are immediately terminated.
Any number greater than 0 - Time in seconds before the graceful lock turns into a
force lock.
Embedded Web Server

The Mediant 3000 boards and modules contain an Embedded Web Server to be used
for device configuration and for run-time monitoring. The Embedded Web Server
enables users equipped with any standard Web-browsing application such as
Microsoft Internet Explorer (Ver. 5.0 and higher) or Netscape Navigator (Ver.
7.2 and higher) to:
9.2.1
Provision devices (refer to ''Advanced Configuration Screen'' on page 276)
Verify configuration changes in the Status screens (refer to ''Status and

Diagnostic Menu'' on page 260)
Load the ini file (refer to ''Software Upgrade Wizard'' on page 266)
Embedded Web Server Protection & Security Mechanisms

Access to the Embedded Web Server is controlled by the following protection and
security mechanisms:
User's Manual
Multi Access Level Username and Password - Refer to "Username and

Password" below
202
User's Manual
9.2.1.1
Limiting the Web Server to Read-Only Mode - Refer to "Limiting the Web
Server GUI to Read-Only Mode" below
Disabling the Web Server - Refer to ''Disabling the Web Server GUI'' on page
205
Encrypted HTTP transport (HTTPS - SSL) - Refer to ''Encrypted HTTP

transport (HTTPS - SSL)'' on page 205
Limiting Web Access to a Predefined List of Client IP Addresses - Refer to'

'Limiting Web Access to a Predefined List of Client IP Addresses'' on page 205
Managing Web Access Using a RADIUS Server - Refer to ''Managing Web

Server Access Using a RADIUS Server'' on page 205
User Accounts
To prevent unauthorized access to the Embedded Web Server, two user accounts are
available, a primary and secondary. Each account is composed of three attributes:
username, password and access level. The username and password enable access to
the Embedded Web Server itself; the access level determines the extent of the access
(i.e., availability of screens and read / write privileges). Note that additional accounts
can be defined using a RADIUS server (refer to 'RADIUS Support' on page 464).
The table below lists the available access levels and their privileges.
Table 9-1: Available Access Levels and their Privileges

Access Level
Numeric
Representation*
Privileges
Security
Administrator
200
Read / write privileges for all screens
Administrator
100
Read-only privilege for security-related screens

and read / write privileges for the others
User Monitor
50
No access to security-related and file-loading

screens and read-only access to the others
No Access
No access to any screen
*The numeric representation of the access level is used only to define accounts in
a RADIUS server (the access level ranges from 0 to 255).
The access level mechanism operation is as follows (for both Web and RADIUS
accounts):
Each Web screen features two (hard-coded) minimum access levels, read and write.
The read access level determines whether the screen can be viewed. The write
access level determines whether the information in the screen can be modified.
When a user tries to access a specific Web screen, his access level is compared with
the access levels of the screen:
Version 4.8
If the access level of the user is less than the screens read access level, the
screen cannot be viewed.
If the access level of the user is equal or greater than the screens read access
level but less than the write access level, the screen is read only.
203
January 2006
Mediant 3000
If the access level of the user is equal to or greater than the screens write access
level, the screen can be modified.
The default attributes for the two accounts are shown in the table below.:
Table 9-2: Access Default Attributes

Account / Attributes
Username
Password
Access Level
Primary Account
Admin
Admin
Security Administrator*
Secondary Account
User
User
User_Monitor
*The access level of the primary account cannot be changed; all other accountattributes can be modified.
The first time a browser request is made, users are requested to provide their
accounts username and password to obtain access. If the Embedded Web Server is
left idle for more than five minutes, the session expires and the user is required to reenter his username and password
To access the Embedded Web Server with a different account, click the Log Off button
and re-access with a new username and password.
For details on changing the account attributes, refer to refer to ''Web User Accounts''
on page 245. Note that the password and username can be a maximum of 19 casesensitive characters.
To reset the username and password of both accounts to their defaults, set the
parameter ResetWebPassword in the ini file, to 1.
9.2.2
Limiting the Embedded Web Server to Read-Only Mode

Initially, the Embedded Web Server displays the default parameters that are preinstalled in the board. These parameters can be modified using the Embedded Web
Server, either by modifying parameters on the various pages or by loading a text
configuration file - an ini file to the Mediant 3000.
Users can limit the Web Server to read-only mode by changing the default of ini file
parameter DisableWebConfig. The read-only mode feature can be used as a security
measure. This security level provides protection against unauthorized access (such as
Internet hacker attacks), particularly important to users without a firewall.
9.2.2.1
Limiting the Embedded Web Server to Read-Only Mode

Users can limit the Web Server to read-only mode by changing the default of ini file
parameter DisableWebConfig. Use the read-only mode feature as a security measure.
This security level provides protection against unauthorized access (such as Internet
hacker attacks), particularly important to users without a firewall.
To limit the Web Server to read-only mode:
User's Manual
Set the ini file parameter DisableWebConfig to 1 (Default = 0, i.e. read-write

mode) and send the modified ini file to the device. All Web pages are presented
in read-only mode. The ability to modify configuration data is disabled. In addition,
users do NOT have access to any file loading page, to the "Change Password"
204
User's Manual

page, to the "SaveConfiguration", or to the "Reset" page.
Note 1: 'Read Only' policy also can be employed by setting DisableWebConfig to 0 ,
setting the secondary account to User_Monitor access level and distributing
the Main and Secondary accounts' user name password pairs according to
the organization's security policy.
Note 2: When DisableWebConfig is set to 1, all users are degraded to Read Only
privileges regardless of their access level.
9.2.2.2
Disabling the Embedded Web Server

You can deny access to the device's Web Server by changing the default of ini file
parameter DisableWebTask. The ability to disable access to the device's Web Server
via HTTP provides a high level of security in which protection against unauthorized
access (such as Internet hacker attacks) is included. This is particularly important to
users without a firewall.
To disable the Embedded Web Server:
9.2.2.3
Set the ini file parameter DisableWebTask to 1 (Default = 0, i.e. web task
enabled). Access to the device's Web Server is denied.
Encrypted HTTP transport (HTTPS - SSL)

Data transportation between Web server and Web client may be conducted over a
secured SSL link that encrypts the HTTP layer. The Web server may be configured to
accept communications only on a secured link (HTTPS) or both on a secured link
(HTTPS) and a non secured link (HTTP). For further details refer to the Appendix,
''Security'' on page 451.
9.2.2.4
Limiting Web Access to a Predefined List of Client IP Addresses

When client IP addresses are known in advance. Users can define a list of up to 10
client IP addresses that are to be accepted by the Web server. Any client that does
not bear an IP address in the predefined list is unable to connect to the Web server.
For further details refer to the Appendix, ''Security'' on page 451.
9.2.2.5
Managing Web Server Access Using a RADIUS Server

Users are given the option to manage the web server's password-username pairs via
a RADIUS server. When this option is used the Dual level access scheme is disabled
and all users that access the web server are deemed to be Administrators with
Read/Write privileges. For further details refer to the Appendix, ''Security'' on page
451.
9.2.3
Correlating PC / Mediant 3000 IP Address & Subnet Mask

Before using the Web browser to access the Mediant 3000s Embedded Web Server,
change the PCs IP address and Subnet Mask to correspond with the Mediant 3000s
factory default IP address and Subnet Mask shown in the table below. For details on
Version 4.8
205
January 2006
Mediant 3000
changing the IP address and Subnet Mask, refer to the Help information provided by
the Operating System used.
Table 9-3: Default IP Address and Subnet Mask

IP Address
Subnet Mask
10.1.10.10
255.255.0.0
Note 1: Note and retain the IP Address and Subnet Mask that you assign to the
device. Do the same when defining Username and Password (refer to
''Username and Password'' on page 203). If the Embedded Web Server is
unavailable (for example, if you have lost your Username and Password),
use the BootP/TFTP Server to access the device, reflash the files and
reset the password. For more information on the BootP/TFTP Server, refer
to the Appendix, ''BootP/TFTP Server'' on page 307.
9.2.4
Accessing the Embedded Web Server

To access the Embedded Web Server, take these 2 steps:
1.
Open any standard Web-browser application, such as Microsoft Internet

Explorer (Ver. 5.0 and higher) or Netscape Navigator (Ver. 7.2 and
higher).
Note: The browser must be Java-script enabled. If java-script is disabled, a

message box with notification of this is displayed.
2.
User's Manual
Specify the IP address of the device in the browser's URL field (e.g.,
http://10.1.229.17 or https://10.1.229.17 for an SSL secure link). The Embedded
Web Server Enter Network Password screen appears.
206
User's Manual
Figure 9-1: Enter Network Password Screen
9.2.5
Using Internet Explorer to Access the Embedded Web Server

Internet Explorer's security settings may block access to the Gateway's Web browser
if they're configured incorrectly. If this happens, the following message appears:
Unauthorized
Correct authorization is required for this area. Either your browser does not
perform authorization or your authorization has failed. RomPager server.
To troubleshoot blocked access to Internet Explorer, take these 7

steps:
Version 4.8
1.
Delete all cookies from the Temporary Internet files folder. If this does not clear
up the problem, the security settings may need to be altered. (Continue to Step
2).
2.
In Internet Explorer, from the Tools menu, select Internet Options. The Internet
Options dialog box appears.
3.
Select the Security tab, and then, at the bottom of the dialog box, click the
Custom Level button. The Security Settings dialog box appears.
4.
Scroll down until the Logon options are displayed and change the setting to
Prompt for user name and Password. Then Click OK.
5.
Select the Advanced tab.
6.
Scroll down until the HTTP 1.1 Settings are displayed and verify that the Use
HTTP 1.1 option is checked.
7.
Restart the browser. This fixes any issues related to domain use logon policy.
207
January 2006
Mediant 3000
9.2.6
Getting Acquainted with the Web Interface
9.2.6.1
About the Web Interface Screen

The figure below is an example of the General layout of the Web Interface screen.
Figure 9-2: Web Interface Screen - Example
The Web Interface screen contains the following parts:
Title bar - contains the corporate logo, background images and product name
Main menu bar - always appears to the left on every screen for quick access to
the other main modules
Sub-menu bar - always appears at the top on every screen and contains links to
the sub-menus of the main module selected in the main menu bar to the left
Main action pane - The main area of the screen in which information is viewed
and configured
The Web interface is divided into the following 7 modules in the main menu bar to the
left:
User's Manual
Quick Setup - Use this module to configure the device's basic settings. (For the
full list of configurable parameters go directly to the Protocol Management and
Advanced Configuration menus.)
Protocol Management - Use the menus in this module to configure the device's
control protocol parameters.
Advanced Configuration - Use the menus in this module to set the device's
advanced configuration parameters (for advanced users only).
Status & Diagnostics - Use the menus in this module to view and monitor the
device's channels, Syslog messages and hardware / software product
208
User's Manual

information.
Software Update - Use the menus in this module when you want to load new
software or configuration files onto the device.
Save Configuration - Use this menu to save configuration changes to the nonvolatile (flash) memory.
Reset - Use this menu to remotely reset the device.
Note: When positioning your curser over a parameter name for more than 1
second, a short description of this parameter is displayed.
9.2.6.2
Saving Changes
To save changes to the volatile memory (RAM) press the Submit button (changes to
parameters with on-the-fly capabilities are immediately available, other parameters
(prefixed with !) are updated only after a device reset). Parameters that are only
saved to the volatile memory revert to their previous settings after hardware reset
(software reset i.e. via the Web Interface offers the option to save the changes to the
non-volatile memory prior to the reset). To save changes so they are available after a
power fail, you must save the changes to the non-volatile memory (flash). When Save
Configuration is performed, all parameters and loaded files are saved to the nonvolatile memory.
To save the changes to non-volatile, take the next 2 steps:
9.2.6.3
1.
From the main menu on the left, click the Save Configuration link. The Save
Configuration screen appears.
2.
Click the Save Configuration button in the middle of the screen. A confirmation
message appears when the save is complete.
Quick Setup
To quickly setup the Mediant 3000, take these 16 steps:
1.
Access the Web Server Interface (refer to ''Accessing the Embedded Web
Server'' on page 206.)
2.
Enter the Administrator level Username (default: Admin) and Password

(default: Admin).
Note: The Username and Password fields are case-sensitive.
3.
Version 4.8
Click OK. The Quick Setup screen appears.
209
January 2006
Mediant 3000
Figure 9-3: Quick Setup Screen
4.
In the IP Configuration section, IP Address and Subnet Mask fields, enter the
appropriate addresses, which must correspond with your network IP Address
settings, or you can enable the DHCP negotiation to start after reset. Refer to
''Correlating PC /Mediant 3000 IP Address & Subnet Mask'' on page 205.
5.
For the Default Gateway Address, DNS Primary Server IP and DNS
Secondary Server IP fields, enter appropriate addresses. (If your network
features a DNS server, clarify with your Network Administrator).
6.
In the Trunk Configuration section, Protocol Type drop-down menu, select the
appropriate option. In the Clock Master Type (the trunk clock source) drop-down
menu, select either Recovered (the clock is recovered from the trunk; default) or
Generated (the trunk clock source is provided by the internal/TDM bus clock
source. The clock source depends on the parameter TDM Bus Clock Source
(Advanced Configuration > TDM Bus Settings).
7.
For the Framing Method dropdown menu, select the appropriate option. (For E1
trunks, always set the Framing Method to Extended Super Frame. For J1, keep
the default setting.)
Note: The Trunk Configuration parameters are global, and apply to all trunks. To
configure trunks individually (per trunk), refer to ''Trunk Settings'' on page
230.
8.
User's Manual
For the Line Code dropdown menu, select either B8ZS (bipolar 8-zero
substitution) for T1 trunks only; HDB3 (high-density bipolar 3) for E1 trunks only;
or AMI (Alternate Mark Inversion), which applies to both T1 and E1.
210
User's Manual
9.
For the Line Code dropdown menu, select either B8ZS (bipolar 8-zero
substitution) for T1 trunks only; HDB3 (high-density bipolar 3) for E1 trunks only;
or AMI (Alternate Mark Inversion), which applies to both T1 and E1.
10. In the Control Protocol Type section, for the Call Agent IP field, if your network
does not feature a DNS server that automatically defines the Call Agents IP
address, enter the appropriate IP address. If you have a DNS server, the field is
optional.
11. In the Call Agent Port field, enter the appropriate port ID. The default is 2427 for
MGCP and 2944 for MEGACO.
12. In the Call Agent Domain Name field, when using the DNS server option, enter
the Domain Name of the Call Agent operating with the Mediant 3000. The DNS
server automatically detects the Call Agents IP address from the Domain Name.
13. If you are working with MGCP, for the Gateway Name field, assign a name to the
device. (For example: gateway1.com). Ensure that the name you choose is the
one that the Call Manager/Agent is configured with to identify your Mediant 3000.
14. If you are working with MGCP, in the Endpoint naming scheme, for the Endpoint
Name and Endpoint Numbering Offset fields, enter an appropriate definitions.
Ensure that the definitions you choose are the definitions that the Call
Manager/Agent is configured with to identify your Mediant 3000.
15. Alternatively, in the Trunk naming scheme, for the Trunk Name field, Trunk
Numbering Offset and Endpoint Prefix fields, enter appropriate definitions.
Ensure that the definitions you choose are the definitions that the Call
Manager/Agent is configured with to identify your Mediant 3000.
16. At the bottom of the screen, click the Reset button. A dialog box appears in which
you confirm the reset action. The new information is added to the system
configuration while the system is restarted. A message informing you of the
waiting period appears. On the Mediant 3000, the Ready and LAN LEDs are lit
green.
9.2.7
Protocol Management
The Protocol Management screen offers access to the following Protocol configuration
screens using the Sub-menu bar at the top of the screen:
Protocol Selection - Refer to "Protocol Selection" below
Basic Configuration - Refer to 'Basic Configuration'
General Parameters - Refer to 'General Parameters'
Channel Configuration - Refer to 'Channel Configuration'
Advanced Configuration - Refer to 'Advanced Configuration'
To access the Protocol Management menu, take this step:
Version 4.8
From the main menu list on the left, click on the Protocol Management link. The
Protocol Management screen with the sub-menu bar on the top is displayed.
211
January 2006
Mediant 3000
Figure 9-4: Protocol Management Screen
9.2.7.1
Protocol Selection
To select the protocol type, take these 2 steps:
1.
Protocol Management screen appears.
2.
Click the radio button of the desired protocol.
Note: Changing the protocol type requires a device reset. When you have
completed configuring the desired parameters, the Mediant 3000 must be
reset using the Reset screen (refer to ''Reset Button'' on page 277) for the
changes to be implemented.
9.2.7.2
Basic Configuration
To configure the Basic Configuration take these 4 steps:
User's Manual
1.
Protocol Selection screen appears.
2.
From the sub-menu bar on the top, click the Basic Configuration link. The Basic
Configuration screen appears.
212
User's Manual
Figure 9-5: Basic Configuration Screen (MGCP)
Figure 9-6: Basic Configuration Screen (MEGACO)
3.
Version 4.8
Use the appropriate tables in the Appendix, ''Individual 'ini' File Parameters'' on
page 315 as a reference when configuring/modifying the Basic Configuration
parameter fields in the Basic Configuration screen.
213
January 2006
Mediant 3000
4.
9.2.7.3
After configuring/modifying the parameter fields, click the SUBMIT button. The
changes are entered into the system and the screen is refreshed.
General Parameters
To configure the General Parameters take these 4 steps:
1.
User's Manual
214
User's Manual
2.
From the sub-menu bar on the top, click the General Parameters link. The
General Parameters screen appears.
Figure 9-7: General Parameters Screen (MGCP)
Version 4.8
215
January 2006
Mediant 3000
Figure 9-8: General Parameters Screen (MEGACO)
9.2.7.4
3.
page 315 as a reference when configuring/modifying the General Configuration
parameter fields in the General Parameters screen.
4.
Channel Configuration
To configure the Channel Configuration take these 4 steps:
1.
User's Manual
216
User's Manual
2.
From the sub-menu bar on the top, click the Channel Configuration link. The
Channel Configuration screen appears.
Figure 9-9: Channel Configuration Screen (MGCP)
Figure 9-10: Channel Configuration Screen (MEGACO)
Version 4.8
3.
page 315 as a reference when configuring/modifying the Channel Configuration
parameter fields in the 'Channel Configuration' screen.
4.
217
January 2006
Mediant 3000
9.2.7.5
Advanced Configuration
To configure the Advanced Configuration take these 4 steps:
1.
2.
From the sub-menu bar on the top, click the Advanced Configuration link. The
Advanced Configuration screen appears.
Figure 9-11: Advanced Configuration Screen (MGCP)
Figure 9-12: Advanced Configuration Screen (MEGACO)
9.2.8
3.
page 315 as a reference when configuring/modifying the Advanced Configuration
parameter fields in the 'Advanced Configuration' screen.
4.
Advanced Configuration Screen

To access the Advanced Configuration screen take this step:
User's Manual
To access the devices advanced configuration parameters, from the main menu
list on the left, click the Advanced Configuration link. The Advanced
218
User's Manual

Configuration Parameters screen appears with the sub-menu bar on the top
displaying the following menu options:
Figure 9-13: Advanced Configuration Parameters Screen
Note: When SS7 is disabled, it does not appear as a menu item.
Network Settings - Contains a drop-down list with the following options:
IP Settings - Refer to ''IP Settings'' on page 221
Application Settings - Refer to ''Application Settings'' on page 222
Routing Table - Refer to ''Routing Table'' on page 224
VLAN Settings - Refer to ''VLAN Settings'' on page 225
Figure 9-14: Network Settings Drop-Down Menu
Media Settings - Contains a drop-down list with the following options:
Version 4.8
Voice Settings - Refer to ''Voice Settings'' on page 225

219
January 2006
Mediant 3000
Fax/Modem/CID Setttings - Refer to ''Fax/Modem/CID Setttings'' on page

226
RTP Settings - Refer to 'RTP Settings'
IPmedia Settings - Refer to ''IPmedia Settings'' on page 227
General Settings - Refer to ''General Settings' on page 228'

Figure 9-15: Media Settings Drop-Down Menu
Trunk Settings - Refer to ''Trunk Settings'' on page 230
SS7 Settings - Contains a drop-down list with the following options:
MTP2 Attributes - Refer to 'SS7 MTP2 Attributes' on page 234
SN Timers - Refer to 'SS7 Signaling Node Timers' on page 235
Link Set Timers - Refer to 'SS7 Link Set Timers' on page 236
Links - Refer to 'SS7 Links' on page 236
SNs - Refer to 'SS7 Signaling Nodes' on page 237
SigTran Group IDs - Refer to 'SS7 SigTran Group IDs' on page 240
SigTran Interface IDs - Refer to 'SS7 SigTran Interface IDs' on page 240
Figure 9-16: SS7 Settings Drop-Down Menu
User's Manual
TDM Bus Settings - Refer to ''TDM Bus Settings'' on page 241
Configuration File - Refer to ''Configuration File'' on page 242

220
User's Manual
Regional Settings - Refer to ''Regional Settings'' on page 243
Security Settings - Contains a drop-down list with the following options:
9.2.8.1
Web User Accounts - Refer to 'Web User Accounts' on page 245
Web Telnet Access List - Refer to 'Web Telnet Access List' on page 247
Firewall Settings - Refer to 'Firewall Settings' on page 248
Certificates - Refer to 'Certificates' on page 250
General Security Settings - Refer to 'General Security Settings' on page

251
IPsec Table - Refer to 'IPSec Table' on page 252
IKE Table - Refer to 'IKE Table' on page 254
Management Settings Refer to 'Management Settings' on page 256
IP Settings
To configure the IP Settings, take these 4 steps:
1.
From the main menu list on the left, click on the Advanced Configuration link.
The Advanced Configuration screen appears.
2.
From the sub-menu bar on the top, move the cursor on the Network Settings
link. A drop-down menu appears. Click on the IP Settings option. The IP
Settings screen appears.
Figure 9-17: IP Settings Screen
Version 4.8
3.
page 315 as a reference when configuring/modifying the IP Settings parameter
fields in the IP Settings screen.
4.
221
January 2006
Mediant 3000
9.2.8.2
Application Settings
To configure the Application Settings, take these 4 steps:
1.
2.
link. A drop-down menu appears. Click on the Application Settings option. The
Application Settings screen appears.
Figure 9-18: Application Settings Screen
User's Manual
3.
Use the ''Web Interface Parameters'' on page 379 table in the Appendix,
''Individual 'ini' File Parameters'' on page 315 as a reference when
configuring/modifying the network parameter fields in the Application Settings
screen.
4.
222
User's Manual
To configure the NFS Settings, take these 5 steps:

1.
To access the NFS Settings table, on the bottom of the Application Settings
screen, click the NFS Table
screen appears.
arrow button. The NFS Settings table
Figure 9-19: NFS Settings Table Screen
2.
To add a remote NFS file system, choose an available line number in the Line
Number drop-down list.
3.
Press the Add an Empty Line button.
4.
Enter values Host/IP and Root Path. Keep the defaults for the remaining
columns or change as needed.
5.
Press the Apply New Settings button. The remote NFS file system is mounted
immediately. Check the syslog server for the NFS mount was successful
message.
To delete a remote NFS file system, take these 2 steps:

1.
To delete a remote NFS file system, click the Edit radio button for the row to be
deleted.
2.
Press the Delete Line button. The row is deleted.
To modify an existing remote NFS file system, take these 2 steps:
Version 4.8
1.
To modify an existing remote NFS file system, click the Edit radio button for the
row to be modified.
2.
Change the values on the selected row as needed. When done making changes,
press the Apply New Settings button. The remote NFS file system is mounted
using the new settings. Check the syslog server for the NFS mount was
successful message.
223
January 2006
Mediant 3000
Note 1: The combination of Host/IP and Root Path should be unique for each row in
the table. For example, there should be only one row in the table with a
Host/IP of 192.168.1.1 and Root Path of /audio. [This applies to row add and
row modify operations]
Note 2: To avoid terminating calls in progress, a row should not be deleted or
modified while the board is currently accessing files on that remote NFS file
system.
Note 3: An NFS file server can share multiple file systems. There should be a
separate row in this table for each remote file system shared by the NFS file
server that needs to be accessed by this board.
9.2.8.3
Routing Table
To configure the Routing Table, take these 4 steps:
1.
2.
link. A drop-down menu appears. Click ON the Routing Table option. The
Routing Table screen appears.
Figure 9-20: Routing Table Screen
User's Manual
3.
To add a new routing entry, in the Add a new table entry fields at the bottom
portion of the screen, enter a the entry data and the click the Add New Entry
button.
4.
To delete an existing entry in the upper portion of the screen, click a checkmark
in the checkbox of the desired IP address row (more than one checkmark is
permissible) and then click the Delete Selected Entries button.
224
User's Manual
9.2.8.4
VLAN Settings
To configure the VLAN Settings, take these 4 steps:
1.
2.
link. A drop-down menu appears. Click the VLAN Settings option in the dropdown list. The VLAN Settings screen appears.
Figure 9-21: VLAN Settings Screen
9.2.8.5
3.
Use the ''Infrastructure Parameters'' on page 322 table as a reference when

configuring/modifying the VLAN Settings parameter fields in the VLAN Settings
screen.
4.
Voice Settings
To configure the Voice Settings, take these 4 steps:
1.
Version 4.8
225
January 2006
Mediant 3000
2.
From the sub-menu bar on the top, move the cursor on the Media Settings link.
A drop down menu appears. Click the Voice Settings option in the drop down
list. The Voice Settings screen appears.
Figure 9-22: Voice Settings Screen
9.2.8.6
3.
page 315 as a reference when configuring/modifying the Voice Settings
parameter fields in the Voice Settings screen.
4.
Fax/Modem/CID Settings
To configure the Fax/Modem/CID Settings, take these 4 steps:
1.
2.
From the sub-menu bar on the top, move the cursor on the Channel Settings
link. A drop-down menu appears. Click on the Fax/Modem/CID Settings option.
The Fax/Modem/CID Settings screen appears.
Figure 9-23: Fax/Modem/CID Settings Screen
User's Manual
226
User's Manual
9.2.8.7
3.
Use the appropriate tables in the Appendix, ''Individual ' on page 315ini 'File
Parameters'' on page 315 as a reference when configuring/modifying the
Fax/Modem/CID Settings parameter fields in the Fax/Modem/CID Settings
screen.
4.
RTP Settings
To configure the RTP Settings, take these 4 steps:
1.
2.
A drop-down menu appears. Click ON the RTP Settings option. The RTP
Figure 9-24: RTP Settings Screen (Network Settings)
9.2.8.8
3.
page 315 as a reference when configuring/modifying the RTP Settings parameter
fields in the RTP Settings screen.
4.
IPmedia Settings
To configure the IPmedia Settings, take these 4 steps:
1.
Version 4.8
227
January 2006
Mediant 3000
2.
A drop-down menu appears. Click on the IPmedia Settings option. The IPmedia
Figure 9-25: IPmedia Settings Screen
9.2.8.9
3.
Use the appropriate tables in the Appendix, ''Individual 'ini 'File Parameters'' on
page 315 as a reference when configuring/modifying the IPmedia Settings
parameter fields in the IPmedia Settings screen.
4.
General Media Settings

To configure the General Media Settings, take these 4 steps:
1.
2.
A drop-down menu appears. Click on the General option. The General Media
Figure 9-26: General Settings Screen
User's Manual
3.
Use the appropriate tables in the Appendix, ''Individual 'ini 'File Parameters'' on
page 315 as a reference when configuring/modifying the General Media Settings
parameter fields in the General Media Settings screen.
4.
228
User's Manual
9.2.8.10
PSTN Settings
9.2.8.10.1
T3 Settings
Note:
'T3' and 'DS3' are terms used interchangeably.
To configure the T3 Settings, take these 4 steps:

1.
2.
From the sub-menu bar on the top, move the cursor on the PSTN Settings link.
A drop-down menu appears. Click on the DS3 Settings option. The DS3
The DS3 Number and Status display are Read Only, showing the T3 LED status
and the T3 parameters shown in the figure below. (The number of DS3 elements
is hardware dependent.)
Figure 9-27: DS3 Settings Screen
3.
Configure/modify the fields in the DS3 Settings screen according to the table
below.
Table 9-4: DS3 Settings

Parameter
Description
DS3 Clock Source
Selects the clock source to be used
DS3 Framing Method
Selects the physical DS3 framing method to be used
DS3 Line Build Out
Selects the DS3 Line Built Out
Version 4.8
229
January 2006
Mediant 3000
4.
Click the SUBMIT button. The changes are entered into the system and the
following screen appears.
Figure 9-28: TP-6310/T3 Burn Configuration Screen
IMPORTANT
If you chose not to burn the device's configuration into flash memory, all
changes made since the last time the configuration was burned, will be lost
after the device is reset.
5.
Select the Burn radio button to burn the configuration into Flash Memory. Select
the No radio button not to allow graceful shutdown before reset. Click on the
Reset button. The following screen appears.
Figure 9-29: TP-6310 T3 Restart Screen
9.2.8.11
Trunk Settings
To view the Trunk Settings, take these 11 steps:
User's Manual
1.
The Advanced Configuration screen.
2.
From the Advanced Configuration screen, click the Trunk Settings option in the
sub-menu bar on the top. The Trunk Settings screen appears.
230
User's Manual
Initially, the screen appears with the parameters fields grayed (indicating readonly). The Stop Trunk button appears at the bottom of the screen.
Figure 9-30: Trunk Settings Screen
3.
To configure a specific trunks parameters or make a change to any of the

parameters, from the Trunks displayed on the top, click the Trunk Status indicator
to select a Trunk. The number of the Trunk is displayed in the upper-righthand corner of the Trunk Configuration display. The parameters displayed are
for the selected Trunk only.
The Trunk Status indicators can appear colored. The table below shows the
possible indicators and their descriptions.
Table 9-5: Trunk Status Color Indicator Key

Indicator
Color
Status
Gray
Description
Disabled
Green
Active - OK
Yellow
RAI Alarm
Remote Alarm Indication (the yellow alarm)
Red
LOS/LOFS
Loss of Signal or Loss of Frame move

the cursor on trunk to view the alarm type
Blue
AIS Alarm
Alarm Indication Signal (the blue alarm)
D-Channel Alarm
D-Channel Alarm
(ISDN only)
(ISDN only)
Orange
When modifying the Protocol Type, there are three different menu types that
match the following 3 protocol families:
Version 4.8
231
January 2006
Mediant 3000
Transparent
ISDN
CAS
When traversing between these 3 protocol families, the menu is modified to

include additional parameters appropriate to the family type selected.
Note: Different trunks can be defined with different protocols (CAS or ISDN
variants) on the same gateway (subject to the constraints in the Mediant
3000 Release Notes).
4.
At the bottom of the screen, click the Stop Trunk button to return the screen to a
modifiable state. The parameters are no longer grayed. When all trunks are
stopped (in a modifiable mode), two buttons are displayed at the bottom of the
screen:
Apply Trunk Settings button
Apply to all Trunks button
When at least one trunk has an Active trunk configuration state), only the Apply
Trunk Settings button appears.
5.
In the Trunk Configuration section, from the Protocol Type and Framing
Method drop-down lists, select the appropriate option. Since in the example
displayed in the figure below, Protocol Type is configured as E1 EURO ISDN,
the ISDN parameters are displayed. Configure the parameter ISDN Termination
Side as User side when the PSTN or PBX side is configured as Network side,
and vice versa. If you do not know the Mediant 3000 ISDN termination side,
choose User side and refer to the Status & Diagnostics screen. If the D-channel
alarm is indicated, choose Network side. For E1 trunks, always set the Framing
Method to Extended Super Frame.
6.
For each of the Bit line items, enter the direct Hex value of the bits in the text
box,
or,
User's Manual
232
User's Manual
configure the bit map directly by clicking the

arrow button, a new
window appears, with the specific bits (refer to the figure below).
Figure 9-31: Q931 Bit Map Screen
7.
For the Clock Master (the trunk clock source) drop-down list, select either
Recovered (the clock is recovered from the trunk; default) or Generated (the
trunk clock source is provided by the internal/TDM bus clock source) the above
selection depends on the parameter TDM Bus Clock Source. Refer to ''TDM Bus
Settings'' on page 241.
8.
For the Line Code drop-down list, select either B8ZS (bipolar 8-zero substitution)
for T1 trunks only; HDB3 (high-density bipolar 3) for E1 trunks only; or AMI for
both T1 and E1.
9.
After modifying any parameters, do one of the following:
To apply the changes to the selected trunk only, click the Apply Trunk
Settings button.
When configuring the device for the first time, or when no protocol is
specified for any trunk, To apply the changes to all trunks, click the Apply To
All Trunks button.
The screen is refreshed. Parameters become read-only (shown grayed). The

Stop Trunk button is displayed at the bottom of the screen.
To make a change to any of the parameters, click the Stop Trunk button to
return the screen to a modifiable state.
10. To commit the changes to the non-volatile (flash) memory, in the main menu on
the left, click the Save Configuration link. The Save Configuration screen
appears.
Version 4.8
233
January 2006
Mediant 3000
11. Click the Save button. The configuration is saved to non-volatile (flash) memory.
Note 1: A device reset may be needed in certain circumstances for the setup to be
activated, if a reset is needed the Web interface alerts the user. In case such
a device reset is needed, click the Reset link in main menu to the left,
choose the Burn option and click the Reset button to restart the device with
the new configuration.' (Refer to 'Rese't Button' on page 277.)
Note 2: If you are modifying multiple screens, and a reset is required in a certain
screen, perform the reset after you are finished modifying all of the screens
you intended and NOT after each screen.
9.2.8.12
SS7 Configuration
9.2.8.12.1
SS7 MTP2 Attributes
To configure the MTP2 Attributes, take these 4 steps:

1.
2.
From the sub-menu bar on the top, move the cursor on the SS7 Configuration
link. A drop-down menu appears. Click on the MTP2 Attributes option. The
MTP2 Attributes screen appears.
Figure 9-32: MTP2 Attributes Screen
User's Manual
234
User's Manual
9.2.8.12.2
3.
Use the table, ''SS7 Parameters'' on page 362 in the Appendix, 'Table
Parameters' on page 387 as a reference when configuring/modifying the fields in
the MTP2 Attributes screen.
4.
After configuring/modifying the parameter fields, click the Create button. The
SS7 Signaling Node Timers
To configure the SS7 Signaling Node Timers, take these 4 steps:

1.
2.
link. A drop-down menu appears. Click on the SN Timers option. The SS7
Signaling Node Timers screen appears.
Figure 9-33: SS7 Signaling Node Timers Screen
3.
Version 4.8
Use the table, ''SS7 Signaling Node Timers Table Parameters'' on page 387 in
the Appendix, 'Table Parameters' on page 387 as a reference when
configuring/modifying the fields in the SS7 Signaling Node Timers screen.
235
January 2006
Mediant 3000
4.
9.2.8.12.3
After configuring/modifying the parameter fields, click the Apply button. The
SS7 Link Set Timers
To configure the Link Set Timers, take these 4 steps:

1.
2.
link. A drop-down menu appears. Click on the Link Set Timers option. The Link
Set Timers screen appears.
Figure 9-34: SS7 Link Set Timers Screen
9.2.8.12.4
3.
Use the table, ''SS7 Signaling LinkSet Timers Table Parameters'' on page 391 in
the Appendix, 'Table Parameters' on page 387 as a reference when
configuring/modifying the fields in the Link Set Timers screen.
4.
After configuring/modifying the parameter fields, click the Apply button. The
SS7 Links
To configure the Links, take these 4 steps:

1.
User's Manual
236
User's Manual
2.
link. A drop-down menu appears. Click on the Links option. The Links screen
appears.
Figure 9-35: SS7 Links Screen
9.2.8.12.5
3.
Use the table, ''SS7 Signaling Link Table Parameters'' on page 392 in the
Appendix, 'Table Parameters' on page 387 as a reference when
configuring/modifying the fields in the Links screen.
4.
SS7 Signaling Nodes
To configure the SS7 Signaling Nodes, take these 4 steps:

1.
Version 4.8
237
January 2006
Mediant 3000
2.
link. A drop-down menu appears. Click on the SNs option. The SS7 Signaling
Nodes screen appears.
Figure 9-36: SS7 Signaling Nodes Screen
User's Manual
3.
Use the table, ''SS7 Signaling Node Table Parameters'' on page 387 in the
configuring/modifying the fields in the SS7 Signaling Nodes screen.
4.
238
User's Manual
To configure the Link Sets screen, take these 3 steps:

1.
From the SS7 Signaling Nodes screen, click on the Link sets link. The SS7 Link
Sets screen appears.
Figure 9-37: SS7 SN Link Sets Screen
2.
Configure/modify the fields in the SS7 Link Sets screen.
3.
To configure the Route Sets screen, take these 3 steps:

1.
From the SS7 Signaling Nodes screen, click on the Route sets link. The SS7
Link Sets screen appears.
Figure 9-38: SS7 SN Routes Screen
2.
Version 4.8
Configure/modify the fields in the SS7 Route Sets screen.
239
January 2006
Mediant 3000
3.
9.2.8.12.6
SS7 SigTran Group IDs
To configure the SigTran Group IDs, take these 4 steps:

1.
2.
link. A drop-down menu appears. Click on the SigTran Group IDs option. The
SigTran Group IDs screen appears.
Figure 9-39: SS7 SigTran Group IDs Screen
9.2.8.12.7
3.
Use the table, ''SigTran Interface GroupsTable Parameters'' on page 398 in the
configuring/modifying the fields in the SigTran Group IDs screen.
4.
SS7 SigTran Interface IDs
To configure the SigTran Interface IDs , take these 4 steps:

1.
User's Manual
240
User's Manual
2.
link. A drop-down menu appears. Click on the SigTran Interface IDs option. The
SigTran Interface IDs screen appears.
Figure 9-40: SS7 SigTran Interface IDs Screen
9.2.8.13
3.
Use the table, 'SigTran Interface IDs Table Parameters' in the Appendix, 'Table
Parameters' on page 387 as a reference when configuring/modifying the fields in
the SigTran Interface IDs screen.
4.
TDM Bus Settings

To configure the TDM Bus settings, take these 6 steps:
1.
2.
From the Advanced Configuration screen, click the TDM Bus Settings option in
the sub-menu bar on the top. The TDM Bus Settings screen appears.
Figure 9-41: TDM Bus Settings Screen
Version 4.8
241
January 2006
Mediant 3000
3.
page 315 as a reference when configuring/modifying the parameter fields in the
TDM Bus Settings screen.
4.
After configuring/modifying the parameter fields, click the Submit button. The
5.
To commit the changes to non-volatile (flash) memory, on the main menu to the
left, click the Reset link. The Reset screen appears.
6.
Select the Burn option and click the Reset button. (Refer to ''Reset Button'' on
page 277.)
Note 1: A device reset may be needed in certain circumstances for the setup to be
activated. Reset can be scheduled for a later time period when call traffic is
at a minimum. If you choose to schedule the Reset for a later time, be sure
to use' the 'Save Configuration scre'en' on page 276 to retain the changes to
the Mediant 3000s non-volatile memory.
Note 2: If you are modifying multiple screens, perform the reset after you are
finished modifying all of the screens you intended and NOT after each
screen.
9.2.8.14
Configuration File
The Configuration File screen enables you to restore/change (download a new ini file
to the Device) or backup the current configuration file that the device is using (make a
copy of the VoIP devices ini file and store it in a directory on your PC).
Restore your configuration - If the VoIP device has been replaced or has lost its
programming information, you can restore the VoIP device configuration file from
a previous backup or from a newly created ini file. To restore the VoIP Device
configuration from a previous backup you must have a backup of the VoIP device
information stored on your PC. (For information about restoring ini file defaults or
backup files, refer to' 'Restoring and Backing Up the Mediant 3000 Configuration''
on page 278.)
Back up your configuration - If you want to protect your VoIP device

programming. . The generated backup ini file contains values that have been set
by the user or are other than the default values.
In the Configuration File screen, you can bring an ini file from the device to a directory
in your PC, and send the ini file from your PC to the device.
Protect the device configuration by bringing the ini file from the device to your PC.
Later, if another device is replaced or loses its programming data, you'll be able to
restore / send the ini file backed up on your PC to the device.
The ini file is a proprietary configuration text file containing configuration parameters
and data. Sending the ini file to the device only provisions parameters that are
contained in the ini file.
The ini file with parameters set at their default values is on the CD accompanying the
device. The ini file can also be received as an e-mail attachment from AudioCodes'
Technical Support. Users can also generate their own ini file using AudioCodes'
DConvert utility (refer to the Appendix, ''Utilities'' on page 495).
User's Manual
242
User's Manual
To save the ini file to the PC, take these 3 steps:

1.
2.
From the Advanced Configuration screen, click the Configuration File link in the
sub-menu bar on the top. The Configuration File screen appears.
Figure 9-42: Configuration File Screen
3.
Click the Get ini File button. You are prompted to select a location in which to
save it.
Note: The ini file that you save from the device to the PC contains only those
parameters whose values you modified following receipt of the device. It
does not contain parameters unchanged at their (original) default value.
To load an ini file from the PC to the device, take these 4 steps:
1.
Click on the Browse button next to the Send the ini file from your computer to
the device field and navigate to the location of the predefined ini file. Refer to the
figure below.
2.
Click the Send File button. The file loading process is activated. When the
loading is complete, a verification message is displayed at the bottom of the
screen: File XXXX was successfully loaded into the device.
3.
From the main menu list on the left, click Reset. The Reset screen appears.
4.
Select the Burn option and click the Restart button. Wait for the device to reset.
After self-testing, the Ready and LAN LEDs on the devices front panel are lit
green. Any malfunction causes the Ready LED to change to red.
Users can restore default parameters by clicking the Restore All Defaults button.
9.2.8.15
Regional Settings
From the Regional Settings screen users can send a Call Progress Tones dat file, a
CAS dat file and/or a Voice Prompts dat file to the device from their PC.
Version 4.8
243
January 2006
Mediant 3000
To access the Regional Settings screen, take these 2 steps:

1.
2.
From the sub-menu bar on the top, click the Regional Settings link. The
Regional Settings screen appears.
Figure 9-43: Regional Settings Screen - Sending CPT, CAS and/or Voice Prompt File to the
Device
The files are available on the CD accompanying your device. They can also be
received as an e-mail attachment from AudioCodes' Technical Support. A Call
Progress Tones txt file can be modified and converted into the binary dat file (refer to
'Converting a CPT ini File to a Binary dat File' in the Appendix, 'Utilities'). When
modifying the Call Progress Tones File, only the dat file can be sent from your PC to
the device. (Refer to ''Modifying the Call Progress Tones File'' on page 415 and the
Appendix, ''Utilities'' on page 495.)
The Call Progress Tones dat file is a region-specific, telephone exchangedependent file. It provides call status/call progress to Customers, operators, and
connected equipment. Default Tones: USA.
The dat Voice Prompts file is played by the device during the phone conversation
on Call Agent request. Download if you have an application requiring Voice
Prompts. The Voice Prompt buffer size in the board is 10 Mbyte.
To send a Call Progress Tone, CAS, or Voice Prompt file to the

board, take these 6 steps:
User's Manual
1.
2.
From the sub-menu bar on the top, click the Regional Settings link. The
Regional Settings screen appears. (Refer to the figure below.)
3.
Click the Browse button to locate the predefined Call Progress Tone, CAS, or
Voice Prompt file as appropriate. (A new software file package may be issued
from AudioCodes or your local supplier.)
4.
Click the Send File button. The file is sent to the board, overwriting the previous
one. The screen is refreshed and a message informs you about the waiting
244
User's Manual

period. When the loading is complete, a verification message is displayed at the
bottom of the screen: File XXX was successfully loaded into the device.
5.
For CPT file downloading only - (The rest of files do not require a device reset.)
From the main menu list on the left, click Reset. The Reset screen appears.
6.
Select the Burn option and click the Restart button. Wait for the device to reset.
After self-testing, the Ready and LAN LEDs on the devices front panel are lit
green. Any malfunction causes the Ready LED to change to red.
To set the date and time, take these 2 steps:

1.
Enter the date and/or time using the YYYY, MM, and DD field for Year, Month
and Day and HH, MM, and SS fields for Hour, Minutes and Seconds.
2.
Click the Set Date and Time button. The date and time is set on the device,
accordingly.
Note: When the NTP feature is enabled (the NTP server is defined in the Network
Settings screen), the date and time are in Read Only mode as they are set
by the NTP server.
9.2.8.16
Security Settings
9.2.8.16.1
Web User Accounts
To change the Web User Accounts attributes, take these 13 steps:

1.
2.
From the sub-menu bar on the top, move the cursor on the Security Settings
link. A drop-down menu appears. Click on the Web User Accounts option. The
Web User Accounts screen appears.
Note 1: A user with Security Administrator access level may change all attributes
for all accounts. A user with an access level other than Security
Administrator can only change their own Username and Password.
Note 2: The access level of the first user account is defined as Security
Administrator and can not be changed.
Note 3: The Password and Username can each be up to 19 characters and are case
sensitive.
3.
Version 4.8
For Security Administrator Access Level
245
January 2006
Mediant 3000
The figure below appears when the current logged on user has the Security
Administrator access level, in which all of the user accounts are displayed.
Figure 9-44: Web User Accounts Screen - Security Administrator Level
4.
To change the Access Level attribute, choose the new access level and click the
Change Access Level button.
5.
To change the User Name attribute, enter a new user name and click the
Change User Name button. The Enter Network Password screen appears.
Figure 9-45: Enter Network Password Dialog
User's Manual
6.
Enter a new username and he current password. The new username takes effect
immediately.
7.
To change the Password attribute, enter the current Password, New Password
and New Password confirmation in the corresponding fields and click the Change
Password button. The Enter Network Password screen appears. (Refer to the
figure above.)
8.
Enter a the username and he new password. The new password takes effect
immediately.
246
User's Manual
9.
For Users with Privileges Lower than Security Administrator

If the current logged on user has less than the Security Administrator
access level, only the user account of the current logged on user is
displayed.
Figure 9-46: Web User Accounts Screen - For Users with Privileges Lower than Security
Administrator
10. To change the User Name attribute, enter a new user name and click the
Change User Name button. The Enter Network Password dialog appears.
(Refer to the figure, "Enter Network Password Dialog" above.
11. Enter a new username and he current password. The new username takes effect
immediately.
12. To change the Password attribute, enter the current Password, New Password
and New Password confirmation in the corresponding fields and click the Change
Password button. The Enter Network Password screen appears. (Refer to the
figure above.)
13. Enter a the username and he new password. The new password takes effect
immediately.
Note: For information on adding additional Web User Accounts, refer to ''RADIUS
Support'' on page 464.
9.2.8.16.2
Web & Telnet Access List
To configure the Web & Telnet Access List, take these 4 steps:
1.
Version 4.8
247
January 2006
Mediant 3000
2.
link. A drop-down menu appears. Click on the Web & Telnet Access List option.
The Web & Telnet access List screen appears.
Figure 9-47: Web & Telnet Access List Screen
3.
To add a new authorized IP address, in the New Authorized IP Address field at

the bottom portion of the screen, enter the desired IP address and click the Add
New Address button.
4.
To delete an authorized IP address, in the upper portion of the screen, click a

checkmark into the checkbox of the desired IP address row (checkmarks in more
than one row is permissible) and click the Delete Selected Addresses button.
Note 1: When all authorized IP addresses are deleted this security feature becomes
disabled.
Note 2: When adding the first authorized IP address, you should add your own
terminal's IP address in order to be able to connect to the web server after
adding the first IP address that is not your current terminal's IP address.
9.2.8.16.3
Firewall Settings
To access the Firewall Settings, take these 2 steps:

1.
User's Manual
248
User's Manual
2.
link. A drop-down menu appears. Click on the Firewall Settings option. The
Firewall Settings screen appears.
Figure 9-48: Firewall Settings Screen
To add a new entry to the Firewall Settings table, take this step:
In the New Rule Index field in the middle of the screen, type the entry index and
click the Add an Empty Rule button. An empty Rule row appears.
or,
Click the radio button of the Rule row you want to copy and click the Copy
Selected Rule as a New Rule button. An exact copy of the selected rule appears
as a new Rule row.
Note: Adding new Rule row entries in itself does not activate them. New Rule row
entries should be configured before activating the entries.
To edit a Rule row entry of the Firewall Settings table, take these 2
steps:
1.
Click the radio button of that Rule row to be edited and click the Make Rule
Editable button. The fields of the Rule row becomes configurable.
2.
Modify the fields as needed and click the Apply Rule Settings button. The
Mediant 3000 is immediately updated.
To activate a Rule row entry of the Firewall Settings table, take this
step:
Version 4.8
Click the radio button of that Rule row to be activated and click the Activate Rule
button.
249
January 2006
Mediant 3000
To deactivate a Rule row entry of the Firewall Settings table, take

this step:
Click the radio button of that Rule row to be deactivated and click the DeActivate
Rule button.
To delete a Rule row entry of the Firewall Settings table, take this
step:
9.2.8.16.4
Click the radio button of that Rule row to be deleted and click the Delete Rule
button.
Certificates
To configure the General Security Settings, take these 8 steps:

1.
2.
link. A drop-down menu appears. Click the Certificates option. The Certificate
Signing Request screen appears.
Figure 9-49: Certificate Sighing Request Screen
3.
User's Manual
In the Subject Name field, type a name for the certificate signing request. The
maximum number of characters is 32.
250
User's Manual
4.
Click the Generate CSR button. The certificate signing request appears in the
screen.
Figure 9-50: Certificate Signing Request
9.2.8.16.5
5.
Copy the certificate signing request and sent it to your Certification Authority for
signing. The Certification Authority sends you a Server Certificate file and a
Trusted Root Certificate Store file, which you should store on the local PC.
6.
To send the Server Certificate file to the Mediant 3000, type in the file name, or
use the Browse button to navigate to the appropriate .txt file, and click the Send
File button.
7.
To send the Trusted Root Certificate Store file to the Mediant 3000, type in the
file name, or use the Browse button to navigate to the appropriate .txt file, and
click the Send File button.
8.
To modify the Private Key file, type in the file name, or use the Browse button to
navigate to the appropriate file, and click the Send File button. The file is in
PEM format, provided by a third-party source.
General Security Settings
To configure the General Security Settings, take these 4 steps:

1.
Version 4.8
251
January 2006
Mediant 3000
2.
link. A drop-down menu appears. Click the General Security Settings option.
The General Security Settings screen appears.
Figure 9-51: General Security Settings Screen
9.2.8.16.6
3.
Configure/modify the parameter fields.
4.
Click the SUBMIT button. The changes are entered into the system and the
screen is refreshed.
IPSec Table
Note: IPSec Security Settings availability is in accordance with the Mediant 3000's
Software Upgrade Key.
To configure the IPSec table , take these 6 steps:

1.
User's Manual
252
User's Manual
2.
link. A drop-down menu appears. Click the IPSec Table option. The IPSec Table
screen appears.
Figure 9-52: IPSec Table Screen (Existing Table Row)
Figure 9-53: IPSec Table Screen (Non -Existing Table Row)
Version 4.8
253
January 2006
Mediant 3000
9.2.8.16.7
3.
Each screen represents a single row in the IPSec table. User can navigate
between rows by selecting the desired row index in the Policy Index drop-down
list at the top of the screen.
4.
Table rows may be in 2 states existent or non-existent as stated in option

showing in the Policy Index drop-down list.
5.
For an existent row you may delete it by clicking the Delete button, or you may
re-configure it by configuring the desired parameters and clicking the Apply
button.
6.
For a non existent row you may create it by configuring the parameters and
clicking the Create button.
IKE Table
Note: IKE Security Settings availability is in accordance with the Mediant 3000's
Software Upgrade Key.
To configure the IKE table , take these 6 steps:

1.
User's Manual
254
User's Manual
2.
link. A drop-down menu appears. Click the IKE Table option. The IKE Table
screen appears.
Figure 9-54: IKE Table Screen (Existing Table Row)
Figure 9-55: IKE Table Screen (Non -Existing Table Row)
Version 4.8
255
January 2006
Mediant 3000
9.2.8.17
3.
Each screen represents a single row in the IKE table. User can navigate between
rows by selecting the desired row index in the Policy Index drop-down list at the
top of the screen.
4.
Table rows may be in 2 states existent or non-existent as stated in the

options showing in the Policy Index drop-down list.
5.
For an existent row you may delete it by clicking the Delete button, or you may
re-configure it by configuring the desired parameters and clicking the Apply
button.
6.
For a non existent row you may create it by configuring the parameters and
clicking the Create button.
Management Settings
To configure the Management Settings, take these 3 steps:
1.
User's Manual
256
User's Manual
2.
From the sub-menu bar on the top, Click on the Management Settings link. The
Management Settings screen appears.
Figure 9-56: Management Settings Screen
3.
Version 4.8
257
January 2006
Mediant 3000
To configure the SNMP Managers table, take these 2 steps:

1.
To access the SNMP Managers table, on the Management Settings screen, click
the SNMP Managers Table
Table screen appears.
arrow button. The SNMP Managers
Figure 9-57: SNMP Managers Table Screen
The SNMP Managers table allows you to configure the SNMP manager's
attributes.
Note: By un-checking a checkbox and clicking SUBMIT, the whole table row is
deleted. By checking the checkbox and clicking SUBMIT, the whole table
row is created with the current field inputs in that row.
2.
User's Manual
Configure the table as desired and click the SUBMIT button and then click the
Close Window button. The lines appear in the Application Settings screen.
258
User's Manual
To configure the SNMP Community String table, take these 2

steps:
1.
To access the SNMP Community String table, on the Management Settings

screen, click the SNMP Community Strings
Community String screen appears.
arrow button. The SNMP
Figure 9-58: SNMP Community String Screen
Note: By marking a checkbox and clicking SUBMIT, the whole table row is deleted.
By only clicking SUBMIT, the whole table row is created with the current field
inputs in that row.
2.
Version 4.8
Configure the table as desired and click the SUBMIT button.
259
January 2006
Mediant 3000
9.2.9
Status and Diagnostic Menu

To access the Status and Diagnostics menu, take this step:
From the main menu list on the left, click on the Status and Diagnostics link.
The Status and Diagnostics screen with the sub-menu bar on the top is
displayed.
Figure 9-59: Status and Diagnostic Menu Screen
9.2.9.1
Channel Status - Refer to 'Channel Status' on page 260
Message Log - Refer to 'Message Log' on page 263
Device Information - Refer to 'Device Information' on page 264
Ethernet Port Information - Refer to Ethernet Port Information
Channel Status
To access the Trunk and Channel Status screen, take these 3
steps:
1.
User's Manual
The Status and Diagnostics screen appears.
260
User's Manual
2.
From the sub-menu bar on the top, click the Channel Status link. The Trunk and
Channel Status screen appears. The screen is Read-only.
Figure 9-60: Trunk and Channel Status Screen
The number of trunks and channels that appear on the screen depends of the system
configuration.
The Trunk and Channel Status indicators can appear colored. The table below shows
the possible indicators and their descriptions.
Table 9-6: Trunk and Channel Status Color Indicator Key

Trunk
Indicator
Channel
Color
Gray
Indicator
Disabled
Color
Gray
Description
Inactive
Green
Active - OK
Green
Active
Yellow
RAI Alarm
Purple
SS7
LOS/LOF Alarm
Black
Non-Voice
Red
Version 4.8
Description
261
January 2006
Mediant 3000
Table 9-6: Trunk and Channel Status Color Indicator Key

Trunk
Channel
Blue
Orange
3.
AIS Alarm
D-Channel Alarm
To display a screen with a summary of parameter information relevant to a

channel, click on the channel.
The following 'per channel' Read-Only screen information is available when
clicking on a specific channel:
Figure 9-61: Basic Information Screen
Initially, the Basic information screen is displayed. Above there are links to the
RTP/RTCP Information screen and the Voice Information screen, in addition to
the Basic Information screen.
User's Manual
262
User's Manual
To access the RTP/RTCP Information screen, take this step:
Click on RTP/RTCP link. The RTP/RTCP Information screen appears.

Figure 9-62: RTP/RTCP Information Screen
To access the Voice Settings screen, take this step:
Click on Voice Settings link. The Voice Information screen appears.

Figure 9-63: Voice Information Screen
9.2.9.2
Message Log
The Message Log is similar to a Syslog. It provides debug messages useful in
pursuing troubleshooting issues.
The Message Log serves the Web Server and is similar to a Syslog server. It displays
debug messages. It is not recommend to use the Message Log screen for logging
errors and warnings because errors can appear over a prolonged period of time, e.g.,
a device can display an error after running for a week. Similarly, It is not recommend
to keep a Message Log session open for a prolonged period (refer to the Note below).
For logging of errors and warnings, refer to ''Syslog'' on page 281.
Version 4.8
263
January 2006
Mediant 3000
To activate the Message Log, take these 4 steps:

1.
The Status and Diagnostics screen appears and Log is activated.
2.
From the sub-menu bar on the top, click the Message Log link. The Message
Log screen appears.
Figure 9-64: Message Log Screen
3.
After receiving messages - Using the scroll bar, select the messages, copy them
and paste them into a text editor such as Notepad. Send this txt file to Technical
Support for diagnosis and troubleshooting as needed.
4.
To clear the screen of messages, click on the sub-menu Message Log. The
screen is cleared. A new session is activated and new messages begin
appearing.
Note: Do not keep the Message Log screen activated and minimized for a
prolonged period as a long session may cause the PC workstation to
overload. While the screen is open (even if minimized), a session is in
progress and messages are sent. Closing the window or moving to another
link stops the messages and terminates the session.
9.2.9.3
Device Information
The Device Information screen displays hardware, software product information and
Device state information. This information can help you to expedite any
troubleshooting process. Capture the screen and email it to Technical Support
personnel to ensure quick diagnosis and effective corrective action.
The screen also displays any loaded files in the device.
User's Manual
264
User's Manual
To display the Device Information screen, take these 2 steps:

1.
2.
From the sub-menu bar on the top, click the Device Information link. The Device
Information screen appears.
Figure 9-65: Versions Screen
To delete any loaded files, take these 5 steps:
9.2.10
1.
2.
From the sub-menu bar on the top, click the Device Information link. The Device
Information screen appears.
3.
In the Device Information table, click the Delete button. The file deletion takes
effect only after a device reset is performed.
4.
In main menu to the left, click the Reset link. The Reset screen appears.
5.
Select the Burn option and click the Reset button to restart the device with the
new settings. (Refer to ''Reset Button'' on page 277.)
Software Update
The Software Update screen offers two options for downloading current software
update files: the Software Upgrade Wizard and Load Auxiliary Files screen.
In addition, the Software Upgrade Key screen is provided for users to enter their
updated Software Upgrade keys.
Version 4.8
Software Upgrade Wizard - Refer to "Software Upgrade Wizard" below
Load Auxiliary Files - Refer to ''Auxiliary Files Download'' on page 272

265
January 2006
Mediant 3000
9.2.10.1
Software Upgrade Key - Refer to ''Software Upgrade Key'' on page 273
Software Upgrade Wizard

The Software Upgrade Wizard allows the user to upgrade the Mediant 3000's software
by loading a new *.cmp file together with a full suite of useful auxiliary files.
Loading a *.cmp file is mandatory in the Software Upgrade Wizard process. During the
process, you choose from the auxiliary files provided for loading. For each auxiliary file
type, you can choose between reloading an existing file, loading a new file or not
loading a file at all.
Figure 9-66: Start Software Upgrade Screen
To use the Software Upgrade Wizard take these 12 steps:

Note: The Software Upgrade Wizard requires the device to be reset at the end of
the process, which disrupts any existing traffic on the device. To avoid
disrupting traffic, disable all traffic on the device before initiating the Software
Upgrade Wizard.
User's Manual
1.
Stop all traffic on the device (refer to the note above.)
2.
From the main menu list on the left, click on the Software Update link. The
Software Upgrade screen with the sub-menu bar on the top is displayed.
266
User's Manual
3.
On the sub-menu bar on the top, click the Software Upgrade Wizard link. The
Start Software Upgrade screen appears.
Figure 9-67: Start Software Upgrade Screen
Note: At this point you may cancel the Software Upgrade process with no
consequence to the device by using the cancel button. If you continue with
the Software Upgrade process by clicking the Start Software Upgrade
button, the process must be followed through and completed with a device
reset at the end of the process. If you use the Cancel button, in any of the
subsequent screens, the Software Upgrade process causes the device to be
reset.
Version 4.8
267
January 2006
Mediant 3000
4.
Click the Start Software Upgrade button to initiate the upgrade process. The
File Loading screen appears displaying the cmp file information. The background
Web screen is disabled. During the Software Upgrade process, the rest of the
Web application is unavailable. After the Software Upgrade process is complete,
access to the full Web application is restored.
Figure 9-68: Load CMP File Dialog Screen
Note the file type list in the left side of the screen. This list contains the relevant
file types that can be loaded via the wizard for this device type. The highlighted
file type in the file type list indicates which file type is being displayed in the main
part of the screen. As you continue through the Software Upgrade process by
clicking on the Next button, each of the relevant file type screens are presented,
going down the list until the Finish screen appears.
Note: The Next button is disabled until you load a *.cmp file. After a *.cmp file is
selected, the wizard upgrade process continues and the Next button is
enabled.
5.
User's Manual
Click the Browse button and navigate to the location of the *.cmp file to be
loaded. The path and file name appears in the field.
268
User's Manual
6.
Click the Send File button to send the file to the device. The File Loading screen
appears with a progress bar indicating the loading period. When the loading is
complete, a message is displayed indicated the file was successfully loaded into
the device.
Figure 9-69: File Loading Dialog Screen
All four buttons (Cancel, Reset, Back, and Next) in the bottom portion of the
screen are activated.
7.
8.
You may choose between these options:
Loading Additional Auxiliary Files
Completing the Software Upgrade Process
Cancel Upgrade Process and revert to the Previous Configuration Files
Loading Additional Auxiliary Files

To move to the next file type on the list to the left, click the Next button. The File
Loading screen appears with the next relevant file type highlighted.
For each file type the user has three options:
Version 4.8
Load a new auxiliary file to the device using the Browse and Send File'
button as described above.
Load the existing auxiliary file - A checkbox (checked by default as shown in

the figure below) appears if relevant to the device. If this checkbox is
checked, the existing file is used in the upgraded system.
Avoid loading any file at all - Clear the checkbox (if the checkbox appears).
269
January 2006
Mediant 3000
Continue through each of the file type screens by clicking Next and selecting one
of the above options. As an example, the figure below displays the File Loading
screen with the CPT file type selected.
Figure 9-70: File Loading Dialog Screen - CPT Type Displayed
9.
Completing the Software Upgrade Process

From any of the file type screens, you can complete the Software Upgrade
process by clicking the Reset button. The device is reset utilizing the new files
you have loaded up to that point, as well as using the existing files according to
the checkbox status of each file type.
10. Revert to the Previous Configuration Files

From any of the file type screens, you can revert to the previous configuration by
clicking the Cancel button. The Software Upgrade process is terminated and the
device is reset utilizing the previous configuration files. Similar screens as shown
in two figures below are displayed.
User's Manual
270
User's Manual
11. When continuing through the Software Upgrade process, you complete the
process from the Finish screen by clicking the Reset button (the Next button is
disabled).
Figure 9-71: File Loading Dialog Screen - Reset Button Stage
During the Reset process, the device burns the newly loaded configuration to
the non-volatile memory. The File Burning screen appears displaying the File
Burning to Flash Memory progress bar. When this is completed, the Reset
Device screen appears displaying the Reset in progress bar. When this is
complete, the End Of Process screen appears displaying the current
configuration information.
Figure 9-72: End of Process Dialog Screen
12. Click the End Process button. The Quick Setup screen appears and the full Web
application is reactivated.
Version 4.8
271
January 2006
Mediant 3000
9.2.10.2
Auxiliary Files Download

The Auxiliary Files Download screen facilitates the download of software updates
using the HTTP protocol. Types of software file updates include:
Voice Prompt - The dat Voice Prompts file is played by the device during the
phone conversation on Call Agent request. Download if you have an application
requiring Voice Prompts.
Call Progress Tone - usa_tones.dat - This is a region-specific, telephone

exchange-dependent file. Call Progress Tones provide call status/call progress to
customers, operators, and connected equipment. Default Tones: U.S.A.
usa_tones.ini - The ini file is the value of the different Call Progress Tones files
(frequency, cadence, etc.). To convert the usa_tones.ini file, which is a txt file, to
a usa_tones.dat file that can be downloaded into the Mediant 3000, use the Call
Progress Tones file generator utility TPDMUtil.exe.
Prerecorded Tones - The *.dat PRT file enhances the devices capabilities to play
a wide range of telephone exchange tones.
CAS - cas.dat includes E1/T1 CAS signaling files, such as E_M_WinkTable.dat,

These files are not needed for ISDN protocols.
To download an auxiliary file, take these 5 steps:

1.
From the main menu list on the left, click on the Software Download link. The
Software Download screen is displayed.
2.
From the sub-menu bar on the top, click the Auxiliary Files Download link. The
Auxiliary Files Download screen appears.
Figure 9-73: Auxiliary Files Download Screen
User's Manual
3.
Use the Browse button to locate the appropriate file on your PC.
4.
Click the Send File button. The files are sent to the Mediant 3000.
272
User's Manual
5.
To commit the changes to the non-volatile (flash) memory, in the main menu on
the left, click the Save Configuration link. In the Save Configuration screen
that appears, click the Save Configuration button. The changes are committed
to the non-volatile memory.
Note: A device reset is required to activate a loaded CPT file, and may be required
for the activation of certain ini file parameters. The Burn option must be
selected. (Refer to ''Reset Button'' on page 277.)
9.2.11
Software Upgrade Key

Mediant 3000s are loaded with a Software Upgrade Key already pre-configured for
each of its TrunkPack Modules.
Users can later upgrade their Mediant 3000 features, capabilities and quantity of
available resources by specifying the upgrades they require and the corresponding
board's or TPM's serial number (or MAC address), and ordering a new key to match
their specification.
The Software Upgrade Key is sent as a string in a text file, to be loaded into the
Mediant 3000. Stored in the Mediant 3000s non-volatile flash memory, the string
defines the features and capabilities allowed by the specific key purchased by the
user. The Mediant 3000 allows users to utilize only these features and capabilities. A
new key overwrites a previously installed key.
Note: The Software Upgrade Key is an encrypted key provided by AudioCodes
only.
9.2.11.1
Backing up the Current Software Upgrade Key

Back up your current Software Upgrade Key before loading a new key to the Mediant
3000. You can always reload this backed-up key to restore your Mediant 3000
capabilities to what they originally were if the new key does not comply with your
requirements.
To backup the current Software Upgrade Key, take these 5 steps:
Version 4.8
1.
Access the Mediant 3000's Embedded Web Server (refer to the ''Embedded Web
2.
Click the Software Update button.
3.
Click the Software Upgrade Key tab. The Software Upgrade Key screen is
displayed (shown in the figure, ''Software Upgrade Key Screen'' below).
4.
Copy the string from the Current Key field and paste it in a new file.
5.
Save the text file with a name of your choosing.
273
January 2006
Mediant 3000
9.2.11.2
Loading the Software Upgrade Key

After receiving the Software Upgrade Key file (do not modify its contents in any way),
ensure that its first line is [LicenseKeys] and that it contains one or more lines in the
following format:
S/N<Serial Number of TrunkPack module> = <long Software Upgrade Key>
For example: S/N370604 = jCx6r5tovCIKaBBbhPtT53Yj...
One S/N must match the S/N of your Mediant 3000 TrunkPack module. The Mediant
3000s S/N can be viewed in the Device Information screen (refer to ''Device
Information'' on page 264).
You can load a Software Upgrade Key using:
9.2.11.3
The Embedded Web Server (refer to ''Loading the Software Upgrade Key Using
the Embedded'' below).
The BootP/TFTP configuration utility (refer to ''Loading the Software Upgrade Key
Using BootP/TFTP'' on page 275).
AudioCodes EMS (refer to the EMS Users Manual or EMS Product Description).
Loading the Software Upgrade Key Using the Embedded Web

Server
To load a Software Upgrade Key using the Web Server, take these
6 steps:
1.
Access the Mediant 3000's Embedded Web Server (refer to ''Accessing the
Embedded Web Server'' on page 206).
2.
Click the Software Update button.
3.
Click the Software Upgrade Key tab; the Software Upgrade Key screen is
displayed (shown in the figure, 'Software Upgrade Key Screen' below).
4.
When loading a single key S/N line to a Mediant 3000:

Open the Software Upgrade Key file (it should open in Notepad), select and copy
the key string of the Mediant 3000s S/N and paste it into the Web field New Key.
If the string is sent in the body of an Email, copy and paste it from there. Press
the Add Key button.
5.
When loading a Software Upgrade Key text file containing multiple S/N lines
to a Mediant 3000:
(Refer to the figure, ''Example of a Software Upgrade Key File Containing Multiple
S/N Lines'' on page 275)
Click the Browse button in the Send Upgrade Key file from your computer
to the device field, and navigate to the Software Upgrade Key text file.
Click the Send File button.
The new key is loaded to the Mediant 3000, validated and if valid is burned to
memory. The new key is displayed in the Current Key field.
Validate the new key by scrolling through the Key features: panel and verifying the
presence / absence of the appropriate features.
6.
User's Manual
After verifying that the Software Upgrade Key was successfully loaded, reset the
Mediant 3000; the new capabilities and resources are active.
274
User's Manual
Figure 9-74: Software Upgrade Key Screen
Figure 9-75: Example of a Software Upgrade Key File Containing Multiple S/N Lines
9.2.11.4
Loading the Software Upgrade Key Using BootP/TFTP

To load the Software Upgrade Key file using BootP/TFTP, take
these 5 steps:
Version 4.8
1.
Place the file in the same location youve saved the Mediant 3000s cmp file.
Note that the extension of the Software Upgrade Key must be ini.
2.
Start the BootP/TFTP configuration utility and from the Services menu in the
main screen, choose option Clients; the Client Configuration screen is displayed
(refer to the 'Client Configuration Screen').
3.
From the drop-down list in the INI File field, select the Software Upgrade Key file
instead of the Mediant 3000s ini file. Note that the Mediant 3000s cmp file must
be specified in the Boot File field.
275
January 2006
Mediant 3000
9.2.11.5
4.
Configure the initial BootP/TFTP parameters required, and click OK (refer to the
Appendix, ''BootP/TFTP Server'' on page 307).
5.
Reset the Mediant 3000; the Mediant 3000s cmp and Software Upgrade Key
files are loaded to the Mediant 3000.
Verifying that the Key was Successfully Loaded

After installing the key, you can determine in the Embedded Web Servers read-only
Key features: panel (Software Update menu > Software Upgrade Key) (refer to
Figure H-1) that the features and capabilities activated by the installed string match
those that were ordered.
You can also verify that the key was successfully loaded to the Mediant 3000 by
accessing the Syslog server. For detailed information on the Syslog server, refer to
''Syslog'' on page 281. When a key is successfully loaded, the following message is
issued in the Syslog server:
"S/N___ Key Was Updated. The Board Needs to be Reloaded with ini file\n"
9.2.11.6
Troubleshooting an Unsuccessful Loading of a License Key

If the Syslog server indicates that a Software Upgrade Key file was unsuccessfully
loaded (the SN_ line is blank), take the following preliminary actions to troubleshoot
the issue:
9.2.11.7
Open the Software Upgrade Key file and verify that the S/N line of the specific
Mediant 3000 whose key you want to update is listed in it. If it isnt, contact
AudioCodes.
Verify that youve loaded the correct file and that you havent loaded the Mediant
3000s ini file or the CPT ini file by mistake. Open the file and ensure that the first
line is [LicenseKeys].
Verify that you did not alter in any way the contents of the file.
Abort Procedure
Reload the key you backed-up in ''Backing up the Current Software Upgrade Key'' on
page 273 to restore your device capabilities to what they originally. To load the
backed-up key use the procedure described in ''Loading the Software Upgrade Key''.
9.2.12
Save Configuration
The Save Configuration screen allows users to save the current parameter
configuration and the loaded files to the Mediant 3000's non-volatile (flash) memory.
Note: If you perform a reset with the Burn option selected immediately after
making the changes to the configuration, there is no need to use the Save
Configuration function prior to the reset.
User's Manual
276
User's Manual
To use the Save Configuration screen, take these 2 steps:

1.
From the main menu list on the left, click on the Save Configuration link. The
Save Configuration screen is displayed.
Figure 9-76: Save Configuration Dialog Screen
2.
9.2.13
Click the Save Configuration button. The new/modified configuration and any
HTTP loaded files are saved to the non-volatile (flash) memory on the device. A
message informing you that it has been saved appears.
Reset Button
The Reset link in the main menu on the left allows the user to initiate a device reset
following which the device utilizes the new configuration stored in the non-volatile
(flash) memory.
To use the Reset Button screen, take these 4 steps:

1.
From the main menu list on the left, click on the Reset button. The Reset screen
is displayed.
Figure 9-77: Reset Screen
2.
Select either of the following Burn options:
Version 4.8
Burn - (Default setting) burns the current configuration to non-volatile (flash)

277
January 2006
Mediant 3000
prior to reset
3.
4.
Dont Burn - Resets the device without first burning the current configuration
to non-volatile (discards all modifications to the configuration that were not
saved to non-volatile memory)
Select either of the following Graceful Shutdown options:
Yes - a timer configuration input field appears - Reset starts only after the
timer expires or no more active traffic exists (the earliest thereof)
No - immediate reset, any existing traffic is terminated at once
Click the Restart Button. If Graceful shutdown was selected, the reset is delayed
and a screen displaying the number of remaining calls and the timer count is
displayed. If Graceful shutdown was not selected the reset starts immediately.
When the reset initiates, If the Burn option is selected, all of the changes made to
the configuration are saved to the non-volatile memory of the device. If the
Dont Burn option is selected, all of the changes made to the configuration are
discarded. The device is shut down and re-activated. A message about the
waiting period is displayed. The screen is refreshed.
9.2.14
Mediant 3000 High Availability Mode
9.2.15
During the time when the Active board synchronizes the Redundant boards
configuration (while the Active and Redundant boards are inter-connected), all
configuration changes are blocked until the system is moved to high availability
mode, (examples of blocked actions are setting board parameters and uploading
files) The duration of this blocked state is up to several minutes.
For Feature key updating, uploading the Feature key file must include the
Feature key for both boards. If the redundant board Feature key is missing or
invalid the system is moved to mismatch configuration mode alerted by SNMP.
Restoring and Backing Up the Device Configuration

The 'Configuration File' screen enables you to restore (load a new ini file to the
device) or to back up (make a copy of the ini file and store it in a directory on your PC)
the current configuration the device is using.
Back up your configuration if you want to protect your devices programming. The
backup ini file includes only those parameters that were modified and contain other
than default values.
Restore your configuration if the device has been replaced or has lost its programming
information, you can restore the devices configuration from a previous backup or from
a newly created ini file. To restore the devices configuration from a previous backup
you must have a backup of the devices information stored on your PC.
To restore or back up the ini file, take this step:
Open the Configuration File screen (Advanced Configuration menu >

Configuration File). The Configuration File screen is displayed. (Refer to
''Configuration File'' on page 242.)
To back up the ini file take these 4 steps:

1.
User's Manual
Click the Get INI FILE button; the 'File Download' dialog opens.
278
User's Manual
2.
Click the Save button. The 'Save As' dialog opens.
3.
Navigate to the folder where you want to save the ini file.
4.
Click the Save button. The VoIP gateway copies the ini file into the folder you
selected.
To restore the ini file take these 4 steps:
Version 4.8
1.
Click the Browse button.
2.
Navigate to the folder that contains the ini file you want to load.
3.
Click the file and click the Open button. The name and path of the file appear in
the field beside the Browse button.
4.
Click the Send ini File button, and click OK in the prompt. The gateway is
automatically reset (from the cmp version stored on the flash memory).
279
January 2006
User's Manual
10. Diagnostics & Troubleshooting
10
Diagnostics & Troubleshooting
10.1
Syslog
The Syslog server (refer to the figure below) enables filtering of messages according
to priority, IP sender address, time, date, etc. Customers can alternatively choose to
download and use the following examples of the many Syslog servers available as
shareware on the Internet:
Kiwi Enterprises: http://www.kiwi-enterprises.com/software_downloads.htm
The US CMS Server: http://uscms.fnal.gov/hanlon/uscms_server/
TriAction Software: http://www.triaction.nl/Products/SyslogDaemon.asp
Netal SL4NT 2.1 Syslog Daemon: http://www.netal.com
Figure 10-1: Syslog Server Main Settings Screen
Syslog protocol is an event notification protocol that allows a device to send event
notification messages across IP networks to event message collectors - also known as
Syslog servers. Syslog protocol is defined in the IETF RFC 3164 standard.
Since each process, application and operating system was written independently,
there is little uniformity to Syslog messages. For this reason, no assumption is made
on the contents of the messages other than the minimum requirements of its priority.
Version 4.8
281
January 2006
Mediant 3000
Syslog uses User Datagram Protocol (UDP) as its underlying transport layer
mechanism. The UDP port that has been assigned to Syslog is 514.
The Syslog message is transmitted as an ASCII message. The message starts with a
leading "<" ('less-than' character), followed by a number, which is followed by a ">"
('greater-than' character). This is optionally followed by a single ASCII space.
The number described above is known as the Priority and represents both the Facility
and Severity as described below. The Priority number consists of one, two, or three
decimal integers.
Example:
<37> Oct 11 16:00:15 mymachine su: 'su root' failed for lonvick on /dev/pts/8
10.1.1
Operating the Syslog Server
10.1.1.1
Sending the Syslog Messages

The Syslog client, embedded in the firmware of the device, sends error reports/events
generated by the device application to a Syslog server, using IP/UDP protocol.
There are presently five error levels reported by the Syslog client:
Emergency level message:
<128>sctp socket setsockopt error 0xf0
Warning level message
<132>Release contains no h.225 Reason neither q.931 Cause information

stateMode:1;
Notice level message:
<133>(
lgr_flow)(2546
) |
#0:ON_HOOK_EV
Info level message:
<134>document http://ab.pisem.net/RadAAIP.txt was not found in documents table
Debug level message:
<135>SCTP port 2905 was initialized
10.1.1.2
Setting the Syslog Server IP Address

To set the address of the Syslog server:
Use the Embedded Web Server GUI (Advanced Configuration>Network Settings

screen - section Logging Settings). (Refer to ''Embedded Web Server'' on page
202 and to the figure below)
Figure 10-2: Setting the Syslog Server IP Address
User's Manual
282
User's Manual
10.1.1.3
Alternately, use the Embedded Web Server GUI or the BootP/TFTP Server to
send the ini configuration file containing the address parameter SyslogServerIP
to the device. Before sending the ini file to the device, specify the address
parameter. For detailed information on the BootP/TFTP Server, refer to the
Appendix, ''BootP/TFTP Server'' on page 307. For an ini file example showing
this parameter, refer to ''Setting Syslog Server IP Address, Enabling Syslog, in an
' on page 283ini 'File'' on page 283 and to the Example of Setting Syslog Server
IP Address, Enabling Syslog, in an ini File below.
Activating the Syslog Client

To activate the Syslog client:
10.1.1.4
Use the Embedded Web Server GUI (Advanced Configuration>Network Settings

screen - section Logging Settings). (Refer to ''Accessing the Embedded Web
Server'' on page 206 and to the figure above.
Alternately, use the Embedded Web Server GUI or the BootP/TFTP Server to
send the ini configuration file containing the parameter EnableSyslog to the
device. For detailed information on the BootP/TFTP Server, refer to the Appendix,
''BootP/TFTP Server'' on page 307. For an ini file example showing this
parameter, refer to ''Setting Syslog Server IP Address, Enabling Syslog, in an '
on page 283ini 'File'' on page 283 and to the Example of Setting Syslog Server
IP Address, Enabling Syslog, in an ini File below.
Setting Syslog Server IP Address, Enabling Syslog, in an ini File

The example below shows an ini file section with an example configuration for the
address parameter SyslogServerIP and an example configuration for the client
activation parameter EnableSyslog.
[Syslog]
SyslogServerIP=10.2.0.136
EnableSyslog =1
10.2
The Embedded Web Server's 'Message Log'

(Integral Syslog)
The Message Log screen in the Embedded Web Server GUI, similar to a Syslog
server only integral to the web server, displays debug messages useful for debugging.
For detailed information, refer to ''Message Log'' on page 263. The Message Log
screen is not recommended for logging of errors and warnings because errors can
appear over a prolonged period of time, e.g., a device can display an error after
running for a week, and it is not recommended to prolong a 'Message Log' session.
For logging of errors and warnings, refer to ''Syslog'' on page 281.
10.3
Changing the Network Parameters via CLI

The Command Line Interface (CLI) is available on Telnet and RS-232 for configuring
network parameters.
Version 4.8
283
January 2006
Mediant 3000
10.3.1
Assigning an IP Address Using the Command Line Interface

(CLI)
To assign an IP address using the CLI, take these 7 steps:
1.
Enable the Embedded Telnet Server:
Access the Mediant 2000 Embedded Web Server (refer to Section 3.3 on
page 19).
Set the parameter Embedded Telnet Server (under Advanced Configuration

> Network Settings > Application Settings) to Enable (Unsecured).
Click the Reset Device button on the main menu bar; the Reset screen is
displayed.
Click the Reset button in the middle of the Reset screen with the Burn option
selected; the Mediant 2000 is shut down and re-activated. A message about
the waiting period is displayed. The screen is refreshed.
2.
Use a standard Telnet application to connect to the Mediant 2000 Embedded

Telnet Server.
3.
Login using the username (Admin) and password (Admin).
4.
At the prompt type conf and press enter; the configuration folder is accessed.
5.
To check the current network parameters, at the prompt, type GCP IP and press
enter; the current network settings are displayed.
6.
Change the network settings by typing: SCP IP [ip_address] [subnet_mask]

[default_gateway] (e.g., SCP IP 10.13.77.7 255.255.0.0 10.13.0.1); the new
settings take effect on-the-fly. Connectivity is active at the new IP address.
Note: This command requires you to enter all three network parameters (each
separated by a space).
7.
10.4
To save the configuration, at the prompt, type SAR and press enter; the Mediant
2000 restarts with the new network settings.
TP-6310 Self-Test
The TP-6310 self-test capabilities are used to identify faulty hardware components on
startup and during run time.
The TP-6310 features three types of testing modes:
Startup tests (Rapid and Enhanced) These tests have minor impact in real-time.
While the Startup tests are executed, the regular operation of the TP-6310 is
disabled.
User-initiated tests (Detailed) The Detailed test is initiated by the user when the
TP-6310 is offline (isnt used for regular service).
Run-time tests (Periodic) Used for monitoring the TP-6310 during run-time.
Rapid The Rapid test is performed every time the TP-6310 starts up. It is executed
each time the TP-6310 completes its initialization process. This is a short test phase in
User's Manual
284
User's Manual

which the only error detected and reported is failure in initializing hardware
components. If an error is detected, an error message is sent to the Syslog.
Detailed - Used in addition to the Rapid and Enhanced test modes. The test is
performed on startup, when initialization of the TP-6310 is completed and if the
parameter EnableDiagnostics is set to 1 or 2. In this mode, the TP-6310 tests its
DSPs, RAM and flash memory. When EnableDiagnostics is set to 1, flash is tested
thoroughly. When EnableDiagnostics is set to 2, flash is only partially tested.
When the test terminates the test results are reported via the event EV_END_BIT.
Periodic The Periodic Test is performed every hour after startup, even when there
is full traffic on the TP-6310; quality is not degraded. The following additional tests are
performed on the redundant board:
ATM ports
Voice path
When the test terminates the test results are reported via the event
EV_ENHANCED_BIT_STATUS. In addition, if an error is detected, an error message
is sent to the Syslog.
10.5
Control Protocol Reports
10.5.1
TPNCP Error Report

When working with the AudioCodes proprietary TPNCP (TrunkPack Network Control
Protocol), the TP-6310 reports all events using a TPNCP log event report mechanism
(using error/debug events), through the network interface. For a list of events, refer to
the section, Board Originated Error Codes, in the VoPLib API Reference Manual,
Document #: LTRT-844xx.
Examples of using the Log Event Report Mechanism are also shown in the VoPLib
API Reference Manual, Document #: LTRT-844xx.
10.5.2
MGCP/MEGACO Error Conditions

When working with MGCP/MEGACO, the device reports error conditions via the Call
Manager (or via a Call Manager of the customers choice) using the standard
MGCP/MEGACO facilities, through the network interface. For more information on
MGCP/MEGACO error conditions, refer to the IETF Website at URL
http://www.ietf.org/rfc/ and refer to RFC 3435/3661 for MGCP and RFC 3015 for
MEGACO.
10.5.3
SNMP Traps
TP-6310 boards support various SNMP traps via the SNMP Agent running on the
board. Among these traps are Trunk MIB traps, acBoardStarted and acResetingBoard
traps. ' Refer to U' on page 183sing SNMP for more details on all SNMP traps
available on the board.
Version 4.8
285
January 2006
Mediant 3000
10.6
Solutions to Possible Problems
10.6.1
Possible Common Problems

Solutions to possible common problems are described in the table below.
Table 10-1: Solutions to Possible Common Problems

Problem
Possible Cause
Solutions
No
communicati
on
Software does not

function in the device
Try to ping the board/module. If ping fails, check for

network problems/definitions and try to reset the
board/module
Network problem
Check the cables.
Network definitions
Check if the default gateway can reach the IP of the

board/module.
Check if the board/module got the correct IP.
Check the validity of the IP address, subnet and default
gateway.
If the default gateway is not used, enter 0.0.0.0
BootP did not reply to

the board/module
Check if the BootP server replied to the board/module at

restart by viewing the log of the BootP server.
Try to restart the BootP server.
Check the MAC address of the board/module in the
BootP server.
ini file was

not loaded
User's Manual
TFTP server down
Check if the TFTP server is working.
TFTP server didnt

get the request
Check the log of the TFTP server.
TP-6310 didnt
request the file from
your TFTP
Check that the TFTP servers IP address is the one that

the TP-6310 is trying to use by viewing the Syslog.
TFTP server bug
Try to restart the TFTP server.
BootP sent to a board

with the wrong TFTP
server address
Check the IP address of the TFTP server being used.
ini file does not exists

in the default
directory of the TFTP
server
Check the default directory of the TFTP server and

check that the ini file exists there.
286
User's Manual
Table 10-1: Solutions to Possible Common Problems

Problem
Possible Cause
Solutions
Wrong ini file name
Verify in Windows Explorer that file extensions are

displayed and the ini file is not XXX.ini.ini by mistake.
Also verify that the extension ini is in lowercase letters.
TFTP servers
timeout is too short
Verify that the TFTP server settings are as follows:

Timeout = 2 sec,
# of retransmission = 10
Wrong ini file

loaded
BootP reply
from wrong
BootP server
10.6.2
ini file is not in the

correct position
An old ini file was probably loaded. Check which ini file
was loaded by using the Syslog server. The Gateway
displays contents of ini file before it began.
ini file corrupted
Check the ini file syntax
Other BootP servers

contain the MAC
address of the
board/module
Check that only your BootP server contains the TP6310s MAC address.
Possible Voice Problems

Solutions to possible voice problems are described in the table below.
Table 10-2: Solutions to Possible Voice Problems

Problem
Possible Cause
Solutions
G.711 voice
quality is bad
(clicks)
Silence compression is
not compatible (when
working with different
Gateway other than
AudioCodes Gateway)
Disable it and check if the quality is better.
The Packet size is not

compatible (with G.711)
Check that the packet period in the remote side

is 20 msec.
Check that the correct -law or A-law
compression is in use
No voice
Version 4.8
There is no match in the

codecs
Change the codec definition.
287
January 2006
Mediant 3000
10.6.3
User Error Messages

Table 10-3: User Error Messages
Error Message Text
Possible Cause
Recommended Action
Answer Detector has been

enabled due to incompatible
barge-in settings'
Speech Barge-in on playback

was requested while Answer
Detector was not activated
Activate the Answer Detector

on Open Channel command.
Answer Detector direction has

been changed to IP due to
incompatible barge-in settings'

was requested with wrong
Answer Detector direction
setting (TDM instead of IP)
Set the Answer Detector

direction in the Open Channel
Command to detect from IP
side.
Answer Detector direction has

been changed to TDM due to
incompatible barge-in settings'

was requested with wrong
Answer Detector direction
setting (IP instead of TDM)
Set the Answer Detector

direction in the Open Channel
Command to detect from TDM
side.
"IBS Detection direction has

been changed to IP, due to
incompatible barge-in
settings'"
DTMF Barge-in on playback

was requested with wrong IBS
Detection direction setting
(TDM instead of IP)
Set the IBS detection direction

in the Open Channel
Command to detect from IP
side.
"IBS Detection direction has

been changed to TDM, due to
incompatible barge-in
settings'"
DTMF Barge-in on playback

was requested with wrong IBS
Detection direction setting (IP
instead of TDM)
Set the IBS detection direction

in the Open Channel
Command to detect from TDM
side.
DigitOnTime must be >= -1.

Channel ID:%d '
Dial command was called with

a <-1 DigitOnTime value.
Set the DigitOnTime to a >=-1

value.
Channel %d is being idled

while user is dialing (%d).'
Channel was closed in the

middle of a signal playback
(E.g. Dial command)
Stop all signals before closing

the channel
ByPass Coder forced to

g711alaw'
Fax/Modem Bypass coder

was set to a LBR coder.
Set the Fax/Modem bypass

coder to a HBR coder (E.g.
G711 Alaw).
Invalid call progress tone

index=%d '
Trying to play a Call Progress

Tone using an invalid index
"Make sure that when playing

a tone by index, that this index
is valid & exists in the Call
Prgoress Tones configuration
file"
CNG Detector Mode forced to

Event Mode'
Fax CNG Detector was set to

Relay while Fax/Modem
detectos were set to Events
Only or Bypass.
Set the Fax CNG Detector to

Events Only
CNG Detector Mode forced to

Disable Mode'
Fax CNG Detector was not set

to Transparent while
Fax/Modem detectos were set
to Transparent.
Set the Fax CNG Detector to

Transparent
Modem Relay Is Not

Supported! Forcing Bypass
Modem detectors were set to

Relay
"Set the Modem Detectors to

Bypass, or Events Only."
User's Manual
288
User's Manual

Error Message Text
Possible Cause
Recommended Action
'Bell Modem May Corrupt

Trunk Testing Operation Disabling the Bell Modem
Detection.'
Bell Modem was activated

while Trunk Testing tones
were activated. This cannot be
done since the detectors
colide.
"Set the Bell Modem the

Transpranet if Trunk Testing is
required, or set the Trunk
Testing detection to disable if
Bell Modem detection is
required."
Invalid CPT index (%d).

Channel ID:%d '
Trying to play a Call

Progeress Tone using an
invalid index

a tone by index, that this index
is valid & exist at the Call
Prgoress Tones configuration
file"
Invalid Tone Type (%d).

Channel ID:%d '
Trying to play a Tone using an

invalid Tone Type

a tone by type, that this type is
valid & exist at the Call
Prgoress & User Defined
Tones configuration file"
Wrong Voice Prompt Coder:

%d. Channel ID:%d '
Trying to play a Voice Prompt

with a Coder that is not valid
Make sure that the Voice

Prompt coder is G711 or
Linear PCM when playing to
IP. Make sure that the Voice
Prompt coder is G711 or
Linear PCM or the Channel's
coder when playing to TDM.
MEDIATION WARNING:
Trying to open two
transcoding channels both
with DSP resource. Channel
ID %d will be opened with no
DSP resource.\n '
Trying to make a transcoding

session with 2 DSP resources.
Transcoding action can be
done only with 1 DSP
resource.
Make sure that when

Transcoding is required in the
Open Channel that a DSP
resource is requested on only
the LBR channel.
MEDIATION WARNING:
Trying to open a channel for
network to network mediation
with a DSP resource. Channel
ID %d will be opened with no
DSP resource.\n '
Requesting for DSP allocation

while Network to Network
mediation was requested
"When making a Network to

Network medation, make sure
that the DSP allocation
parameter is in Disable state."
No DSPs detected.'
Software could not find any

DSP on board
Replace hardware
Too many (%d) call progress

signals'
Number of Call Progress

tones downloaded to the
board is too high
Make sure that the total

number of tones downloaded
does not exceed 32
Too many user defined

signals. Not all signals can be
inserted.'
Number of User Defined tones

downloaded to the board is
too high

does not exceed 32
SetupLogicalChannel: Coder
number %d is not supported
by channel %d. Changed to
Trying to Open a Channel with

a non supported Coder
Make sure that the Coder

being used when openning the
channel is valid according the
Mode'
Version 4.8
289
January 2006
Mediant 3000

Error Message Text
Possible Cause
g711alaw.'
Recommended Action
the DSP template
configuration
Invalid configuration of
channel detectors.\n'
IBS detectors were set

incorrectly
RTPRedundancyDepth is out
of range. The maximum
allowed value will be set.'
Trying to set RTP redundancy

depth to a value >1
In current version RTP

Redundancy supports only
redundancy depth of 1.
Cypher (%d) is not supported.

The corrected value will be
set.'
Trying to activate the

encryption on a not supporting
product.
Check with AudioCodes

representative for encryption
supporting products.
SCE cannot be used with this

coder. The corrected value will
be set.'
Trying to activated Silence

Compression on coders that
do not support Silence
Compression.
VoxADPCM & MSGSM coders

do not support Silence
Compression. Change Coder
or disable the Silence
Compression.
EC length (%d) is too large

(cannot exceed %d). The
corrected value will be set.'
Trying to set the Echo

Cancellation Tail length to a
value above the maximum
alowed
Set the Echo to Echo

Canceller Length to a value
equal or lower than the
Maximum EC Length board
parameter.
BrokenConnectionEventTimeo
ut re-set to maximum allowed.
Channel ID: %d'
RTP Broken Connection Time

out cannot exceed
0x80000000/0x320
Set to a value less than

0x80000000/0x320
BrokenConnectionEventTimeo
ut re-set to minimum allowed.
Channel ID: %d'
RTP Broken Connection Time

out cannot be less than 3.
Set to a value greater than 3.
Invalid TxM (%d) - correction

will be performed (%d).'
The number of requested

voice frames inside one RTP
packet is too high.
The M factor parameter

cannot exceed 12.
Media Security cannot work

with TxM > 1. Correction to
TxM=1 will be performed.'
Encryption does not support

more than 1 voice frame per
RTP packet
Do not change the M factor

channel parameter from 1
when using encryption
Invalid FaxBypassM. The

corrected value will be set.'
The number of requested

voice frames inside one RTP
packet during Fax/Modem
Bypass session is too high.
the Fax/Modem Bypass M

factor channel parameter
cannot exceed 12.
Invalid
EnhancedFaxRedundancyDep
th value (%d). Correction will
be performed to %d.'
The requested depth of the

Fax Relay enhanced
redundancy is too high
The enhanced Fax Relay

redundancy depth cannot
exceed 4
input
FaxRedundancyDepth>%d.
The corrected value will be
set.'
The requested depth of the

Fax Relay high speed
redundancy is too high
The Fax Relay redundancy

depth cannot exceed 2.
Changing Maximum Fax Rate

to %d due to buffer size
Maximum Fax rate was

configured above a valid
Lower the fax redundancy

depth or lower the maximum
User's Manual
290
User's Manual

Error Message Text
Possible Cause
Recommended Action
limitations.'
buffer size
fax rate.
Selected DSP Version

Template (#%d) is not
available. Changing to 0.\n'
Configuring a non valid DSP

template
DSP templates can only be

set as specified in the
products release notes.
Error in DSP Version

Template %d for device %d.'
Configuring a non valid DSP

template
DSP templates can only be

set as specified in the
products release notes.
RTP Payload type (RFC2833

Tx) %d is out of range.
Channel %d. Changed to
default(%d). '
RFC 2833 RTP Payload Type

was set out of the RTP
Payload Type dynamic range
Set the Payload Type to a

value between 96 to 127.
RTP Payload type (RFC2833

Rx) %d is out of range.
default(%d).'


RTP Payload type (RFC2198)

%d is out of range. Channel
%d. Changed to Default(%d). '


RTP Fax ByPass Payload

type %d is out of range.
default(%d). '
VBD (Bypass) RTP Payload

Type was set out of the RTP

RTP Modem ByPass Payload

type %d is out of range.
default(%d) '
VBD (Bypass) RTP Payload

Type was set out of the RTP

NSE Dynamic Payload type

%d. Changed to default(%d). '
NSE RTP Payload Type was

set out of the RTP Payload
Type dynamic range

NOOP time interval %d is out

of range. Channel %d.
Changed to default(%d). '
The configuration of the

imterval between 2
consecutive No-Op packets is
below a minimum alowed
Set the No-Op interval

parameter to be above 20.
NOOP Dynamic Payload type

%d. Changed to default(%d). '
No-Op RTP Payload Type


Too many (%d) User Defined

Tones. Changed to %d.'
Number of User Defined tones

too high

does not exceed 32
Too many User Defined Tone

Frequencies. Only %d could
be loaded'
Number of User Defined

configured total frequencies
too high

number of frequencies
declared in the downloaded
UDT data base does not
exceed 64.
Too many (%d) Call Progress


Version 4.8
291
January 2006
Mediant 3000

Error Message Text
Possible Cause
Recommended Action
signals. Changed to %d.'
board is too high
does not exceed 32
Modulation is not supported.

Only %d signals could be
loaded'
NA
NA
Too many Call Progress

Frequencies. Only %d signals
could be loaded.'

board is too high

does not exceed 32
Trying to dial more than 1 digit

when DigitOnTime = -1.
Channel lD:%d'.
"When DigitOnTime == -1
(play forever), the user cannot
play more than 1 digit"
Use only 1 digit per Dial

command when playback of a
digit forever is required
Cannot play more than %d

tones sequentially. Channel
ID:%d.'
The number of tones input to

the Play Tone sequence
command us too high
The maximum tones that can

be input to the Play Tone
Sequence command is 8.
Cannot play more than %d

tones sequentially.'
The number of tones input to

the Play Tone sequence
command us too high
The maximum tones that can

be input to the Play Tone
Sequence command is 8.
Unexpected CED Signal after

detection of CNG Signal At
State Fax.'
CED was detected after a

CNG detection.
Mostly an Echo problem.

Check that Echo Canceller is
on. Make sure the line Echo
does not more than 6 db
below the original voice
RTP Payload Type is

changed. Old PT=%d New
PT=%d.'
Issued when RTP packet with

worng payload type is being
received
Make sure that the channel is

configured to the correct coder
& RTP Payload Type. Make
sure that no bad/malformed
packets are being sent to this
channel
adTimerExpired:Audio has not

been provisioned - raising
alarm.'
Possible causes for this are

that the gateway was not
provisioned on an APS or that
provisioning for the gateway
on the APS is not enabled.
Recommended actions would

be to determine on the APS
that the gateway is
provisioned correctly and that
it also has provisioning
enabled on the APS.
"The designer employed an

abstraction in terms of
'errorString' to generate a log.
The real text is Segment <n>
not provisioned, where n is
the numeric segment id of an
audio segment that the call
agent tried to play, but doesnt
exist in the onboard audio.
The possible cause is either
that the audio was not
provisioned from the APS or
that it had been provisioned
recently and that the
AMS/gateway was not been
"The recommended action for

this error is to validate on the
APS that the segment has
been provisioned, and if
necessary, to manually
provision fresh audio to the
gateway."
User's Manual
292
User's Manual

Error Message Text
Possible Cause
Recommended Action
reprovisioned."
NTP:doNTPTimerTaskAction:
NTP Server Failed to respond
to previous query. Please
check the IP Address.'
"This can be caused by a bad

value that has been entered or
by a request that interrupts the
normal sequence of the timer
function, such as an SNMP
request for time."
Either check the network

IpAddress or recognize that if
the time between requests
was not fully realized that
someone did a manual
request for the NTP field or
changed the iterations values.
"'%s Bad digit on address

name:
%s',updateErrorPrefix,addrNa
me"
"The rows in the

TargetAddrTable are indexed
with a string of the form:
mgr<digit> or trap<digit>. The
""mgr"" entries are for trusted
managers and the ""trap""
entries are for trap
destinations. The SNMP
configuration software on the
board found a badly formed
index string. This is most likely
the result of the Element
Management System (EMS)
creating a row with the bad
index string."
"Determine why the EMS is

creating rows in the
TargetAddrTable with poorly
formed index strings. As a
workaround, use ini files to
configure trusted managers
and trap destinations until the
problem is fixed."
"Max retries exceeded. DNS

name resolution failed for
%s',fs->hostname.'"
"A remote file system was

configured using a domain
name, instead of an IP
address. The domain name
could not be resolved to an IP
address. The board's DNS
server configuration may not
be correct or there may be a
problem with the DNS server."
Ensure that a DNS server is

configured. Ensure that the
DNS server has an entry for
the domain name of the NFS
server.
" Failure to mount remote NFS

system. %s IP=%s path=%s
state=%s
numRetries=%d',str,AcUdpTra
nsport::getIpStr(fs->ipaddr),fs>getRootPathName(),NfsSmM
ount::stateEnumToStr(fs>mountState),fs->retries' "
There was a failure to mount a

remote NFS file system. This
could be due to an error in the
configuration of the file system
in the board's remote file
system table. It could be
because the NFS server is
down or configured
improperly.
Ensure that the remote NFS

file system is configured
properly on the board. Ensure
that the NFS file server is up
and configured properly.
Ensure that NFS daemons are
running.
"Unable to create new

request, invalid URI."
"An attempt was made to

access a file on a remote file
system that is configured on
the board, but is not
mounted."
Determine why the remote file

system was not mounted.
Look through the syslog for
messages which might give a
reason for the mount failure.
Unable to create new request.

File system not found.
"An attempt was made to

system that is configured on
the board, but is not
Determine why the remote file

system was not mounted.
Look through the syslog for
messages which might give a
Version 4.8
293
January 2006
Mediant 3000

Error Message Text
Unable to create new request.

Resource not available.
Possible Cause
Recommended Action
mounted."
reason for the mount failure.
An attempt was made to

system that is not configured
on the board. This could be
due to an error in the
configuration of the file system
in the board's remote file
system table. Or it could be
due to an error in the URI
provided by the call agent.
Configure the remote file

system on the board. Ensure
that the URI provided by the
call agent in the control
protocol message is correct.
Warning:
TDMBusClockSource is
Internal and Framer is
acCLOCK_MASTER_OFF
(Recover clock). This is not a
stable Clock Source.'
'Warning:
PSTNAutoClockEnable is
relevant only when
Network (your setting is
TDMBusClockSource =
Internal).'
Warning:
TDMBusLocalReference was
set to a negative value and
has been changed to zero.'
Warning:
TDMBusClockSource is set to
Network. At least one trunk
must be
acCLOCK_MASTER_OFF
(recover clock).'
"Note: Trunk number = %d
configuration was changed to
Recover Mode because it was
configured to be
TDMBusLocalReference.',Boa
rdParams.TDMBusLocalRefer
ence"
Error: TDMBusClockSource is
set to Network. All trunks set
to be
acCLOCK_MASTER_ON
(master clock). Can't use other
trunks as recover clock. Set
one trunk to be
acCLOCK_MASTER_OFF.'
User's Manual
294
User's Manual

Error Message Text
Possible Cause
Recommended Action
"Error: When configuring the

board to recover the clock
from
PSTNTDMBusLocalReference
, the trunk must be active.
Trunk Number =
%d.',BoardParams.TDMBusLo
calReference"
Warning: The Framer clock is
set to
acCLOCK_MASTER_OFF
(recover clock). This might be
problematic in case the trunk
gets the clock from a different
clock source.'
"Warning:
PSTNAutoClockEnable is
relevant only when recovering
the clock from PSTN and
%d.',BoardParams.TDMBusCl
ockSource'"
Warning - No such TDM bus
clock source.'
PSTN Trunk Validation Check
Warning TDMBusClockSource is
Internal and Framer is
acCLOCK_MASTER_OFF
(Recover clock). This is not a
stable clock source.'
Warning PSTNAutoClockEnable is
relevant only when
Network (your setting is
TDMBusClockSource =
Internal).'
Warning TDMBusClockSource is set to
Network. At least one trunk
must be
acCLOCK_MASTER_OFF
(recover clock).'
Warning - The Framer clock is
acCLOCK_MASTER_OFF
Version 4.8
295
January 2006
Mediant 3000

Error Message Text
Possible Cause
Recommended Action
(recover clock). This might be

problematic in case the trunk
gets the clock from a different
clock source.'
"PSTN Trunk Validation
Check Warning PSTNAutoClockEnable is
relevant only when Recover
clock from PSTN and
%d.',ImageBoardParams.TDM
BusClockSource"
Warning - no such TDM bus
clock source.'
Warning: ISDN is Network
side and you have requested
clock from the PSTN Network.'
"'acl_iua_config() - duplicate
Int_id =%d,on Trunk =
%d.',ImageBoardParams.Ext.I
UATrunkConfig[TrunkId].IuaInt
erfaceId,TrunkId"
"'acl_dua_config() - duplicate
Int_id =%d,on Trunk =
%d.',ImageBoardParams.Ext.I
UATrunkConfig[TrunkId].IuaInt
erfaceId,TrunkId"
Framing method is not
supported in Temux.'
Framing method is not
supported in Ultra mapper.'
IsdnValidation - Cannot add
another variant - configuration
failed. Reached maximum
ISDN variants number.'
"PSTN Validation Check failed
- In TP2810 board, the Line
Type must be T1 for Trunk
number = %d.',i"
"PSTN Validation Check failed
- Line Type must be E1 or T1
for Trunk number = %d.
Please change the protocol
type.',i"
PSTN Validation Check failed.
User's Manual
296
User's Manual

Error Message Text
Possible Cause
Recommended Action
Internal and all trunks

ClockMaster are
acCLOCK_MASTER_OFF.
Change the
TDMBusClockSource to
Network or ClockMaster to
acCLOCK_MASTER_ON.'
"PSTN Validation Check
failed.
TDMBusLocalReference is
configured to be trunk number
= %d and the trunk isn't
configured to be Recover
Mode.',ImageBoardParams.T
DMBusLocalReference"
Network but all trunks are set
to acCLOCK_MASTER_ON
(master clock). Can't use other
trunks as recover clock. Set
one trunk to be
acCLOCK_MASTER_OFF.'
"PSTN Validation Check
failed. When configuring the
from
, the trunk must be active
(protocol type should not be
set to NONE).'"
PSTN Validation Check failed
- V5 Configuration Error.'
All trunks configured with
protocol type NONE.
Reconfigure the trunks and
reset the board.'
"'acPSTNVCValidationCheck()
- Vc Id (%d) is not in range (0%d).',VcId,(MaxTrunkNum-1)"
"'acPSTNVcVsTrkValidationC
heck() - Driver is not
ready.',TrkId,(MaxTrunkNum1)"
heck() - Trunk Id (%d) is not in
range (0 -
Version 4.8
297
January 2006
Mediant 3000

Error Message Text
Possible Cause
Recommended Action
%d).',TrkId,(MaxTrunkNum-1)"
heck() - VC is not as Trunk
Line Type - VC: %d Trk:
%d.',VcId,TrkId"
failed because of on-the-fly
changes is not supported on
this HW.'
failed. Protocol type must be
different from
acPROTOCOL_TYPE_NONE.
'
failed. Line Type is E1 or
trying to configure non-T1
protocol. TP2810 supports
only T1.'
failed. Protocol type must be
the same line type (E1\T1). Do
not mix line types.'
failed. Protocol family
configuration error
(E1_transparent_31 can not
be configured with any other
E1 protocol type).'
Check failed. Framing method
%x is not valid (Line type is
T1)
',pTrunkConfig[TrunkId].Frami
ngMethod"
Check failed. Framing method
%x is not valid (Line type is
E1)
',pTrunkConfig[TrunkId].Frami
ngMethod"
"'Warning: Line Code does not
fit T1 Line Type. Line Code is
:%x. B8ZS will be used as
default',pTrunkConfig[TrunkId]
.LineCode"
failed. The ISDN configuration
User's Manual
298
User's Manual

Error Message Text
Possible Cause
Recommended Action
is incompatible with this

Ram.hex (it should be
compiled differently).'
failed due to configuration of
CAS protocol with wrong HW
or ini file parameter CASProtocolEnable disabled.'
failed due to wrong
CASTableIndex parameter
configuration.'
Check failed. Missing CAS
table at
TableIndex=%d.',pTrunkConfi
g[TrunkId].CASTableIndex"
Check failed. When
configuring CAS trunk, close
all chanells relevant to this
trunk. Channel ID = %d',CID"
failed. Insufficient DSP
resource when configuring
CAS trunk.'
PSTNValidationCheck():
Trying to change ISDN->CAS.
Insufficient DSP resources.
Use Apply with
acPROTOCOL_TYPE_NONE
followed by Apply with the
wanted protocol.'
CheckThatAllProtocolsAreCo
mpatabile(): TR08
configuration failed. Check the
syslog for more information.'
"ProtocolType not valid for
TrunkId : %d. ProtocolType
changed to
acPROTOCOL_TYPE_NONE.
',i"
CheckThatAllProtocolsAreCo
mpatabile(): Illegal mix of
ProtocolTypes for Trunks.'
"'Action Failed IUACheckfForDoubleInterfaceI
Version 4.8
299
January 2006
Mediant 3000

Error Message Text
Possible Cause
Recommended Action
d - duplicate Int_id
=%d.',ImageBoardParams.Ext
.IUATrunkConfig[TrunkId].IuaI
nterfaceId"
"Error: When configuring the
from
, the trunk must be active.
Trunk number =
%d.',BoardParams.TDMBusLo
calReference"
"CheckProtocolTypeValidation
() - For trunks configured with
protocol type NONE,
reconfigure the trunks and
reset the board.'"
It is illegal to set all trunks with
protocol type NONE.'
'InitializeAllFramesForNonePr
otocols() - Invalid Line type
(should be E1 or T1)'
'PSTNInterruptAudit(): HW
interrupt is stuck for too long.'
'MaxTrunkNum exceeds
MAX_TRUNK_CAPACITY.'
Configure To Work for AMS
only. Do not use
TRUNKs.TdmBusType
defined as FRAMERS but no
TRUNKs found.'
'TdmBusType defined as
FRAMERS but no TRUNKs
found.'
User's Manual
300
User's Manual
11. Functional Specifications
11
Technical Specifications
11.1
Mediant 3000 Selected Specifications

Table 11-1: Mediant 3000 Selected Specifications
Item
Characteristic
Channel Capacity
Network Ports/DSP Calls
Up to 2016 simultaneous calls
(independent digital voice, fax or

data ports)
All media processing ports can be tied to ATM-AAL2, AAL2, IPRTP, PSTN-DS0
Wireline ,Wireless with UMTS: Up to 2,016 Low Bit Rate Voice
channels
Wireless with CDMA: Up to 1,764 Low Bit Rate Voice channels
Note: When using some coders channel capacity may be
reduced for specific functions.
DSP Channel Configuration

Options
480, 1008, 2016 Universal ports
Voice Messaging
HTTP Streaming
Playback (streaming via HTTP) of raw or wav G.711 files stored

on a remote Web server.
Playback from Local Storage
Prompts and announcements playback (32 MB integral memory

of G.711 recorded prompts)
Remote NFS file system access
Remote NFS file system access based upon NFS version 2

(RFC1094) or version 3 (RFC1813) standards for audio
playback and recording of raw, wav, or au files stored on a
remote NFS file system server
Media Processing
IP Transport
VoIP (RTP/ RTCP) per IETF RFC 3550 and RFC 3551
DTMF/MF Transport
DTMF/MF RTP Relay per RFC-2833, Mute, Transparent

(transfer in coder as voice).
Version 4.8
301
January 2006
Mediant 3000

Item
Characteristic
Enhanced Services
Announcement playback - Advanced audio package per H.248.9

and PacketCableBAU package (Future implementation)
Voice recording/playback (Future implementation)
Local announcement storage
Trunk testing per GR-822, tests: TL 100,102 and 105,
Multiple Vocoder Transcoding
Limited Conferencing for 3-way parties
Voice Coders
Voice Compression
(Independent dynamic vocoder
selection per channel)
Wireline: G.711, PCM, 64 kbps (m-law/A-law)

G.723.1 MP-MLQ, 6.3 kbps ACELP, 5.3 kbps
G.729A CS-ACELP, 8.0 kbps
Wireless-UMTS: GSM-FR, GSM-EFR and AMR (all rates)
Wireless-CDMA: EVRC
Software
Echo Cancellation
G.165 and G.168 2000 with 32, 64 or 128 msec tail length
(128 may reduce channel density)
Fax Modem Relay/ByPass
T.38 (IP) compliant Group 3 fax relay and Fax-bypass (switch to

G.711) support
Modem Bypass (incl.V.90)
In-band/Out-of-band Signaling
Packet side, DTMF and tone detection and generation
DTMF & Tone Signaling
DTMF detection and generation per TIA 464B

MF-R1, MFC-R2, detection and generation
Call progress Tone detection and generation
Gain Control
Programmable
Silence Suppression
Voice Activity Detection (VAD),

Comfort Noise Generation (CNG)
(According to standard coder support)
VoIP Standards Compliance
RTP/RTCP per RFC 3550/3551

DTMF over RTP per RFC 2833
Control Protocols
MGCP (RFC 3435)
Call control, Basic announcements package, Conferencing
MEGACO (H.248)
Call control and R2 package, Basic announcements package,

Conferencing
TPNCP
AudioCodes proprietary TPNCP (Via Ethernet)
User's Manual
302
User's Manual

Item
Characteristic
Management Interfaces
SNMP V2
Standard MIB-2, RTP MIB, Trunk MIB, AudioCodes' proprietary

MIBs
Embedded Web Server
Enabling device configuration and run-time monitoring with an

Internet browser
Syslog
Supported by SysLog servers
Signaling
SS7
MTP-2 and MTP-3 (ITU/ANSI/China) link termination
SigTran
IUA (RFC 3057) over SCTP (RFC 2960)

M2UA, (RFC 3331) over SCTP (RFC 2960)
transferring MTP-2 payload
High Availability
1+1 system setup
System is occupied with 2 boards, one is active in working mode

and the other is redundant in stand by mode
Processor
Control Processor
Motorola PowerQUICC 8280
Control Processor Memory
480 channels: SDRAM - 256 MB

2016 channels: SDRAM - 512 MB
Signal Processors
AudioCodes AC491 VoIP DSP @ 300 mHz
Interfaces
Gigabit Ethernet (GbE)
1+1 redundant 10/100/1000 Base-TX ports ports

Interface options:
10/100/1000 Base-TX: RJ-45 Connector Interface (CAT5
Twisted pair)
Or
10/100/1000 Based-RX: 1.25 Gbps optical SFP modules - Hot
Swappable
OC-3/STM-1 PSTN
1+1 APS Redundancy

155.54 Mbps optical SFP modules; Hot Swappable
OC-3c/STM-1c ATM
1+1 Redundant
OC-3c optical replaceable LC Connector (ATM AAL1/2/5)
155 Mbps optical SFP modules; Hot Swappable
Physical
Version 4.8
303
January 2006
Mediant 3000

Item
Characteristic
Supply Voltages and Power

Consumption (typical)
5 A @ -48 VDC
Environmental
Humidity: 10 to 90% non-condensing
Hot Swap
Full cPCI hot swap supported for media processing boards

according to PICMG 2.1
250 watts
Redundant Power Supplies provide protection but are non Hot

Swappable
Host Interface
Via Packet interface using AudioCodes proprietary TPNCP or

standard control protocols
Enclosure Dimensions
2U high, 19-inch wide rack mount, shelf or desk top, 4-slot cPCI
chassis
8.8 x 48.26 x 29.68 cm ; 3.5 x19 x 11.87 inch (h x w x d)
including mounting brackets
cPCI chassis PICMG 2,0 R2.1 cPCI
2 middle mounting brackets - Optional
Weight
Total including packaging 12.2 KG; 5.6 lbs.
Connectors and Switches

Rear Panel
Power: (model dependent)

- DC power - MSTB2.5/2-STF (5.08mm) Phoenix Contact
Cable connection mate: PC4/2-STF-7,62 (AudioCodes
supplied)
BITS/SETS: RJ-48connector or optical 1.25 Gbps SFP module
Connection mate: FK-MC 0.5/8-ST-2,5 Phoenix Contact
(AudioCodes supplied)
ESD connectors
Front Panel
Hardware Reset button - on 6310 board

Alarm Cut-off button - on Fan Module (future implementation)
ESD connectors
Fiber Optic Cable

ATM and PSTN (SDH) - Singlemode Fiber
Input Sensitivity: -32 dBm typical; -28 dBm maximum
LAN (GbE) - Multi-mode
Input Sensitivity: -29 dBm typical; -17 dBm maximum
Output Power: -15 dBm minimum; -8 dBm maximum

Output Power: -9.5 dBm minimum; -2 dBm maximum
Diagnostics
Front panel LEDs
User's Manual
Provide visual status indications and alarms - on PEMs, 6310

boards, Power Supplies, Fan Tray
304
User's Manual

Item
Characteristic
SysLog events
Supported by SysLog servers
Type Approvals
Telecommunications Standards
FCC part 68, TBR4 and TBR13
Safety and EMC Standards
UL60950, FCC part 15 class Bce mark (EN55022 Class B,

EN60950, EN55024, EN300 386
Environmental
NEBS Level 3 (Designed to meet) GR-63-Core, GR-1089-Core,

Type 1&3,
ETS300 019 (Future Implementation)
Operating Systems
O/S Support
Windows 2000, Windows XP, Windows 2003

Unix Solaris (Sparc or Intel machines)
Linux RedHat (Intel machines)
OS wrapper to support other operating systems
Version 4.8
305
January 2006
User's Manual
12. Appendix - BootP/TFTP Server
12
Appendix - BootP/TFTP Server
12.1
Introduction
The BootP/TFTP Server enables easy configuration and provisioning for AudioCodes
boards and Media Gateways. The BootP and TFTP servers contain specific
adaptations as per manufacturer requirements. The latest version of the BootP/TFTP
application is 2.3.0.5.
12.1.1
12.1.2
Version 4.8
Key Features
Internal BootP server supporting hundreds of entities
Internal TFTP server
Contains all required data for AudioCodes products in predefined format
Provides a TFTP server address, enabling network separation of TFTP and

BootP servers
Tools to backup and restore the local database
Templates
User-defined names for each entity
Option for changing MAC address
Protection against entering faulty information
Remote reset
Unicast BootP respond
User-initiated BootP respond, for remote provisioning over WAN
Filtered display of BootP requests
Location of other BootP servers that contain the same MAC entity
Common log screen for both BootP and TFTP sessions
Display of manufacturer vendor specific information parameters
Support for manufacturer's selective BootP feature (The BootP server inserts
manufacturer specific vendor information that includes the text, AUDC)
Compatible with Windows 98, Windows NT, Windows 2000, WindowsXP
Specifications
BootP standards: RFC 951 and RFC 1542
TFTP standards: RFC 1350 and RFC 906
Operating System: Windows 98, Windows NT and Windows 2000, Windows XP

307
January 2006
Mediant 3000
Maximum number of MAC entries: 200
BootP Fields:
12.1.3
Hardware address (MAC): 12 hex digits
IP address
Subnet
Default Gateway
TFTP server IP (Using the TFTP server IP field enables download of

firmware from a different Host)
Boot File
ini File
Call Agent IP
New MAC (optional)
Screens:
File Upload and Message screen
Preferences screen
Client Configuration screen
Template Definition screen
BootP/TFTP Server Installation

The BootP/TFTP Server can be installed on a PC from the Mediant 3000 Software &
Documentation CD.
To install the BootP/TFTP Server, take these 3 steps:

1.
User's Manual
Unzip the TPxx.exe file and navigate to the BootP zip file under .\Utilities\BootP &
TFTP server.
308
User's Manual
2.
Double click on the BootP zip file and run setup.exe. The installation procedure
begins. After completing the procedure, open Start>Programs>BootP. The
BootP/TFTP Server main screen is displayed.
Figure 12-1: Main Screen
The figure above shows the main screen of the BootP/TFTP Server, featuring:
Program State - Pauses the program. When the program is paused, no

replies to BootP requests are sent.
View Clients button - Opens up the Clients Configuration screen.
View Templates button - Opens up the Templates Configuration screen.
Clear Log button - Clears the log.
Filter Unknown Clients button - Filters all BootP requests that are not
listed in the Client Configuration screen.
Reset button - Opens a dialog, in which users can enter an IP of a client.

The program sends a reset command to that client.
Edit>Preferences - Opens the Preferences screen for defining BootP and

TFTP parameters.
Log Screen - Displays all BootP requests and TFTP sessions, including the
time and date of the request. In addition, the response type is also
displayed:
Version 4.8
Client Not Found
Client Found
Clients Mac Changed
Client Disabled
Listed at (when using the Test Selected Clients button).

309
January 2006
Mediant 3000
3.
12.1.4
For a TFTP session, file name and download status are displayed.
Pop-Up Menu - Right-clicking on a line in the log screen displays the pop-up
menu. In this menu there two options:
Reset - When this option is selected, the program searches the

database for the selected MAC. When the client is found, the program
adds the clients MAC to the ARP table, and then sends a reset
command to the client. Note that by performing the remote reset this
way, the user does not have to know the current IP address of the
client. To perform this option, the user must have administrator
privileges, otherwise an error message appears.
View Client - This option is the same as double-clicking on a line.

When selected, the Clients Screen opens. If the Clients MAC is found
in the database, it is focused. If not, a new client is added, with the MAC
filled out. The remaining fields require fill in.
At first run, you are requested to fill in the fields displayed on the Preferences
screen. To open the Preferences screen, from the main screen, select
Edit>Preference. Follow the directions detailed in 'Preferences Screen' on page
311 to configure the screen.
Logging Screen
The BootP/TFTP Server main screen includes the Log line, printed per BootP request
with the following parameters:
Hardware (MAC) address
Status (found or not found in cache)
Date and Time
Assigned IP address (if found)
Client name
Client specific Information - contains vendor specific information, which includes:

Board type, last IP, bootload version, and flash cmp version, etc. In order to
access the board information, add -be 1 to the ini file selection in the BootP
application. With this initial setting, even after deleting -be 1, the board continues
to report its internal data.
Clicking a Log line displays all BootP reply parameters or enables entry to a new
entity.
Right clicking a Log line opens up a menu.
Selecting Reset causes a soft reset of the board. Reset is available only for client
MACs that are configured on the BootP server. The second option on the menu is
View Client, which produces the same display as when clicking on the Log line.
User's Manual
310
User's Manual
12.1.5
Preferences Screen
Figure 12-2: Preferences Screen
The Preferences screen above is used to define BootP and TFTP configuration
parameters:
TFTP directory
ini File Mask
Boot File Mask
TFTP timeout and number of retransmissions
BootP replay type (Broadcast or Unicast)
BootP ARP mode (dynamic or static)
Number of initiated BootP replies (send after remote reset), optionally used when
the Mediant 3000 is installed behind the firewall that blocks BootP broadcast
requests.
In the BootP section, the user can select ARP mode: Dynamic or Static, and reply
type: Broadcast or Unicast. For a typical application, use Dynamic ARP mode and
Unicast, as shown above.
This option requires the user to have administrator privileges otherwise an error
message appears. If you dont have administrator privileges, uncheck the ARP
Manipulation Enabled checkbox in the Preferences Screen.
The Number of Timed Replies (the number of initiated timed BootP replies) can be
used when the Mediant 3000 is installed behind a Firewall that blocks BootP
broadcast requests. In a typical application, this feature can be disabled by entering 0
in this field. When selected, several BootP replies are sent to the Mediant 3000
immediately after the remote reset command.
Version 4.8
311
January 2006
Mediant 3000
For the TFTP server, the user can configure a TFTP directory and a value for TFTP
Timeout and Maximum Retransmissions. Set these values to 2 and 10 as shown
above as 5 and 10.
The TFTP server can be disabled by clearing the Enable checkbox.
12.1.6
Client Configuration Screen

Figure 12-3: Client Configuration Screen
The Client Configuration screen shown in the figure above displays:
All client entities
MAC
Name
IP per entity
In the left pane of the screen is the client list. By clicking on a client in this list, the
following parameters for this client are displayed on the right side of the screen:
User's Manual
Client MAC - This is the MAC address of the client. When the user edits the
MAC, a new client is added, with the same parameters as the previous client.
The client can be disabled by un-checking the check box on the right side of the
Client MAC. This causes the BootP server not to reply to the BootP request. The
client can be enabled by checking the check box. Click on the Apply button each
time the client enable check box is checked or unchecked.
312
User's Manual
Client Name - A text field for entering the client description.
Template - The template to be used for this client. When a template is selected,
its parameters override all of the previous parameters.
IP, Subnet, Gateway - Normal IP parameters.
TFTP Server IP - The IP address of the TFTP Server.
Boot File, ini File - The files to request from the TFTP server.
Note the seven check boxes to the right of the parameters. These enable the user to
assign only the fields from the template, which have adjacent marked checkboxes.
The rest can be unique for each client. When the field is assigned a value from the
selected template, the field is grayed (and unmodifiable).
With this screen, users can:
Add a new entry
Delete an existing entry
Modify an existing entry
Test a selected client for finding all BootP servers that respond to a BootP
request with a specific MAC address
If a template is selected, any parameter can be entered manually or copied from the
selected template by marking the checkbox to the right of the parameter. Usually, only
an IP address is entered manually while other parameters are copied from the
template.
To save them after performing changes, click Apply. By clicking Apply & Reset, the
program saves the changes to the database, performs a remote Reset to the client by
adding the clients MAC to the ARP table, and then sends out a reset command. This
option works only if ARP Manipulation Enabled checkbox in the Preferences
screen is checked (in the figure, 'Preferences Screen' on page 311) otherwise an
error message appears. It requires the user to have administrator privileges. The
remote reset is supported for software in this version and up.
When adding a new client, click Add Client. A client dialog box with blank parameters
is displayed. After filling out the parameters, click Apply. The client is added.
To find out if there is another BootP server on the net that contains a client with the
same MAC address, click Test Selected Clients. In the log screen, view the IP
addresses of all BootP servers that contain the same MAC address in the status
Listed At. In normal operation, BootP client MAC address should be listed only on a
single BootP server. If the MAC address is listed in multiple BootP servers, it must be
removed from other BootP servers.
Version 4.8
313
January 2006
Mediant 3000
12.1.7
Template Screen
Figure 12-4: Templates Screen
The figure above shows the Templates screen, which provides a fast way to configure
a number of clients that have the same parameters (except for the IP address). To use
the Templates screen, create a template, and then apply the template to the client by
selecting it.
The template includes:
User's Manual
Subnet
Gateway, TFTP server
BootFile
ini file
Call Agent fields
Server IP
314
User's Manual
13. Appendix - Individual ini File Parameters
13
Appendix - Individual ini File

Parameters
13.1
Individual ini File Parameters

The individual parameters contained in the ini file are provided in the following
parameter group tables:
System Parameters (refer to ''System Parameters'' on page 316)
Infrastructure Parameters (refer to ''Infrastructure Parameters'' on page 322)
Media Processing Parameters (refer to ''Media Processing Parameters'' on page

335)
PSTN Parameters (refer to ''PSTN Parameters'' on page 347)
SS7 Parameters (refer to ''SS7 Parameters'' on page 362)
Common Control Protocols Parameters (refer to ''Common Control Protocols

Parameters'' on page 364)
MGCP Specific Parameters (refer to ''MGCP Specific Parameters'' on page 371)
NFS Parameters (refer to NFS Parameters)
MEGACO Specific Parameters (refer to ''MEGACO Specific Parameters'' on page

375)
Web Interface Parameters (refer to ''Web Interface Parameters'' on page 379)
SNMP Parameters (refer to ''SNMP Parameters'' on page 382)
SCTP Parameters (refer to ''SCTP Parameters'' on page 384)
VoATM Parameters (refer to ''VoATM Parameters'' on page 386)
Names for optional configuration files (CAS signaling, Call Progress Tones and
Voice Prompts files).
Users do not have to specify all (or any) of the parameters in the ini file. If a parameter
is left unspecified in an ini file and the ini file is then loaded to the Mediant 3000, the
Mediant 3000 is configured with that parameter's default value. Leaving all ini file
parameters unspecified and loading the file to the Mediant 3000 is thus result in the
Mediant 3000 being configured with its defaults (contained in the software image cmp
file).
Note: To restore the Mediant 3000's default configuration parameters, use an
empty ini file without any valid parameters or with a semicolon (;)
preceding all lines in the file.
Array Parameters
Version 4.8
315
January 2006
Mediant 3000
Some parameters have array values. For each of these parameters listed in the
parameter tables below, if the ini file field name is used as is, the parameter applies to
all of its elements. To specify each element individually, add _xx (xx equals the
element number) to the end of the ini file field name. Information about the array
value's elements is contained in the Description column.
13.1.1
System Parameters
The table below lists and describes the system parameters contained in the ini file.
Use this table as a reference when modifying ini file parameter values.
Table 13-1: System Parameters

Host/Manual
Default Value
ini File Field Name
Description
ActiveBoardIPAddress
Defines the IP addresses of

the active boards in a High
Availability configuration, from
which the redundant board
receives state DB packets.
Range = Any IP address
ActiveBoardPort
Defines the port number for

the High Availability service.
Range = Valid port number
Default =
BSP_TPNCP_UDP_CONTRO
L_PORT
See Descr.
See Descr.
ActivityListToLog
This parameter defines what

activities are to be reported by
the device in the form of a log
message.
Parameter format is x, y, z.
where x, y, z are activity codes
to be reported by the device.
Supported activity codes:
PVC - Parameter Value
Changes.
AFL = Auxiliary Files Loading.
DR = Device Reset.
FB = Flash Burning.
SWU = SoftWare Update.
ARD = Access to Restricted
Domains.
NAA = Non Authorized
Access.
SPC = Sensitive Parameter
Changes.
Empty string
See Descr.
User's Manual
316
Valid Range
See Descr.
User's Manual

ini File Field Name
Description
AlarmHistoryTableMax
Size
Determines the maximum

number of rows in the Alarm
History table.
The parameter is controllable
via the Config Global Entry
Limit MIB (located in the
Notification Log MIB).
Default =
ALARM_HISTORY_DEFAULT
_SIZE
Range: 50 to 1000
Host/Manual
Default Value
Valid Range
See Descr.
See Descr.
(For Mediant 1000, the

range is 10 to 1000).
AUPDVerifyCertificates
This parameter configures the

AutoUpdate facility to verify
server certificates when using
HTTPS.
0 or 1
AutoUpdateCmpFile
Enables / disables the

automatic update mechanism
for the cmp file.
0 = The automatic update
mechanism doesnt apply to
the cmp file (default).
1 = The automatic update
mechanism includes the cmp
file.
0 or 1
AutoUpdateFrequency
Determines the number of

minutes the gateway waits
between automatic updates.
The default value is 0 (the
update at fixed intervals
mechanism is disabled).
Range: Any number
See Descr.
AutoUpdatePredefined
Time
Schedules an automatic
update to a predefined time of
the day.
The range is 'HH:MM' (24hour format).
For example: 20:18
NULL
See Descr.
BehaviorUponRadius
Timeout
This parameter defines device

behavior upon a RADIUS
timeout.
Values are:
0 = Deny access
1 = Check password locally
0 or 1
Version 4.8
317
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
Provides a link to a Channel

Associated Signaling (CAS)
file to be downloaded from a
remote server.
Range =
http://server_name/file,
https://server_name/file
NULL
See Descr.
CmpFileURL
This parameter provides a

link to a software image (cmp
file) to be downloaded from a
remote server.
Range = tftp://server_ip/file,
NULL
See Descr.
CptFileUrl
Provides a link to a Call

Progress Tones (CPT) file to
be downloaded from a remote
server.
Range =
NULL
See Descr.
DefaultAccessLevel
This parameter defines the

default access level for the
device. Default value is
'Security Administrator' (=
200).
200
0 to 255
DisableWebConfig
Enables or disables Web

Configuration.
0 = Read & Write mode
(default)
1 = Read Only mode
0 or 1
DisableWebtask
Enables or disables Web

Server Tasks.
0 = Enable (default);
1 = Disable
0 or 1
DNSPriServerIP

DNS primary server's IP
address.
Range = Legal IP address
0.0.0.0
See Descr.
DNSSecServerIP

DNS secondary server's IP
address.
0.0.0.0
See Descr.
ini File Field Name
Description
CasFileUrl
User's Manual
318
User's Manual

Host/Manual
Default Value
Valid Range
This parameter is used to

enable monitoring of on-the-fly
parameter changes via Syslog
messages.
1 = Activate
0 = Deactivate (default)
0 or 1
ENABLESTUN

enable the STUN module,
used for NAT traversal of UDP
packets.
1= Enable; 0 = Disable
0 or 1
EnableSyslog

enable the Syslog protocol
log.
1 = Activate; 0 = Deactivate
0 or 1
ETHERDISCOVER
MODE
Controls EtherDiscover mode

of operation.
0 = Always disable
EtherDiscover
1 = Enable EtherDiscover if
unconfigured; allow changes
to IP configuration (default)
2 = Always enable
EtherDiscover, but do not
allow changes.
0, 1, 2
IniFileTemplateUrl
Provides a link to an ini file to

server, in addition to IniFileUrl.
Range =
NULL
See Descr.
IniFileURL
This parameter provides a link

to an ini file to be downloaded
from a remote server.
NULL
See Descr.
InitialShellCommand
A Command Shell command

to be executed during
initialization. Several
commands can be entered
(separated by a semicolon).
NULL
KeepAliveTrapPort
The port to which the keep

alive traps are sent.
162
0 to 65534
M3KglobalIpAddr
Defines the Mediant 3000

global IP address to be used
by the active module in HA
system. (Dotted format
notation. e.g., 192.10.1.255).
0.0.0.0
See Descr.
ini File Field Name
Description
ENABLEPARAMETERS
MONITORING
Version 4.8
319
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range

define the NAT binding
lifetime, in seconds. STUN
refreshes the binding
information after this time
expires.
Range = 0 to 2592000
30
See Descr.
NTPServerIP

define the NTP server's IP
address.
0.0.0.0
See Descr.
NTPServerUTCOffset

define the NTP time to offset,
in seconds.
Default = 0
Range = -43200 to +43200
seconds
See Descr.
NTPUpdateInterval

NTP update interval, in
seconds. It's inadvisable to set
it exceeding 1 month
(2592000 seconds).
Range = 0 to 2592000
seconds
Default = 86400 seconds
See Descr.
See Descr.
PrtFileUrl
Provides a link to a
prerecorded tones dat file, to
server.
Range =
NULL
See Descr.
RadiusLocalCache
Timeout
Expiry time [sec] of locally

stored RADIUS password
cache.
Special values:
-1 = No Expiry
0 = No Cache
300 seconds
-1 or 0
RadiusLocalCacheMode

ability to reset the expiry of the
local Radius password cache:
0 = Expiry can't be reset
1 = Expiry resets on each
successful access to device
0 or 1
RedundantBoardIP
Address
Defines the IP address of the

redundant board, to which
state DB packets are sent.
Range = Any IP address
NULL
See Descr.
ini File Field Name
Description
NATBINDINGDEFAULT
TIMEOUT
User's Manual
320
User's Manual

Host/Manual
Default Value
Valid Range
Invokes an immediate restart

of the gateway.
This option can be used to
activate offline (not on-the-fly)
parameters that are loaded via
IniFileUrl.
0 = The immediate restart
mechanism is disabled
(default).
1 = The gateway immediately
restarts after an ini file with
this parameter set to 1 is
loaded.
0 or 1
SaveConfiguration
Determines if the device

configuration (and the
loadable file) is saved in flash.
Choose either:
1 = Save configuration file (the
Call Progress Tones, PRT
and/or coefficient file) in nonvolatile memory
0 = Don't save
0 or 1
SendKeepAliveTrap
When Enabled, this parameter

invokes the keep-alive trap
and sends it out every 9/10 of
the time defined in the
parameter defining NAT
Binding Default Timeout.
0 = Disable; 1 = Enable
0 or 1
STUNSERVER
PRIMARYIP
Defines the primary STUN

Server IP address.
0.0.0.0
See Descr.
STUNSERVER
SECONDARYIP
Defines the secondary STUN

server IP address.
0.0.0.0
See Descr.
SyslogServerIP
This parameter defines the IP

address in dotted format
notation.
e.g., 192.10.1.255
0.0.0.0
See Descr.
ini File Field Name
Description
ResetNow
Version 4.8
321
January 2006
Mediant 3000

ini File Field Name
Description
TelnetServerEnable
Enables or disables the

embedded Telnet server.
Telnet is disabled by default
for security reasons.
0 = Disable
1= Enable
2 = SSL mode (if available requires an SSL-aware Telnet
client software)
Host/Manual
Default Value
Valid Range
0 to 2
SSL mode is not available

on the MP-124 media
gateways
TelnetServerIdle
Disconnect
This parameter is used to set

the timeout for disconnection
of an idle Telnet session
(minutes). When set to zero,
idle sessions are not
disconnected.
Range: Any number
See Descr.
TELNETSERVERPORT
Defines the port number for

the embedded Telnet server.
Range = Valid port number
23
See Descr.
TrunkingToAnalog
FunctionalityProfile

Trunking to Analog
Functionality Profile.
0 = Disable
1 = Enable
MelCAS/LoopStart/GroundSta
rt to Analog Functionality
Refer to the enumerator
acTrunkingToAnalogFunctiona
lityProfile enum for the
possible values.
Integer >0
VpFileUrl
Provides a link to a Voice

Prompts file to be downloaded
from a remote server.
Range =
NULL
See Descr.
13.1.2
Infrastructure Parameters
The table below lists and describes the Infrastructure parameters contained in the ini
file. Use this table as a reference when modifying ini file parameter values.
User's Manual
322
User's Manual
Table 13-2: Infrastructure Parameters

Host/Manual
Default Value
Valid
Range
Sets the IP address of TPNCP

authorized servers.
Range = IP address in dotted
notation: xxx.xxx.xxx.xxx
0.0.0.0
See
Descr.
BaseUDPPort
Defines the lower boundary of UDP

ports to be used by the board. The
upper boundary is calculated on the
basis of BoardBaseUDPPort + 10 *
(Number of Channels). This
parameter value must be a multiple
of 10.
4000
See
Descr.
BootPRetries
Defines the number of BootP retries

that the board sends during start-up.
The board stops issuing BootP
requests when either an
AA122BootP reply is received or the
Number Of Retries is reached. This
parameter takes effect only after the
next board reset.
Range: 1 to 7,15
1 = 1 BootP retry, 1 sec.
2 = 2 BootP retries, 3 sec.
15 = BootP retries indefinitely.
1 to 7,15
BootPSelectiveEnable
Configures the board so that it will

only accept BootP replies, from
AudioCodes proprietary BootPTFTP Software.
0 or 1
BRONZESERVICECLAS
S
DIFFSERV
Sets the DiffServ for the Bronze

service class content.
10
0 to 56
DisableH100ClocksOn
TrunkFailure
Disables the H.100 clocks output

when the PSTN reference trunk
fails.
0 = Disable
1 = NetRef
2 = A\B
3 = All
0 to 3
DisableNetRefOnTrunk
Failure
Disables the NetRef signal when the

PSTN reference trunk fails.
1 = Disables; 0 = Enables
0 or 1
ini File Field Name
Description
AuthorizedTPNCP
Servers
Version 4.8
323
January 2006
Mediant 3000

Host/Manual
Default Value
Valid
Range
Disables specific events from being

sent to the VoPLib. For the selected
event, refer to enumerator
acTEvent.
Range: 0 to acLAST_EVENT
See
Descr.
EnableDetectRemote
MACChange
Allows for the detection of an

incoming RTP stream from a
changed remote MAC address.
Used for board redundancy
purposes.
0 = Disable
1 = Enable (trigger by media)
2 = Enable (trigger by GARP)
3 = Enable (trigger by either media
or GARP)
0 to 3
EnableDiagnostics
Checks the correct functionality of

the different hardware components
on the board. On completion of the
check, the board sends an
EV_END_BIT value, which contains
information on the test results of
each hardware component.
0 = No diagnostics (default)
1 = Perform diagnostics (full test of
DSPs, PCM, Switch, LAN, PHY and
Flash)
2 = Perform diagnostics (full test of
DSPs, PCM, Switch, LAN, PHY, but
partial, test of Flash, a quicker
mode)
0 to 2
EnableDNSasOAM
Sets the location of the DNS. If this

parameter is set and the machine is
functioning in multiple IP mode, the
DNS is located on the OAM
network. If not, the DNS is on the
control network.
0 = Control VLAN; 1 =OAM VLAN
0 or 1
EnableICMP
UnreachableReport
Reports receipt of unreachable

ICMP packets.
0 = Disabled; 1 = Enabled
0 or 1
ini File Field Name
Description
DisableTPNCPEvent
User's Manual
324
User's Manual

Host/Manual
Default Value
Valid
Range
Specifies the type of compare

operation performed on the first
packet that is received on a newly
opened channel for the Network
Address Translation (NAT) feature.
If set to 1, the board compares the
first incoming packets source IP
address, to the remote IP address
stated in the opening of the channel.
If the two IP addresses do not
match, the NAT operation takes
place. Consequently, the remote IP
address and the UDP port of the
outgoing stream are replaced by the
source IP address and UDP port of
the first incoming packet.
0 or 1
EnableLANWatchdog
Detects LAN failures on the board.

A LAN failure can result from a
software or hardware malfunction. If
a LAN failure is detected, the board
performs a self reset (when not in
PCI mode).
0 or 1
EnableMultipleIPs
Enables the multiple IP feature.

0 or 1
EnableNTPasOAM
Sets the location of the Network

Time Protocol (NTP). If this
parameter is set and the machine is
functioning in multiple IP mode, the
NTP is located on the OAM network.
If not, the NTP is located on the
control network.
0 or 1
EnablePPPoE
Enables the PPPoE (Point-to-Point

Protocol over Ethernet) feature.
0 or 1
EnableSCTPasControl
Sets the location of the Stream

Control Transmission Protocol
(SCTP). If this parameter is set and
the machine is functioning in
multiple IP mode, the SCTP is
located on the control network. If
not, the SCTP is located on the
OAM network.
0 or 1
ini File Field Name
Description
EnableIPAddrTranslation
Version 4.8
325
January 2006
Mediant 3000

Host/Manual
Default Value
Valid
Range
Sets the TPNCP location on the

Operation, Administration and
Management (OAM) network, when
operating in multiple IP mode.
If this parameter is set and the
machine is working in multiple IP
mode, TPNCP is located on the
OAM network.
0 = TPNCP on Control network
1 = TPNCP on OAM network
0 or 1
EnableTPNCPSecurity
Secures the TrunkPack Network

Control Protocol (TPNCP) by
accepting only pre-determined
servers via the parameter defining
authorized TPNCP servers.
0 = Disabled; 1 = Enabled
0 or 1
EnableUDPPort
Translation
Specifies the type of compare

operation performed on the UDP
ports. When set, the compare
operation is performed on the UDP
ports. If this parameter is set,
EnableIpAddrTranslation must also
be set.
0 or 1
EthernetPhy
Configuration
Controls the Ethernet connection

mode type. Auto-negotiate falls back
to Half-Duplex mode (HD) when the
opposite port is not in Autonegotiate mode. The speed (10
Base-T or 100 Base-TX) in this
mode is always configured correctly.
0 = 10 Base-T half-duplex
1 = 10 Base-T full-duplex
2 = 100 Base-TX half-duplex
3 = 100 Base-TX full-duplex
4 = Auto-negotiate
0 to 4
ExtBootPReqEnable
1 = Enables extended information to

be sent in the BootP request. The
device uses the vendor specific
information in the BootP request to
provide device-related, initial startup
parameters such as board type,
current IP address, software
version, geographical address, etc.
This is not available in DHCP. 0 =
Disable
0 or 1
ini File Field Name
Description
EnableTPNCPasOAM
User's Manual
326
User's Manual

Host/Manual
Default Value
Valid
Range
Forces an exception dump that is

sent every time the board restarts.
The last SW exception dump would
be sent each time the board
restarts.
0 or 1
GOLDSERVICECLASSDI
FFSERV
Sets the DiffServ for the Gold

26
0 to 56
HeartbeatDestIP
Sets the destination UDP port to

which the Heartbeat Packets are
sent.
0.0.0.0
See
Descr.
HeartbeatDestPort
Sets the destination UDP port to

which the heartbeat packets are
sent.
0 to 64000
HeartbeatIntervalmsec
Sets the time delay in msec

between consecutive heartbeat
packets.
Use multiples of 10.
Range = 0x0 to 0xffffffff
Default = 0xFFFFFFFF
See Descr.
See
Descr.
HeartbeatSecondary
DestIP
Sets the secondary destination IP

address to which the heartbeat
packets are sent.
0.0.0.0
See
Descr.
ICMPUnreachable
ReportInterval
Determines:
(a) The time the board ignores
incoming ICMP unreachable
packets from the channel activation
time.
(b) The time it takes from the last
ICMP unreachable packet until the
board reports ICMP Reachable.
Range = unsigned long
5000
See
Descr.
INIFileVersion
Contains the ini file version number

that is reported in the
acEV_BOARD_STARTED event.
Range = Long integer value.
See
Descr.
LocalControlDefaultGW
Defines the default gateway of the

Control when operating in a multiple
IP mode.
Range: Legal IP
0.0.0.0
See
Descr.
ini File Field Name
Description
ForceExceptionDump
Version 4.8
327
January 2006
Mediant 3000

Host/Manual
Default Value
Valid
Range
Defines the IP address of the

IP mode.
Range: Legal Subnet
0.0.0.0
See
Descr.
LocalControlSubnetMask
Defines the Subnet Mask of the

IP mode.
Range: Legal Subnet
0.0.0.0
See
Descr.
LocalMediaDefaultGW
Defines the default gateway for the

media interface, when operating in a
multiple IP mode.
Range: Legal IP address
0.0.0.0
See
Descr.
LocalMediaIPAddress
Defines the IP address of the Media

when operating in multiple IP mode.
0.0.0.0
See
Descr.
LocalMediaSubnetMask
Defines the Subnet Mask for the

media interface when operating in a
multiple IP mode.
Range: Legal Subnet
0.0.0.0
See
Descr.
LocalOAMDefaultGW
Sets the Default gateway for the

OAM interface when operating in
multiple IP mode.
Range: Legal IP address in subnet
0.0.0.0
See
Descr.
LocalOAMIPAddress
Sets the IP address of the OAM

(Operation, Administration &
Management) when operating in
multiple IP mode.
0.0.0.0
See
Descr.
LocalOAMSubnetMask
Sets the Subnet Mask for the OAM

interface, when operating in multiple
IP mode.
Range: Legal Subnet
0.0.0.0
See
Descr.
MIIRedundancyEnable
Determines whether or not to

activate LAN redundancy, for
platforms other than the TP-1610
that have two Ethernet ports.
0 or 1
ini File Field Name
Description
LocalControlIPAddress
TP-260/UNI Only
NETWORKSERVICECLA
SSDIFFSERV
Sets the DiffServ for Network

48
0 to 56
PCMLawSelect
Selects the type of PCM

companding law in input/output
TDM bus (TDM bus is defined using
the TDMBusType parameter).
1=A-law
3= -law
See Descr.
0, 1 or 3
User's Manual
328
User's Manual

ini File Field Name
Description
Host/Manual
Default Value
Valid
Range
See
Descr.
If the initial value is zero or if no

value is set in the ini file, the value
will be set according to the PSTN
line type:
A-law for E1 line type
-law for T1 line type
PPPoEPassword
Password for PAP or Secret for

CHAP authentication.
Range = String[47]
PPPoERecover
IPAddress
IP address to use when booting

from the flash to non-PPPoE (Pointto-Point Protocol over Ethernet)
environment.
notation xxx.xxx.xxx.xxx
10.4.10.4
See
Descr.
PPPoERecoverDfgw
Address
Default GW address to use when

booting from the flash to nonPPPoE (Point-to-Point Protocol over
Ethernet) environment.
10.4.10.1
See
Descr.
PPPoERecoverSubnet
Mask
Subnet Mask to use when booting

from the flash to non-PPPoE (Pointto-Point Protocol over Ethernet)
environment.
Default = 255.255.0.0
See Descr.
See
Descr.
PPPoEServerName
Server Name for CHAP

authentication.
Range = String[47]
See
Descr.
PPPoEStaticIPAddress
IP address to use in static

configuration setup. If set, used
during PPP negotiation to request
this specific IP address from the
PPP server. If approved by the
server, this IP is used during the
session.
0.0.0.0
See
Descr.
PPPoEUserName
User Name for PAP or Host Name

for CHAP authentication.
See
Descr.
46
0 to 56
Range = String[47]
PREMIUMSERVICECLA
SS
MEDIADIFFSERV
Version 4.8
Sets the DiffServ for Premium

service class content and media
traffic.
329
January 2006
Mediant 3000

Host/Manual
Default Value
Valid
Range
Comprises the Destination column

of the static routing rules that users
can add to. Range: Legal IP
Address.
NULL
See
Descr.
RoutingTableDestination
MasksColumn
Comprises the destination masks

column of the static routing rules
that users can add to.
NULL
See
Descr.
RoutingTableGateways
Column
Comprises the gateways column of

the static routing rules
Range = Legal IP Address
NULL
See
Descr.
RoutingTableHopsCount
Column
Comprises the Hops count column

of the static routing rules
20
0 to 255
hops
RoutingTableInterfaces
Column
Comprises the interfaces column of

the static routing rules. I/F # 0 to 2
0 to 2
SctpIPAddress
Set the source IP address for the

SCTP traffic.
See Descr.
See
Descr.
ini File Field Name
Description
RoutingTable
DestinationsColumn
Default = 0.0.0.0 (the main source

IP will be used in that case)
When working in multiple IP mode,
the control/OAM IP will be used
(according to the parameter
EnableSCTPasControl).
SerialData
Changes the serial data bit for the

Simplified Message Desk Interface
(SMDI).
7 = 7-bit; 8 = 8-bit
M1K Only
7 or 8
SerialFlowControl
Changes the serial flow control for

the Simplified Message Desk
Interface (SMDI).
0 = None;1 = Hardware
0 or 1
M1K Only
SerialParity
Changes the serial parity for the

(SMDI).
0 = None; 1 = Odd; 2 = Even
M1K Only
0, 1, 2
SerialStop
Changes the serial stop for the

(SMDI).
1 = 1-bit; 2 = 2-bit
1 or 2
User's Manual
330
User's Manual

ini File Field Name
Description
Host/Manual
Default Value
Valid
Range
0 or 1
M1K Only
SMDI
Enables the Simplified Message

Desk Interface (SMDI). SMDI
defines a method whereby
telephony systems can provide
voice-messaging systems with data
required by those telephony
systems to process incoming calls
intelligently.
Whenever the phone system routes
a call, it sends a SMDI message
through an EIA/TIA-232 connection
to the voice-messaging system. It
tells it the line that it is using, the
type of call that it is forwarding, and
information about the source and
destination of the call.
0 = Normal Serial
1 = Serial SMDI
M1K Only
SubnetBroadcastAfter
ENetSOEnabled
Enables subnet broadcast after

Ethernet switchover.
0 or 1
TDMBITSClock
Reference
Configures the BITS clock reference

when the board source clock is set
to BITS and Fallback is set to
manual or non-revertive.
1 = REF_1
2 = REF_2
1 to 2
TDMBITSClockSource
Configures which clock is output to

the BITS card and on which output
signal.
Range:
0 = No output
(acTDMBusClockSource_Null)
4 = Network_A
(acTDMBusClockSource_Network)
16 =
Network_B(acTDMBusClockSource
_Network_B)
17 =
ATM_A(acTDMBusClockSource_AT
M_OC3)
18 =
ATM_B(acTDMBusClockSource_AT
M_OC3_B)
0, 4, 16 to
21
Version 4.8
331
January 2006
Mediant 3000

Host/Manual
Default Value
Valid
Range
Selects the clock source on which

the board synchronizes.
1 = Local oscillator
3 = MVIP
4 = PSTN Network
8 = H.110A
9 = H.110B
10 = NetRef1
11 = NetRef2
12 = SC2M
13 = SC4M
14 = SC8M
Default = 1; TP-1610 = 3
See Descr.
1,3,4,8 to
22
TDMBusEnableFallback
Defines the auto fallback of the

clock.
Range:
0 = Manual
1 = Auto Non-Revertive
2 = Auto Revertive
0 to 2
TDMBusFallbackClock
Selects the fallback clock source on

which board synchronizes in the
event of clock failure.
4 = PSTN Network
8 = H.110A
9 = H.110B
10 = NetRef1
11 = NetRef2
4, 8 to 11
TDMBusLocalReference
When the clock source is set to

Network, this parameter selects the
Trunk ID to be used as the clock
synchronization source of the board.
When using H.110/H.100 bus, this
parameter also selects the trunk
used as the clock source for the
NetRef clock generation (in this
case, the clock source must not be
set to Network).
Range = 0 to (MAX_TRUNK _NUM1)
See
Descr.
TDMBusmasterSlave
Selection
Sets SC/MVIP/H.100/H.110 to
either:
0 = Slave mode (another board in
the system must supply the clock to
the TDM bus) or Master mode (the
board is the clock source for the
TDM bus) or Secondary Master
mode (for H100/H110 Bus only).
1 = H.110A Master in Master mode
2 = H.110B Master
0 to 2
ini File Field Name
Description
TDMBusClockSource
User's Manual
332
User's Manual

Host/Manual
Default Value
Valid
Range
Selects the NetRef output

functionality.
0 = Do not output any NetRef
1 = Generation of NetRef 1
2 = Generation of NetRef 2
3 = Generation of both
0 to 3
TDMBusNetrefSpeed
Determines the NetRef frequency

(for both generation and
synchronization).
0 = 8 kHz
1 = 1.544 MHz
2 = 2.048 MHz
0 to 2
TDMBusOutputPort
Defines the SC/MVIP/H.100/H.110

output port to be used for the
board's channel #0. All other
channels then occupy the next
timeslots sequentially.
Range:
0 to 15 for SC/MVIP
0 to 31 for H.110
See
Descr.
TDMBusOutputStarting
Channel
Defines the outgoing TDM Timeslot

for board's channel #0. The
remaining channels are organized
sequentially.
0 to 127
TDMBusSpeed
Selects the TDM bus speed

according to the Bus Type as
follows:
SC = 0/2/3
H.110/H.100 = 3
MVIP = 0
Where:
0 = 2048 kbps
2 = 4096 kbps
3 = 8192 kbps
4 = 16384 kbps
Default: TP-260/UNI = 2;
See Descr.
See
Descr.
See Descr.
See
Descr.
ini File Field Name
Description
TDMBusNetrefOUTPUT
MODE
All other boards = 3

TDMBusType
Version 4.8
Selects the TDM bus interface to be

used (only one TDM bus interface
can be enabled at one time although
more than one can physically exist
on the board).
Range:
0 = acMVIP_BUS
1 = acSC_BUS
2 = acFRAMERS
4 = acH100_BUS
5 = EXT TDM
6 = Analog
333
January 2006
Mediant 3000

ini File Field Name
Description
Host/Manual
Default Value
Valid
Range
8 = SW Pstn
Default:
TP-1610 = 2;
TP-260/UNI = 1
TpncpNatTraversal
Password
Selects a password for

authentication with the TPNCP host.
Rumble
Any string
TpncpNatTraversalMode
This parameter indicates that the

device should initiate the connection
to the TPNCP host.
! = Enable; 0 = Disable
0 or 1
VLANBRONZESERVICE
CLASSPRIORITY
Sets the priority for the Bronze

0 to 7
VLANCONTROLVLANID
Sets the control VLAN identifier.
1 to 4094
VLANGOLDSERVICECL
ASSPRIORITY
Sets the priority for the Gold service

class content.
0 to 7
VLANHEARTBEAT
VLANID
Sets the heartbeat stream VLAN

identifier.
0 to 4094
VLANMEDIAVLANID
Sets the media VLAN identifier.
1 to 4094
VLANMODE
Sets the VLAN functionality.

2 = PassThrough
0 to 2
VLANNATIVEVLANID
Sets the VLAN identifier, assumed

for inbound packets without a VLAN
tag.
0 to 4094
VLANNETWORKSERVIC
E
CLASSPRIORITY
Sets the priority for Network service

class content.
0 to 7
VLANOAMVLANID
Sets the OAM (Operation,

Administration and Management)
VLAN identifier.
1 to 4094
VLANPREMIUMSERVIC
E
CLASSCONTROLPRIORI
TY
Sets the priority for Premium service

class content and control traffic.
0 to 7
VLANPREMIUMSERVIC
E
CLASSMEDIAPRIORITY
Sets the priority for Premium service

class content and media traffic.
0 to 7
vlanSendNonTaggedOn
Native
Specify whether to send non-tagged

packets on the native VLAN. By
default, priority-tagged packets
(vlanId=0) are sent.
0 or 1
User's Manual
334
User's Manual

ini File Field Name
Host/Manual
Default Value
Description
Valid
Range
1 = dont send
13.1.3
Media Processing Parameters

The table below lists and describes the Media Processing parameters contained in the
ini file. Use this table as a reference when modifying ini file parameter values.
Table 13-3: Media Processing Parameters

Host/Manual
Default Value
Valid Range
Determines the AMD (Answer

Machine Detector) detection
direction.
0 = Detection from TDM side
1 = Detection from Network
side
0 or 1
ATMG711DefaultLaw
Select
Determines the ATM G.711

Default Law Select.
0 = A-Law; 1 = m-Law
0 or 1
BasicRTPPacketInterval
Selects the RTP packet rate

for sample based coders
(such as G.711, G.726,
G.727). Also applicable for
G.729, G.729E & G.728.
0 = Default (set internally)
1 = 5 msec
2 = 10 msec
3 = 20 msec
0 to 3
BellModemTransport
Type
Use this parameter to set the

Bell modem transport
method.
0 = Transparent
2 = Bypass (enum
ByPassEnable)
3 = Transparent with Events
(enum EventsOnly)
0, 2, 3
ini File Field Name
Description
AMDDetectionDirection
Version 4.8
335
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
Determines if the broken

connection mechanism is
activated when the RTP
stream is activated (= 1); or
when first RTP packet is
received (= 0).
(acTActivateBrokenConnectio
n)
0 or 1
BrokenConnectionEvent
Timeout
Determines for how long the

RTP connection should be
broken before the Broken
Connection event is issued.
In units of 100 msec.
Range = 3 to 21474836 in
units of 100 msec (300 to
0x80000000 msec)
3 (= 300 msec)
See Descr.
CallerIDTransportType
Defines the CallerID

Transport type.
0 = Disable
1 = Relay
2 = ByPass
3 = Mute
0 to 3
CallerIDType
Defines the supported Caller

ID type.
0 = Bellcore
1 = ETSI
2 = NTT
4 = British
16 = ETSI_ETS
17 = Denmark
18 = Indian
19 = Brazilian
1, 2, 4, 16 to 19
CallProgressDetector
Enable
Enables or disables detection

of Call Progress Tones.
0 or 1
CASTransportType
Controls the ABCD signaling

transport type over IP.
0 = No Relay over the
network
1 = Enable CAS relay
according to RFC 2833
0 or 1
CNGDetectorMode
Determines the CNG

Detector mode.
0 = Disable
1 = Relay
2 = Event Only
0 to 2
ini File Field Name
Description
BrokenConnectionEvent
ActivationMode
User's Manual
336
User's Manual

Host/Manual
Default Value
Valid Range
Determines the notification

mode for the RTP connection
establishment event
acEV_CONNECTION_ESTA
BLISHED.
0 = Notify only after a broken
connection event
1 = Also notify when the first
RTP packet is received
0 or 1
DisableNAT
Enables or disables the NAT

feature.
0 = Do not disable NAT
1 = Disable NAT
0 or 1
DisableRTCPRandomize
Controls whether RTCP

report intervals are
randomized or whether each
report interval accords exactly
to the parameter defining
RTCP Mean Tx Interval (in
milliseconds).
0 = Randomize
1 = Dont Randomize
0 or 1
DJBufMinDelay
Defines the Dynamic Jitter

Buffer Minimum Delay (in
msec).
150
0 to 150
DJBufOptFactor
Defines the Dynamic Jitter

Buffer frame error/delay
optimization.
0 to 12
DSPVersionTemplate
Number
Selects the DSP load

number. Each load has a
different coder list, a different
channel capacity and different
features supported.
0 to 255
DTMFDetectorEnable

of DTMF signaling.
0 or 1
DTMFTransportType
Defines the type of DTMF

transport.
0 = Erase DTMFs from voice
transport not relayed to
remote
2 = DTMFs not erased are
not relayed to remote
3 = DTMFs are muted from
the voice stream and relayed
0, 2, 3
ini File Field Name
Description
Connection
Establishment
NotificationMode
Version 4.8
337
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
Defines and controls the

DTMF generation volume [dBm]
-11
-31 to 0
ECHybridLoss
Sets the worst case ratio

between the signal level
transmitted to the hybrid and
the echo level returning from
hybrid. Set this per worst
hybrid in the system in terms
of echo return loss. Refer to
the enumeration
acTECHybridLoss.
0 = 6 dBm
1 = 9 dBm
2 = 0 dBm
3 = 3 dBm
0 to 3
EnableContinuityTones
Enables or disables
Continuity Test tone detection
and generation according to
the ITU-T Q.724
recommendation.
0 or 1
EnableDSPIPM
Detectors
Enables or disables DSP IP

Media Detectors. Enabling
this parameter might reduce
the board channel capacity.
0 or 1
EnableEchoCanceller
Enables or disables the Echo

Canceler.
0 or 1
EnableFaxModem
InbandNetworkDetection
Enables or disables inband

network detection related to
fax/modem.
0 or 1
ENABLEMEDIA
SECURITY
Enables or disables Media

Security protocol (SRTP) .
Enabling this parameter might
reduce the board channel
capacity.
0 or 1
EnableNoiseReduction
Support
Enables or disables Noise

Reduction. Enabling this
parameter might reduce the
board channel capacity.
1 = Enable; 0 = Disable
0 or 1
EnablePatternDetector
Enables or disables activation

of the PD (Pattern Detector).
0 or 1
ini File Field Name
Description
DTMFVolume
User's Manual
338
User's Manual
ini File Field Name
Description
Host/Manual
Default Value
Valid Range
EnableRFC2658
Interleaving
When enabled, RTP packets

include an interleaving byte
for VBR coders.
0 or 1
EnableSilence
Compression
Enables or disables Silence

Suppression Mode.
0 = Disable =
SILENCE_COMPRESION_DI
SABLE
1 = Enable =
SILENCE_COMPRESION_E
NABLE
2 = Enable without adaptation
=
SILENCE_COMPRESION_E
NABLE_NOISE_ADAPTATIO
N_DISABLE
0 to 2
EnableStandardSID
PayloadType
When set to 1 (Enable), SID

packets are sent with the
RTP SID type (RFC 3389).
Determines whether Silence
Indicator (SID) packets that
are sent and received are
according to RFC 3389.
0 = Disabled (default).
1 = Enabled.
0 or 1
Note: Applicable only to

MP-11x and Mediant 1000.
EnableSTUModem
Detection

of two tones required for an
STU modem.
0 or 1
EnableTrunkTesting
Tones
Enables or disables trunk

testing tones.
0 = Disables trunk testing
tones
1 = Enables trunk testing
tones
0 or 1
EVRCRate

configure the EVRC coder bit
rate.
0 = Variable Rate
1 = 1 kbps
2 = 4 kbps
0 to 3
Version 4.8
339
January 2006
Mediant 3000
ini File Field Name
Description
Host/Manual
Default Value
Valid Range
3 = 8 kbps
FaxBypassPayloadType
Users can use this parameter

to modify the Fax Bypass
Mode RTP packet's payload
type.
In the case of congestion (if
the selected payload type is
already used for other
coders/modes), then a
TP_SETUP_PARAMETER_I
NVALID_ERROR is issued
and the payload type is set to
the default value (102).
It is the user's responsibility to
avoid congestion with other
payload types.
102
0 to 127
FaxModemBypasDJBuf
MinDelay
Determines the Jitter Buffer

constant delay (in msec)
during a Fax & Modem
Bypass session;(the minimum
Jitter Buffer Size).
40
0 to 150
FaxModemBypassBasic
RTPPacketInterval
Sets the basic Fax / Modem

Bypass RTP packet rate.
0 = Default (set internally)
(PACKET_INTERVAL_DEFA
ULT)
1 = 5 msec
(PACKET_INTERVAL_5_MS
EC)
2 = 10 msec
(PACKET_INTERVAL_10_M
SEC)
3 = 20 msec
(PACKET_INTERVAL_20_M
SEC)
0 to 3
FaxModemBypassCoder
Type

to set the fax/modem bypass
coder (according to
acTCoders).
0 = G.711 A-Law
0 to 64
FaxModemBypassM
Defines the number of basic

frames to generate one RTP
fax/modem bypass packet.
1 or 2
User's Manual
340
User's Manual

Host/Manual
Default Value
Valid Range
Determines the fax gain

control.
The range -18 to -3 relates to
-18.5 dBm to -3.5 dBm in
steps of 1 dBm.
-12
-18 to -3
FaxRelayECMEnable
Enables or disables the using

of ECM mode during Fax
Relay.
0 or 1
FaxRelayEnhanced
RedundancyDepth
Determines the number of

repetitions to be applied to
control packets when using
the T.38 standard.
0 = No redundancy
1 = 1 packet redundancy
4 = Maximum redundancy
0 to 4
FaxRelayMaxRate
Limits the maximum rate at

which fax messages are
transmitted.
0 = 2400 bps
1 = 4800 bps
2 = 7200 bps
3 = 9600 bps
4 = 12000 bps
5 = 14400 bps
0 to 5
FaxRelayRedundancy
Depth
Determines the depth of

redundancy for fax packets.
This parameter is applicable
only to non-V.21 packets.
0 = No redundancy
0 to 2
FaxTransportMode
Sets the Fax over IP transport

method.
0 = Transparent
1 = Relay
2 = Bypass
0 to 3
IBSDetectionRedirection
Determines the IBS (In-Band

Signaling) Detection
Direction.
0 = PCM; 1 = Network
0 or 1
ini File Field Name
Description
FaxModemRelayVolume
Version 4.8
341
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
Defines the ABCD (CAS)

pattern to be applied on the
signaling bus before it is
changed by the user or the
PSTN protocol. This is only
relevant when using PSTN
interface with CAS protocols.
0x0 to 0xF
IdlePCMPattern
Defines the PCM pattern

applied to the E1/T1 timeslot
(B-channel) when the channel
is idle.
Default:
0xFF if PCMLawSelect is mLaw
0xD5 if PCMLawSelect is ALaw
See Descr.
0x00 to 0xFF
InputGain
Defines the PCM input gain.

Range = -32 dB to +31 dB in
1 dB steps.
Default = No Gain
-32 to +31
LowDSPResources
EventHyst
Determines the space

between the low and hi
watermarks of the DSP
resource notifications.
Range = 0 to the maximum
number of DSP channels
See Descr.
LowDSPResources
EventThreshold
Determines when a
notification indicating a 'low
number of DSP resources' is
issued. Range = Between 0
and the maximum number of
DSP channels
See Descr.
MaxDTMFDigitsInCID
String
Determines the maximum

number of DTMF digits in a
DTMF-based Caller ID string
26
0 to 26
ini File Field Name
Description
IdleABCDPattern
User's Manual
342
User's Manual
ini File Field Name
Description
MaxEchoCancellerLengt
h
Defines the maximum board

EC (Echo Canceler) length
capability.
Host/Manual
Default Value
Valid Range
See Descr.
0 = EC length determined
internally to reach maximum
channel capacity.
4 = 32 msec
11 = 64 msec
22 = 128 msec
TP-1610/TP260/UNI only:
Using 128 msecs reduces the
channel capacity to 200
channels.
MFSS5DetectorEnable

of MF SS5 line signaling.
0 or 1
MFTransportType
Defines the type of MF

transport.
0 = Erase MFs from voice
transport not relayed to
remote
2 = MFs not erased are not
relayed to remote
3 = MFs are muted from the
voice stream and relayed
0, 2, 3
MinDTMFDigitsInCID
String
Determines the minimum

number of DTMF digits in a
DTMF-based Caller ID string.
0 to 26
ModemBypassPayload
Type

to modify the Modem Bypass
Mode RTP packet's payload
type.
In the case of congestion (if
the selected payload type is
already used for other
coders/modes), then a
TP_SETUP_PARAMETER_I
NVALID_ERROR is issued
and the payload type is set to
the default value (103).
It is the user's responsibility to
avoid congestion with other
payload types.
103
0 to 127
NoiseReduction
ActivationDirection
Noise Reduction activation

direction
0 = from TDM side
0 or 1
Version 4.8
343
January 2006
Mediant 3000
ini File Field Name
Description
Host/Manual
Default Value
Valid Range
1 = from Network side
NoiseReductionIntensity
Noise Reduction Intensity:

0 = Weakest
8 = Normal
15 = Strongest
0 to 15
NSEMode
Enables or disables Cisco's

NSE fax / modem automatic
pass-through mode.
0 or 1
NSEPayloadType

to modify the NSE packet's
payload type.
105
96 to 127
PDPattern
Defines the patterns that can

be detected by the Pattern
Detector.
0 to 0xFF
PDThreshold
Defines the number of

consecutive patterns to
trigger the pattern detection
event.
0 to 31
PrerecordedTonesFile
Name
Defines the name (and path)

of the file containing the
Prerecorded Tones.
Range = String of ASCII
characters
See Descr.
QCELP13Rate

configure the QCELP13
coder bit rate.
0 = Variable Rate
1 = 1 kbps
2 = 3 kbps
3 = 7 kbps
4 = 13 kbps
0 to 4
QCELP8Rate

configure the QCELP8 coder
bit rate.
0 = Variable Rate
1 = 1 kbps
2 = 2 kbps
3 = 4 kbps
4 = 8 kbps
0 to 4
RFC2198PayloadType
This parameter sets the RFC

2198 (RTP Redundancy)
packet's parameter 'RTP
Payload Type'.
104
96 to 127
User's Manual
344
User's Manual

Host/Manual
Default Value
Valid Range
Controls the RFC 2833 Rx

Relay RTP Payload type.
96
96 to 127
RFC2833TxPayload
Type
Controls the RFC 2833 Tx

Relay RTP Payload type
96
96 to 127
RTPNOOPENABLE
User can enable or disable

Noop packets sending mode
by setting this parameter.
0 to 1
RTPNOOPINTERVAL
User can modify Noop

packets sending interval by
setting this parameter (in
msec)
10000 msec
20 to 600000
(10 min)
RTPNOOPPAYLOAD
TYPE
User can modify the Noop

packets RTP Payload type by
setting this parameter.
120
96 to 127
RTPRedundancyDepth
Enables or disables
generation of RFC 2198
redundancy packets.
0 or 1
SerialPortAuditInterval
Min
Interval timeout in minutes, of

the Serial Port audit. In case
of 0 value, the audit isn't
running.
0 to 60
SITDetectorEnable
Enables or disables SIT

(Special Information Tone)
detection according to the
ITU-T recommendation
E.180/Q.35.
0 or 1
TestMode
Defines the type of testing

mode applied:
0 = Coder Loopback performs
an encoder/decoder loopback
inside the DSP device
1 = PCM Loopback loops
back an incoming PCM to the
outgoing PCM.
2 = ToneInjection generates a
1000 Hz tone to the outgoing
PCM
3 = NoLoopback sets the
channel to work in normal
mode
0 to 3
UserDefinedTone
DetectorEnable

of User Defined Tones
signaling.
0 or 1
ini File Field Name
Description
RFC2833RxPayload
Type
Version 4.8
345
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
Sets the V.22 modem

transport method.
0 = Transparent
2 = Bypass
0, 2, 3
V23ModemTransport
Type
Sets the V.23 modem

transport method.
0 = Transparent
2 = Bypass
0, 2, 3
V32ModemTransport
Type
Sets the V.32 modem

transport method.
0 = Transparent
2 = Bypass
0, 2, 3
V34ModemTransport
Type
Sets the V.34 modem

transport method.
0 = Transparent
2 = Bypass
0, 2, 3
VBRCoderHeader
Format
When enabled, RTP packets

include an interleaving byte
for VBR coders.
0 or 1
VoicePayloadFormat
Sets the voice payload

format. Choose either 0 =
RTP or 1 = ATM (which
enables working with vendors
that use G.726 ATM Payload
Format over RTP). Uses the
enum
acTVoicePayloadFormat.
0 = VoicePayloadFormatRTP
1 = VoicePayloadFormatATM
2=
VoicePAyloadFormatIllegal
0 to 2
VoicePromptsFileName
Defines the name (and path)

of the file containing the
Voice Prompts.
Range = String of ASCII
characters
See Descr.
VoiceVolume
Defines the voice output gain

control.
Range = -32 dB to +31 dB in
1 dB steps
-32 = mute
Default = 0 = No Gain
-32 to +31
ini File Field Name
Description
V22ModemTransport
Type
User's Manual
346
User's Manual
Note: The following parameters are to be supported in the next applicable

release:
13.1.4
AMDDetectionDirection
CallerIDTransportType
CallerIDType
QCELP13Rate
QCELP8Rate
PDThreshold
PDPattern
PSTN Parameters
The table below lists and describes the PSTN parameters contained in the ini file. Use
this table as a reference when modifying ini file parameter values.
Table 13-4: PSTN Parameters

Host/Manual
Default Value
Valid Range
This is a pointer to the

CAS filename index (0-7).
The index is
CASFileName_X.
CASFileName_0 through
to CASFileName_7 are
the path and names of the
CAS protocol
configuration files.
NULL
See Descr.
This parameter enables or

disables the CAS protocol
configuration.
0 or 1
ini File Field Name
Description
CASFileName
CASProtocolEnable
When this parameter is

enabled, the conference
capability is disabled.
TP-6310 only
Version 4.8
347
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
This parameter
determines which CAS
protocol file to use on a
specific trunk. The index
value corresponds to the
number configured for the
parameter
CASFileName_X.
Range = not greater than
the parameter defining the
PSTN CAS Table Num.
See Descr.
CASTablesNum
This parameter defines

the quantity of CAS tables
that are loaded to the
device during a reset. The
quantity of CAS tables
defined should match the
value configured for
parameter
CASFILENAME_X.
0 = when there is no CAS
table to be loaded
0 to 8
ClockMaster
Use to select the trunk

clock source.
0=
acCLOCK_MASTER_OF
F (clock recovered from
the line)
1=
acCLOCK_MASTER_ON
(the trunk clock source is
provided by the
internal/TDM bus clock
source depending on the
parameter TDM Bus
Clock Source)
0 or 1
0 to 2
ini File Field Name
Description
CASTableIndex
TP-6310/T3 Only
Not relevant for TP6310/SDH
DCHConfig
User's Manual
Defines D-channel
configuration. This setting
is only applicable to ISDN
PRI protocols that support
NFAS and/or D-channel
backup procedures.
0 = D-channel is Primary
1 = Backup
2 = NFAS
348
User's Manual

Host/Manual
Default Value
Valid Range
Disables a Trunk - The

trunk behaves as if it is
not physically connected,
i.e., it enters mode of: no
transmit on that Trunk.
Use to change the
transmission state of the
PSTN physical device.
Enable, Disable (Tri state)
or Send Blue Alarm.
0 = Trunk Enabled
1 = Trunk Disabled
0 or 1
The DPNSSBehavior
parameter represents a
Bit field parameter. Each
bit represents a specific
type of DPNSS behavior.
Currently only the first 2
bits are in use.
See Descr.
ini File Field Name
Description
DisableTrunkAfterReset
DPNSSBehavior
DPNSS_BEHAV_STOP_
SABMR_AFTER_NL_AN
D_NT1 bit: (bit #0, bit
mask 0x0001)
When set to 1: DPNSS
stops repeating SABMR
after NL and NT1 limits
are exceeded.
When set to 0: DPNSS
continues repeating
SABMR after NL and NT1
limits are exceeded.
Default is 0 (continue
repeating SABMR)
DPNSS_BEHAV_FULL_S
TARTUP_SUCCESS bit:
(bit #1, bit mask 0x0002)
When set to 1: the Startup
Procedure is considered
as a SUCCESS only
when ALL DLCs
succeeded to Reset;
When set to 0: the Startup
Procedure is considered
as a SUCCESS as soon
as 1 DLC succeeded to
Reset;
Default is 0: (only partial
reset is considered as a
success).
Version 4.8
349
January 2006
Mediant 3000

Host/Manual
Default Value
ini File Field Name
Description
FramingMethod
Selects the physical

framing method used for
this trunk.
0 = default according to
protocol type E1 or T1
[E1 default = E1 CRC4
MultiFrame Format
extended G.706B (as c)]
[T1 default = T1 Extended
SuperFrame with CRC6]
0 = E1 Extended
SuperFrame Format (E1
default)
1 = T1 SuperFrame
Format (T1 default)
a = E1 DoubleFrame
Format
b = E1 CRC4 MultiFrame
Format
c = E1 CRC4 MultiFrame
Format extended G.706B
A = T1 4-Frame
multiframe
C = T1 Extended
SuperFrame without
CRC6
F = J1 Extended
SuperFrame with CRC6
(Japan)
See Descr.
0, 1, a, b, c, A, C,
F
ISDNDuplicateQ931BuffMo
de
Activates / de-activates
delivery of raw Q.931
messages. Refer to the
VoPLib documentation
('ISDN Flexible Behavior').
0 to 255
ISDNGeneralCC
Behavior
This is the bit-field used to

determine several general
ISDN behavior options.
Refer to the VoPLib
documentation (ISDN
Flexible Behavior).
See Descr.
ISDNIBehavior
Bit-field used to determine

several behavior options,
which influence how the
Q.931 protocol behaves.
Refer to the VoPLib
documentation (ISDN
Flexible Behavior).
See Descr.
User's Manual
350
Valid Range
User's Manual

Host/Manual
Default Value
Valid Range

determine several
behavior options that
influence how the ISDN
Stack INCOMING calls
behave. Refer to the
(ISDN Flexible Behavior).
See Descr.
ISDNNFASInterfaceID
Defines the Interface ID.

Works with
NS_EXPLICIT_INTERFA
CE_ID. Refer to the
VoPLib
documentation(ISDN
Flexible Behavior).
Default = (unsigned char)
-1.
See Descr.
0 to 255
ISDNOutCallsBehavior

determine several
behavior options that
influence how the ISDN
Stack OUTGOING calls
behave. Refer to the
(ISDN Flexible Behavior).
See Descr.
IUAInterfaceID
Defines the IUA trunk

interface ID value unsigned integer - in RFC
3057 - SIGTRAN.
0xFFFFFFFF
LineBuildOut.
OVERWRITE
Used to overwrite the

Framer's XPM registers
values (these registers
control the line pulse
shape).
0 = No overwrite;
1 = Overwrite
0 or 1
LineBuildOut.LOSS
Use to select the line build

out loss to be used for this
trunk.
0 = 0 dB
1 = 7.5 dB
2 = 15 dB
3 = 22.5 dB
0 to 3
ini File Field Name
Description
ISDNInCallsBehavior
Version 4.8
351
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
Used to control the

Framer's XPM0 register
value (line pulse shape
control).
Applicable only when
TrunkConfig.LineBuildOut.
Overwrite=1.
Should be used only by
expert users.
0 to 255
LineBuildOut.XPM1
Used to control the

control).
Overwrite=1.
expert users.
0 to 255
LineBuildOut.XPM2
Used to control the

control).
Overwrite=1.
expert users.
0 to 255
LineCode
Use to select line code.

B8ZS or AMI for T1 spans
and HDB3 or AMI for E1
spans.
0 = Use B8ZS line code
(for T1 trunks only =
default)
1 = Use AMI line code (for
T1 or E1 trunks)
2 = Use HDB3 line code
(for E1 trunks only)
0 to 2
ini File Field Name
Description
LineBuildOut.XPM0
Not applicable for TP6310
User's Manual
352
User's Manual

Host/Manual
Default Value
Valid Range
Relevant only to T1 ISDN

NFAS trunks, this
parameter indicates the
group number of the
NFAS group.
Valid NFAS group
numbers are only 1 to 4. 0
indicates that this trunk is
not NFAS (in this case the
parameters ISDN NFAS
Interface ID and Dch
Config are ignored).
0 to 4
Use to set the PSTN

protocol to be used for
this trunk. Relevant only
when
TDMBusType=acFRAME
RS (2).
Either:
NONE = 0
E1_EURO_ISDN = 1
T1_CAS = 2
T1_RAW_CAS = 3
T1_TRANSPARENT = 4
E1_TRANSPARENT_31
=5
E1_TRANSPARENT_30
=6
E1_MFCR2 = 7
E1_CAS_R2 = 8
E1_RAW_CAS = 9
T1_NI2_ISDN = 10
T1_4ESS_ISDN = 11
T1_5ESS_9_ISDN = 12
T1_5ESS_10_ISDN = 13
T1_DMS100_ISDN = 14
J1_TRANSPARENT = 15
T1_NTT_ISDN = 16
E1_AUSTEL_ISDN = 17
E1_HKT_ISDN = 18
E1_KOR_ISDN = 19
T1_HKT_ISDN = 20
E1_QSIG = 21
E1_TNZ_ISDN = 22
T1_QSIG = 23
V5_2_AN = 26
T1_IUA = 28
E1_IUA = 29
T1_EURO_ISDN = 34
T1_DMS100_MERIDIAN_
ISDN = 35
See Descr.
ini File Field Name
Description
NFASGroupNumber
ProtocolType
Version 4.8
353
January 2006
Mediant 3000

ini File Field Name
Description
Host/Manual
Default Value
Valid Range
See Descr.
0 or 1
E1_DUA = 37
T1_NI1_ISDN = 36
Q931RelayMode
Activates / de-activates
the ISDN level 3 Q.931
Relay Mode. Choose 0 or
ActivateLAPDmessaging
or
Q931_RELAY_TO_HOST
or Layer3_IS_IUA.
SDHFbrGrpLpMapping
Type
Selects the Low Path

mapping type (TU/VT
signal label + payload
maping type) for the
PSTN interface, generally
per Fiber Group. Single
Fiber Groups are
supported in the PSTN
interface of TP6310.
Relevant only when
TDMBusType=acFRAME
RS (2).
0 = Asynchronous VT1.5
and DS1
1 = Asynchronous TU12
and E1
15 = Undefined
Should be in coordination
with other parameters as
follows: SDHFbrGrp_LP_Mapping
_Type
- ProtocolType
For more details, refer to
the
SDHFbrGrpSdhSonetMod
e parameter description.
Applicable only to TP6310
SDHFbrGrpProtected
Set to true (1) to activate

APS (Automatic
Protection Switching)
mechanism on PSTN
interface, generally per
Fiber Group. Single Fiber
Groups are supported in
the PSTN interface of
TP6310.
0 = APS not activated
1 = APS activated
User's Manual
354
User's Manual

ini File Field Name
Description
Host/Manual
Default Value
Valid Range
TP-6310 Only
SDHFbrGrpSdhSonet
Mode
Selects SDH / SONET

mode for the PSTN
interface, generally per
Fiber Group. Single Fiber
Groups are supported in
the PSTN interface of TP6310. Relevant only
when
TDMBusType=acFRAME
RS (2).
0 = Unknown
1 = STM1
2 = OC3
Should be in coordination
with other parameters as
follows: SDHFbrGrp_LP_Mapping
_Type- ProtocolType
When STM1 mode is
selected, please use
SDHFbrGrp_LP_Mapping
_Type = 1 (VC12) and
ProtocolType for E1.
When OC3 mode is
selected, please use
SDHFbrGrp_LP_Mapping
_Type = 0 (VT1.5) and
ProtocolType for DS1.
TP-6310 only
See Descr.
TDMBusPSTNAutoClockEn
able
Use to enable or disable

the PSTN trunk autofallback clock feature.
0=
PSTN_Auto_Clock_Disabl
e
1=
PSTN_Auto_Clock_Enabl
e
0 or 1
TP-6310/T3 Only
Not relevant for TP6310/SDH
Version 4.8
355
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
Define static TDM hairpinning (cross-connection)

to be performed at
initialization. Connection
is between trunks with
option to exclude a single
B-Channel in each trunk.
Format example: T0T1/B3,T2-T3,T4-T5/B2.
NULL
See Descr.
TerminationSide
Use to set the ISDN

Termination to either User
or Network. Termination =
For ISDN only.
0 = User side
1 = Network side
0 or 1
TraceLevel
Defines the Trace level:

acNO_TRACE = 0
acFULL_ISDN_TRACE =
1
acLAYER3_ISDN_TRAC
E=2
acONLY_ISDN_Q931_M
SGS_TRACE = 3
acLAYER3_ISDN_TRAC
E_NO_DUPLICATION = 4
acFULL_ISDN_TRACE_
WITH_DUPLICATION = 5
acISDN_Q931_RAW_DA
TA_TRACE = 6
acISDN_Q921_RAW_DA
TA_TRACE = 7
acISDN_Q931_Q921_RA
W_DATA_TRACE = 8
acSS7_MTP2 = 10
acSS7_MTP2_AND_APP
LI = 11
acSS7_MTP2_SL_L3_NO
_MSU = 12
acSS7_AAL = 15
0 to 15
TrunkAdministrativeState
Defines the administrative

state of a trunk.
0 = Lock the trunk; stop
trunk traffic to configure
the trunk protocol type
2 = Unlock the trunk;
enable trunk traffic
0 or 2
ini File Field Name
Description
TDMHairPinning
User's Manual
356
User's Manual

ini File Field Name
Description
TrunkLifeLineType

define the type of trunk
lifeline. Short trunks 1-2,
3-4.
0 = Activate lifeline on
power down
power down or on
detection of LAN
disconnect
power down or on
detection of LAN
disconnect or loss of ping
Host/Manual
Default Value
Valid Range
0 to 2
Mediant 1000 Only
13.1.5
13.1.6
SDH/SONET Configuration
This section is only relevant for PSTN STM-1 / OC-3 ports in TP-6310.
The board supports both STM-1 and OC-3 transmission modes. The mode is
determined by ini file parameter SDHFBRGRP_SDHSONETMODE (1: STM-1, 2:
OC-3)
The Tributary Types supported are VC12 in STM-1 and VT1.5 in OC-3. These
types are selectable by ini file parameter SDHFBRGRP_LP_MAPPING_TYPE
(0: VT1.5, 1: VC12)
The board supports the following two working modes (selected by the two
parameters described above):
13.1.6.1
Mapping of E1s into VC12s and than multiplexing of 63 VC12 into an STM-1
frame
Mapping of T1s into VT1.5s and multiplexing of 84 VT1.5 into an OC-3 frame
The board supports Trunk Numbering in TPNCP and H.248: When working in
STM-1, trunk numbers are in the range of 0 to 62 (E1s) and in OC-3, from 0 to
83 (T1s). Trunks are numbered according to ETSI EN 300 417-1-1, Annex D
recommendation.
E1 Trunk Enumeration
The following table is used for converting internal STM-1 (KLM) numbering to
sequential trunk numbering for API references. The 3 numbers - TUG3, TUG2 and TU
- set the position of the E1 (V-12) trunk inside the STM-1 frame.
Version 4.8
357
January 2006
Mediant 3000
Table 13-5: STM-1 Numbering Conversion Table

TUG3
TUG2
TU
Trunk Number
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
User's Manual
358
User's Manual
Table 13-5: STM-1 Numbering Conversion Table

TUG3
TUG2
TU
Trunk Number
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
Version 4.8
359
January 2006
Mediant 3000
13.1.6.2
T1 Trunk Enumeration
The following table is used for converting internal OC3 numbering to sequential trunk
numbering for API references. The 3 numbers - STS-1, TUG2 and TU - set the
position of the T1 (V-1.5) trunk inside the OC3 frame.
Table 13-6: OC3 Numbering Conversion Table

STS-1
VT-Group
VT
Trunk Number
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
User's Manual
360
User's Manual

STS-1
VT-Group
VT
Trunk Number
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
Version 4.8
361
January 2006
Mediant 3000

STS-1
VT-Group
VT
Trunk Number
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
13.1.7
SS7 Parameters
The table below lists and describes the SS7 parameters contained in the ini file. Use
Table 13-7: SS7 Parameters

Host/Manual Valid
Default Value Range
ini File Field Name
Description
SS7_MTP2_Param_AERM_TI
E
Defines the SS7 alignment emergency

error rate threshold.
0 to 10
SS7_MTP2_Param_AERM_TI
N
Defines the SS7 alignment normal

error rate threshold.
0 to 20
User's Manual
362
User's Manual
ini File Field Name
Host/Manual Valid
Default Value Range
Description
SS7_MTP2_Param_Error_Cor Defines the SLI error correction

rection_Method
method.
0, B or P
0 = no error correction
B = Basic
P = PCR (Preventive Cyclic
Retransmission)
SS7_MTP2_Param_IAC_CP
Defines the number of aborted proving

attempts before sending an out-ofservice to MTP-3.
0 to 10
SS7_MTP2_Param_Link_Rat
e
Defines the SS7 SLI Link Rate.
0, A or D
Choose either:
0 = link not active
A = 64 kbps
D = 56 kbps
SS7_MTP2_Param_LSSU_Le
ngth
Defines the SS7 MTP2 LSSU length

as 1 or 2 (bytes).
1 to 2
SS7_MTP2_Param_Octet_Co
unting
Defines the SS7 MTP2 Octet received

while the octet is in counting mode (#
of Octets received - N Octets - while in
Octet counting mode).
16
0 to 256
SS7_MTP2_Param_PCR_N2
Defines the Preventive Cyclic

Retransmission - the number of
message signal unit octets available
for retransmission (ITU-T Q703 6.4 Forced retransmission).
200
0 to 512
SS7_MTP2_Param_SUERM_
SU_D
Defines the SS7 Signal Unit error rate

monitor D threshold.
256
0 to 256
SS7_MTP2_Param_SUERM_
T
Defines the SS7 SUERM (Signal Unit

Error Rate Monitor) T threshold.
64
0 to 256
SS7_MTP2_Param_Timer_T1
Defines the SS7 MTP2 T1 alignment

ready timer (in msecs).
50000
0 to
100000
Defines the SS7 MTP2 T2 unaligned

timer (in msecs).
150000
0 to
200000
Defines the SS7 MTP2 T3 timer

aligned.
2000
0 to 20000
E
Defines the SS7 MTP2 T4e

Emergency proving period timer
(msec).
500
0 to 5000
N
Defines the SS7 MTP2 T4n Nominal

proving period timer.
8200
0 to 15000
Defines the SS7 MTP2 Sending SIB
120
0 to 2400
Version 4.8
363
January 2006
Mediant 3000
ini File Field Name
Host/Manual Valid
Default Value Range
Description
timer.
Defines the SS7 MTP2 Remote

Congestion timer (in msec).
6000
0 to 10000
Defines the SS7 MTP2 excessive

delay of the ack timer (in msec).
2000
0 to 5000
SS7MTP3RdcyBoardNum
Defines the board number for the

Signaling System 7 (SS7) MTP3-User
Adaptation Layer redundancy mode.
Each board is allocated a unique
number. All boards share a single
redundancy table.
See Descr
0 or 1
0, 2, 4
0 to MAX_RDCY_BOARDS
SS7MTP3RdundancyMode
Defines the Signaling System 7 (SS7)

MTP3-User Adaptation Layer
redundancy mode. Determines the
redundancy flavor.
0 = M3BRDCY_MODE_DISABLED,
1 = M3BRDCY_MODE_ENABLED
SS7MTP3RdundancyTransfer
Type
This is an MTP3-User Adaptation

Layer parameter of the Signaling
System 7 (SS7), used to define the
cross-board connection media type for
the redundancy feature.
0 = M3BRDCY_CONN_TYPE_NONE,
2 = M3BRDCY_CONN_TYPE_TCP,
4 = M3BRDCY_CONN_TYPE_MTP2
SS7MTP3RdcyBoardNum
13.1.8
This parameter is used to define the

board number for the Signaling
System 7 (SS7) MTP3 User
Adaptation Layer redundancy mode.
Each board is allocated a unique
number. All boards share a single
redundancy table.
0, 2, 4
Parameters Common to All Control Protocols

The table below lists and describes the parameters, contained in the ini file, that are
common to all call control protocols. Use this table as a reference when modifying ini
file parameter values.
User's Manual
364
User's Manual
Table 13-8: Control Protocol Parameters

Host/Manual
Default Value
Valid Range
Determines the media

gateway's initial administrative
state.
0 = Locked
1 = shuttingdown (read only)
2 = Unlocked
0 to 2
AdminStateLockControl
Defines the time remaining (in

seconds) for the shutdown to
complete.
0 = = immediate shutdown
-1 = waits until all calls drop
(infinite)
>0 = the number of seconds
to wait
-1
-1, 0, > 0
CallAgentDomainName
Defines a domain name to be

used to connect with the Call
Agent. The parameter takes
precedence over the Call
Agent IP and the provisioned
Call Agent parameters
NULL
String[63]
CallWaitingToneDuratio
n
Changes the call waiting

tones family duration, in
msec. Range: 300 to 300,000
msec
12000
See Descr.
CODERTBLFILENAME

name of an external coders
table. In this table, the user
can decide which coders will
be used in the system. The
original file is a text file, and it
is converted by DCONVERT
to a binary file.
""
String[63]
CPCipherSuiteType
Defines the default cipher

type for the control protocol:
0 = none
1 = TGCP
2 = SRTP
0 to 2
CPPlayAnnouncement
ToNetworkSide
This (MGCP-related)
parameter forces all
announcements to be played
towards the network side.
0 = Default TDM
1 = Network side
0 or 1
ini File Field Name
Description
AdminState
Version 4.8
365
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
Controls MGCP/MEGACO
functioning for SDP structure.
The current support is for
RFC 2327 and RFC 3108.
Every new RFC support
should be turned on or off with
this parameter.
Range: unsigned Integer > 0
Currently only value 1 is
supported, and when set it
turns on the support of RFC
3407 (simple capabilities)
See Descr.
CPTransportType
Defines the transport type for

the control protocol:
0 = UDP; 1 = TCP
0 or 1
CPTrunkIdOffset
Sets the trunk numbering

offset.
CPTRUNKIDOFFSET_2
sets first trunk number to 2.
0, >0
DefaultPacketization
Period
Defines the default

packetization period (Frame
Size).
Default = 20 msec
(for G.723 = 30)
20
5 to 80
DialToneDuration
Defines the timeout (in

seconds) for the dial tone
signal.
16
1 to 65535
DigitMapTimeoutTimer
Defines the timeout value (T

symbol) in a digit map, in
increments of 10. For
MEGACO, it's the start timer.
For the others, it's the end
timer.
16
1 to 65535
DTMFDigitLength
Defines time to play DTMF, in

msec.
100
0 to 65535
DTMFInterDigitInterval
Defines the time between

DTMFs played, in msec.
100
0 to 65535
EnableCallerIDTypeTw
o
Enables or disables Caller ID

Type 2. If Off (0), Caller ID
Type Two is not played (if
playing is requested from the
Call Agent).
0 = Off; 1 = On
0 or 1
ini File Field Name
Description
CPSDPPROFILE
User's Manual
366
User's Manual
ini File Field Name
Description
EndpointName
MGCP: Gateway's endpoint

name. This is a prefix used to
identify the endpoint, i.e.,
'ACgw' in the following
example:
'ACgw5@acl.com'.
MGCP Default: 'Acgw'
Host/Manual
Default Value
Valid Range
See Descr.
String[19]
MEGACO: Prefix of the

endpoint part of the
termination name
MEGACO Default: 'line' for
analog board and '/c' for
trunking boards.
EndpointPREFIX
MGCP: This parameter

generates (together with
parameter Trunk Name) a
local endpoint name on trunkenabled media gateways.
NULL
String[19]
GatewayName
Defines the media gateway's

identification name.
See Descr.
String[63]
MGCP: Gateway's
identification name towards
the MGCP Call Agent. If
undefined, the gateway name
holds the IP address of the
board.
MGCP Default:
AudioCodes.com
MEGACO: Prefix of the
gateway part of the
termination name.
MEGACO Default: NULL for
analog boards and 'tgw' for
trunking boards.
KeepAliveEnabled
This parameter can be used

to enable a KeepAlive
message (NOP
ServiceChange).
0 = disable; >0 = enable
0 or >0
KeepAliveInterval

define the interval in seconds
of a KeepAlive message.
12
1 to 300
MGControlProtocolType
Defines the control protocol

type. Choose either:
0 = None
1 = MGCP
0, 1, 2, 4, 8
Version 4.8
367
January 2006
Mediant 3000
ini File Field Name
Description
Host/Manual
Default Value
Valid Range
2 = MEGACO
4 = H.323
8 = SIP
MGCPCommunication
LayerTimeout
Assumed delay of the

communication layer. It is
used in retransmission. This
parameter defines the
maximal time to wait for a
response before declaring a
disconnection (in seconds).
30
>0
MGCPCompatibility
Profile
Controls MGCP/MEGACO
functioning for vendor-specific
compatibility. Refer to the
product's User's Manual or
the enumerator
mgTMGCPProfile for possible
values.
Integer > 0
MGCPDefault
PacketizationPeriod
Defines the default

packetization period (Frame
Size).
20
5 to 120
MGCPDefaultCoder
This parameter can be used

to set a default coder for
channel opening. For the legal
coder names, refer to the
product's User Manual.
Default =
cpDPT_G711Mulaw_Coder
G.711
See Descr.
MGCPDTMFDetection
Point
Defines if the detection of

DTMF events is notified at
end of DTMF or at start of
DTMF.
0 = at start of DTMF
1 = at the end of DTMF
0 or 1
MGCPRetransmission
Timeout
Controls protocols
retransmission timeout. Sets
the initial time (in msec) for
the first retransmission. The
retransmission intervals
thereafter increase
exponentially.
200
0 to 10000
MGCPRetransmition
Timeout
Sets the initial time for the first

retransmission. The
Retransmission intervals
thereafter increase
exponentially.
200
0 to 65535
User's Manual
368
User's Manual

Host/Manual
Default Value
Valid Range
Use this parameter to define a

list of up to 10 (MGCP) or 5
(MEGACO) legal IP
addresses separated by ',' or
';' for the ServiceChange
command. The gateway starts
connecting with the first and in
case of failure, attempts the
others.
Range: Legal IP Address
NULL
See Descr.
Ports
Use this parameter to define a

list of up to 10 (MGCP) or 5
(MEGACO) Call Agent UDP
ports separated by , or ; for
each Call Agent defined by
the parameter used to specify
the Allowed Call Agent
Address.
2944
0 to 65535
RadiusVSAAccess
Attribute
Defines the 'Security Access

Level' attribute code in the
VSA section of the Radius
packet that the device should
relate to.
35
0 to 0xFF
RadiusVSAVendorID
Defines the vendor ID that the

device should accept when
parsing a Radius response
packet. (Default is 5003)
Range = 0 to 0xFFFFFFFF
5003 = AUDC
See Descr.
RandomizeTransaction
ID
Defines if the transactions

produced by the board start
with a fixed or random
number.
1 = Randomize On
Refer also to the parameters
defining Transaction Id Range
and Transaction Id Base.
0 or 1
RedundantCallAgent
DomainName
Defines the redundant MGCP

Call Agent domain name.
Default = ' ' (empty string)
See Descr.
String[63]
RTCPInterval
Defines the time interval

between the adjacent RTCP
reports, in msec.
5000
0 to 65535
ini File Field Name
Description
Version 4.8
369
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
When using a G.729 coder

connection and SCE (Silence
Suppression Enable) is On, a
single SID packet is sent.
If set to 1 and the channel
was opened or modified to
operate with the G.729 coder
with Silence Suppression
when Silence is detected, only
a single SID packet is sent.
If set to 0, SID packets are
sent frequently, according to
energy changes that require a
SID packet for each change.
0 or 1
TransactionIDBase
Defines the minimum number

for the transaction ID.
Default = 2000
2000
>0
TransactionIDRange
Defines the range for the

transaction ID.
Default = 999999999
See Descr.
>0
TransparentCoder
PayloadType
Alternative payload type used

when using transparent coder.
116
0 to 127
TrunkName
MGCP: This parameter

generates (together with the
parameter defining the
Endpoint Prefix) a local
endpoint name on trunkenabled media gateways.
MGCP Default = ' ' (empty
string)
See Descr.
String[19]
NULL
See Descr.
ini File Field Name
Description
SingleSIDPacketWithS
CEG729
MEGACO: Prefix of the trunk

part of the termination name.:
MEGACO Default = ' ' for
analog boards and 's' for
trunking boards
TrunkTestURL
User's Manual
Defines the VXML trunk

testing URL.
Range = Any legal URL
TP-6310 Only
370
User's Manual
ini File Field Name
Description
USETransparentCoder
WithHBR
If this parameter is set to 1

and the connection uses HBR
(High Bit Rate) coders, the
DTMF transport type is set to
Transparent.
Coders list:
Host/Manual
Default Value
Valid Range
0 or 1
G711Alaw_64, G711Mulaw,
G726_16, G726_24,
G726_32, G726_40,
G727_16, G727_24_16,
G727_24, G727_32_16,
G727_32_24, G727_32,
G727_40_16, G727_40_24,
G727_40_32.
0 = Do not use
1 = Use
Note: The following parameter is to be supported in the next applicable release:
13.1.9
EnableCallerIDTypeTwo
MGCP-Specific Parameters
The table below lists and describes the MGCP-specific parameters contained in the
Table 13-9: MGCP Specific Parameters
ini File Field Name
Description
ActivateallChannelsOn
BoardInit
Activates (1) or deactivates (0) all

DSPs when the board is initialized.
Used in order to perform
signals/events operations prior to
CRCX.
0 = Deactivate
1 = Activate
Version 4.8
371
Host/Manual
Default Value
Valid Range
0 or 1
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
The Call Agent IP address, in dotted

notation, to be used for the initial
Restart in Progress (RSIP) message.
Set to 0.0.0.0 to avoid sending RSIP.
This parameter overrides the BootP
server's Call Agent IP address, if
provided.
NULL
See Descr.
CallAgentPort
Defines the Call Agent port number.

Defaults to the MGCP default port
number of 2427.
2427
0 to 65534
ClearRequestBuffer
0 = only an empty R: clears the

event list and only an empty S:
clears and stops the current signals
list.
Signals and events will be cleared
only when new signals/events are
requested or an empty
signals/events request is mentioned
in the command.
1 = if an encapsulated identifier (X:)
is present in the command, all TO
signals and all events are cleared.
0 or 1
ConnectionIDBase
Defines the lowest number for the

Connection ID values assigned by
the media gateway.
20
>0
ConnectionIDRange
Defines the range for the Connection

ID values assigned by the gateway.
Default = 999999999
See Descr.
>0
DefaultSecretKeyMetho
d
Sets the RTP RTCP default method

of key generation.
0 = base 64; 1 = Clear
0 or 1
Depopulatedchannels
Number
Enables the Call Agent to access

only a subset of the on-board
channel bank. Set to (-1) to use all
available channels.
Range = 0 to the maximum number
of channels in the board.
-1
See Descr.
ini File Field Name
Description
CallAgentIP
User's Manual
372
User's Manual

Host/Manual
Default Value
Valid Range
This parameter configures the option

to send piggy-backed commands
while RSIPS are sent; e.g., if the
event is triggered by the board and
RSIP was not sent yet, RSIP is sent
and piggy-backs the event along with
it, the call manager faces endpoint
restart and then the event. Default =
1 (piggy-back on)
0 = commands sent by gateway are
not piggy- backed.
1 = commands sent by gateway are
piggy-backed.
0 or 1
GatewayMGCPPort
Forces the media gateway to listen

to another UDP port instead of to the
original 2427, as defined in RFC
2705.
2427
0 to 65535
LongDurationEventTime
Defines the default time to trigger the

long duration event (in seconds).
3600
>0
MGCPEndPoint
NumberingOffset
Enables users to add an offset to

endpoints. This parameter functions
only with Endpoint Naming
configuration. Using this parameter
with Trunk Naming configuration is
disallowed, so use the
'TrunkIdOffset' parameter.
>0
MGCPNamingPattern
Defines the endpoint naming pattern

which represents the naming method
used by the gateway. Use of *
represents a number or wild card.
MGCP 1.0
String[39]
MGCPPersistentEvents
Lists the events to be used as

persistent events. The format is the
same as the requested event
parameter (R:), for example, 'D/
x(N)'.
See Descr.
String [127]
ini File Field Name
Description
EnablePiggyBacking
Default:
MP media gateways: 'L/hd,L/hu,L/hf'
Other devices: Empty
Version 4.8
373
January 2006
Mediant 3000

Host/Manual
Default Value
Valid Range
When this parameter exists in the ini

file, the generated RSIPs include the
media gateway's / board's MAC
address in addition to the regular
parameters.
This parameter is sent as an MGCP
extension parameter.
1 = Include the MAC address of the
media gateway / board
0 = Don't include the MAC address
of the media gateway / board
0 or 1
MGCPVersion
Defines the MGCP protocol version.
MGCP 1.0
String[39]
MGCPXUAMAKE
Defines the make part of x-ua

response according to RFC 3149.
The maximum length of this
parameter is 32 bytes.
0 = Disable: 1 = Enable
0 or 1
MGCPXUAMODEL
The model part of x-ua response

according to RFC 3149.
The maximum length of this
parameter is 32 bytes.
0 or 1
MGHistoryBufferTime
Lim
Defines the time that a transaction is

kept in the history buffer.
30
0&>0
QuarantineModeState
Sets the default quarantine handling

state. When set, the quarantine
handling state is set to LockStep. If
not set, it is set to Loop and Discard.
0 = Loop/Discard
1 = Lockstep
When enabled, the Quarantine
events are handled according to
RFC 2705. In non-quarantine
modes, a Notification is sent
immediately on event detection.
0 or 1
RedundantAgentIP
Defines the redundant Call Agent IP

address to be used for the initial
Restart in Progress message (RSIP).
Set to 0.0.0.0 to avoid sending RSIP.
Range = IP address in dotted format
notation
NULL
See Descr.
RedundantAgentPort
Defines the redundant Call Agent

port number.
Defaults to the MGCP default port
number of 2427.
2427
0 to 65534
ini File Field Name
Description
MGCPSendMACWith
RSIP
User's Manual
374
User's Manual

Host/Manual
Default Value
Valid Range
Specifies whether or not to send an

RSIP when the LAN is re-connected.
0 = Don't send RSIP
1 = Send RSIP
0 or 1
UseBRacketsWith
GatewayName
When the Gateway Name is defined

as an empty string and this
parameter is set to 1, the gateway
name takes the board IP address
with added brackets. i.e.,
[10.2.211.11].
0 = Off; 1 = On
0 or 1
UseNewFormatCoder
Negotiation
Disables the response of all coders

(and descriptions) that are returned
on execution of the CRCX (Create
Connection command) or MDCX
(Modify Connection command)
without a coder and SDP (Session
Description Protocol) included in the
command.
For detailed information, refer to
Coder Negotiation in RFC 3136.
0 = Do not use the new format
1 = Use the new format
0 or 1
UseRangeEndpointsWit
hRSIP
While parameter is set to 1 (default).

RSIPs are sent in range format e.g.,
"RSIP 1234 ACGw[ep1ep2]@AUDC.com".;if parameter is
set to 0 RSIP will be sent on each
endpoint.
On trunking gateways RSIPs are not
sent at all.
0 or 1
UseWildCardWithRSIP
When the wildcard is used, RSIPs

turn in a single message on
EndPoint Naming configuration and
Single message for each trunk in
Trunk Naming configuration. If Off
and the number of channels is less
than 64, an RSIP message is sent
for each Endpoint.
0 = Do not use; 1 = Use
0 or 1
ini File Field Name
Description
RSIPOnNetwork
Disconnection
13.1.10
MEGACO-Specific Parameters
The table below lists and describes the MEGACO-specific parameters contained in
the ini file. Use this table as a reference when modifying ini file parameter values.
Version 4.8
375
January 2006
Mediant 3000
Table 13-10: MEGACO Specific Parameters

Host/Manual
Default Value
Valid Range
Selects the profile for the

AAS package specification
standard.
0 = TD-51 standard
1 = H.248.9 standard
0 or 1
ATM_BIT_FIELD_SIZE
(For binary MEGACO)

Defines the bit field size for
each ATM termination name
level.
0 to 30
ATM_Num
Defines the starting number

for each ATM termination
level name.
Integer >0
AudioTermPattern
Defines the name pattern of

an audio termination.
Applicable to IPM-1610 and
TP-6310 only.
NULL
String[32]
BCTTermPattern
Defines the name pattern of a

BCT termination
TP-6310 only.
NULL
String[32]
ConferenceTermPattern

conference termination.
TP-6310 only.
NULL
String[32]
DigitMapName
Name of the provisioned digit

map.
NULL
String[10]
DIGITMAPPING
Defines the digit map patterns

separated by a vertical bar (|),
as defined in the MEGACO
RFC.
NULL
String[151]
EP_BIT_Field_Size
(For binary MEGACO)

each name level (level 0 is
the left one, i.e., the Trunk
number).
The total binary name is 32
bits long.
0 to 30
EP_Num

for each name level (level 0 is
the left one when looking at
the parameter defining Phys
Term Name Pattern). Thus, to
start trunk numbering from 1,
set EP_NUM_0 to 1.
Range: Any positive number
See Descr.
ini File Field Name
Description
AASPackagesProfile
User's Manual
376
User's Manual

Host/Manual
Default Value
Valid Range

an ATM termination.
NULL
String [30]
LogicalRTPTermPattern

an RTP termination.
For example: 'gw/rtp/*'. The '*'
sign stands for the actual
number of the RTP
termination.
NULL
String [30]
MEGACO_MID
Defines media gateway's MID

towards the MGCP/MEGACO
Call Agent. If empty or illegal,
the MID holds the IP address
of the board
NULL
String[64]
MEGACOASN1Profile
Used to profile the binary

ASN.1 encoding. Refer to the
product's User's Manual for
possible values.
Integer >0
MEGACOCheckLegality
OfMGC
This parameter is specified if

MEGACO rejects commands
from an MGC not in the
provisioned list.
1 = Reject, don't check
0 = Check
0 or 1
MEGACOContextID
Offset
Offset for the context ID

generated by the gateway.
e.g., offset = 100 causes the
first context to be 101.
Range = 0 to 4294967295
See Descr.
MEGACOEncoding
Sets the MEGACO coding

method.
1 = Support MEGACO
protocol's binary ASN.1
format
0 = Text mode
0 or 1
MEGACOProvisioned
AudioSize
Defines the provisioned audio

size indicated by parameter
X-PtEngr.
TP-6310 only.
60
1 to 65535
MEGACOProvisioned
BCTSize
Provisioned BCT size

indicated by parameter XPtEngr.
TP-6310 only.
60
1 to 65535
MEGACOProvisioned
ConfSize
Provisioned conference size

indicated by parameter XPtEngr.
60
1 to 65535
ini File Field Name
Description
LogicalATMTermPattern
Version 4.8
377
January 2006
Mediant 3000
ini File Field Name
Description
Host/Manual
Default Value
Valid Range
The value is dynamically

limited according to the
number of DSP channels and
the used feature key.
TP-6310 only.
MEGACOProvisioned
TrunkTestingSize
Defines the provisioned TT

(trunk testing) size indicated
by the parameter X-PtEngr.
TP-6310 only.
60
1 to 65535
MEGACOTerminationID
Offset
Offset for the ephemeral

termination IDs in the
gateway.
e.g., offset = 100 causes the
first ephemeral termination ID
to be 101.
Note: This parameter was
replaced by the parameter
'RTP_Num'.
Range = 0 to 4294967295
See Descr.
MEGACOTrunkIDOffset
Sets the offset to the trunk

numbering.
e.g., Offset = 2 causes the
first trunk number to be 2.
Note: This parameter was
replaced by the parameter
'EP_NUM'.
Range: 0 to 4294967295
See Descr.
MGCExecutionTime
Defines the estimated

execution time of the MGC (in
msec).
100
0 to 2000
MGCProvisional
ResponseTime
Defines the provisional

response timer for the MGC
(in msec).
100
0 to 20000
MGExecutionTime
Defines the estimated

execution time of the media
gateway (in msec).
100
0 to 2000
MGProvisionalRespons
eTime
Defines the provisional

response timer for the media
gateway (in msec).
100
0 to 20000
PhysTermNamePattern

physical termination.
For Example: 'tgw/t*/c*'. The
'*' sign stands for the actual
numbers of the trunk and Bchannel.
NULL
String [30]
User's Manual
378
User's Manual

Host/Manual
Default Value
Valid Range
(For binary MEGACO)

each RTP termination name
0 to 30
RTP_Num

for each name's RTP
termination level (level 0 is
the left one, i.e., the Trunk
number).
Range: Any positive number
See Descr.
TrunkTestTermPattern

trunk test termination.
TP-6310 only.
NULL
String[32]
ini File Field Name
Description
RTP_BIT_Field_Size
13.1.11
Web Interface Parameters

The table below lists and describes the Web Interface parameters contained in the ini
file. Use this table as a reference when modifying ini file parameter values.
Table 13-11: Web Interface Parameters

Host/Manual
Default Value
Valid
Range
Changes an AudioCodes Web

background image to the user
background image, by loading
a GIF/JPEG file.
Notes:
1. Background height should
be 85 pixels.
2. Background image is
duplicated alongside to fit the
screen width.
NULL
String[47]
HTTPPort
Determines the local HTTP

port of the device.
Range = 1 to 65535 (other
restrictions may apply in this
range)
80
See Descr.
HTTPSCertFileName
Defines the name of the

HTTPS server certificate file
to be downloaded via TFTP.
The file must be in base64encoded PEM format.
NULL
String[47]
ini File Field Name
Description
BKGImageFIleName
Version 4.8
379
January 2006
Mediant 3000

Host/Manual
Default Value
Valid
Range
Defines the Cipher string for

HTTPS (in OpenSSL cipher
list format).
Refer to URL
http://www.openssl.org/docs/a
pps/ciphers.html
Range = EXP, RC4
See Descr.
HTTPSOnly
Use this parameter to allow

only HTTPS connections
(force security). When set to
1, unencrypted HTTP
(normally, port 80) is blocked.
0 or 1
HTTPSPORT
Determine the local Secure

HTTPS port of the device.
The default port is 443.
Range = 1 to 65535 (other
restrictions may apply in this
range)
443
See Descr.
HTTPSRequireClientCertifi
cate
Requires client certificates for

HTTPS connection. The client
certificate must be preloaded
on the gateway, and its
matching private key must be
installed on the managing
computer. Time and date
must be correctly set on the
gateway, for the client
certificate to be verified.
0 to 1
HTTPSRootFileName
Defines the name of the

HTTPS trusted root certificate
file to be downloaded via
TFTP. The file must be in
base64-encoded PEM format.
NULL
String[47]
LogoFileName
GIF/JPEG image file name to

replace the AudioCodes Web
logo image appearing in the
upper left hand corner of the
device web interface pages.
(Note: Image height should be
85 pixels.)
NULL
String[47]
LogoWidth
Defines the logo image (upper

left hand corner of web
interface pages) width in pixel
units.
Range = Up to 9999 pixels
441
See Descr.
ini File Field Name
Description
HTTPSCipherString
User's Manual
380
User's Manual

Host/Manual
Default Value
Valid
Range
Activates the
userProductName parameter.
1 = On - Enables the
userProductName string to
override any AudioCodes
defaults.
0 = Off - userProductName
string has no effect on the
product name.
0 or 1
UseRProductName
A string of characters to
replace the default
AudioCodes product name
appearing in the upper right
hand corner of the device web
interface pages.
NULL
String[29]
UseWeblogo
Enables the webLogoText

string to override any loaded
logo image file.
1 - Enables the webLogoText
string to override any loaded
logo image file (and
AudioCodes default logo
image).
0 - The webLogoText string
has no effect on the logo
image.
0 or 1
WEBACCESSLIST
Allows IP addresses to
connect to the Web interface.
Set to zeroes to allow all IP
addresses.
Range: Valid IP address
0.0.0.0
See Descr.
WebAuthMode
Selects HTTP basic (clear

text) or digest (MD5)
authentication for the web
interface.
0 = basic authentication (clear
text) is used.
1 = digest authentication
(MD5)is used.
2 = digest authentication
(MD5) is used for HTTP, while
basic authentication is used
for HTTPS.
Note that turning on RADIUS
login forces basic
authentication.
0 to 2
ini File Field Name
Description
UseProductName
Version 4.8
381
January 2006
Mediant 3000

Host/Manual
Default Value
Valid
Range
Replaces the default

AudioCodes logo image,
appearing in the upper left
hand corner of the device web
interface pages, with a text
string.
Note: This string will also
replace the AudioCodes name
in the title bar.
NULL
String[15]
Uses the RADIUS (Remote

Authentication Dial-In User
Server/Service) for Web
interface authentication.
Make sure that
ENABLERADIUS is on.
Use of this parameter without
HTTPSONLY = 1 is not
recommended.
0 or 1
ini File Field Name
Description
WebLogoText
WEBRADIUSLOGIN
13.1.12
SNMP Parameters
The table below lists and describes the SNMP parameters contained in the ini file.
Table 13-12: SNMP Parameters

Host/Manual
Default Value
Valid Range
Enables a row in the SNMP

Managers table.
0 or 1
SNMPManagerTableIP
Used to define the SNMP manager

server IP address. This is the
tabular version of the parameter
defining SNMP Manager IP.
String[15]
SNMPManagerTrap
SendingEnable
Enables the SNMP Manager's IP

address for traps to be sent to it.
0 or 1
SNMPManagerTrapPort
Sets the trap ports to be used by

the different managers.
This parameter is the tabular
version of the parameter defining
SNMP Trap Port
162
100 to
65534
ini File Field Name
Description
SNMPManagerIsUsed
User's Manual
382
User's Manual
Table 13-12: SNMP Parameters

Host/Manual
Default Value
ini File Field Name
Description
SNMPPort
This parameter specifies the port

number for SNMP requests and
responses. Generally, it isn't
specified and the default is used.
161
100 to
65534
SNMPREADONLY
COMMUNITYSTRING
Used to define a read-only

community string.
Default =
DEFAULT_READONLY_COMMUN
ITY_STRING
See Descr.
String[19]
SNMPREADWRITE
COMMUNITYSTRING
Used to define a read-write

community string.
Default =
DEFAULT_READWRITE_COMMU
NITY_STRING
See Descr.
String[19]
SNMPTRAP
COMMUNITYSTRING
Defines the community string used

in traps.
Default =
DEFAULT_TRAP_COMMUNITY_S
TRING
See Descr.
String[19]
SNMPTrapManagerHos
tName
Defines a FQDN of a remote host

that is used as an SNMP Manager.
The resolved IP address replaces
the last entry in the trap manager
table (defined by the parameter
SNMPManagerTableIP_x) and the
last trap manager entry of
snmpTargetAddrTable in the
snmpTargetMIB.
For example:
'mngr.corp.mycompany.com'.
NULL
String [99]
SNMPTRUSTEDMGR
Defines the IP address of a trusted

SNMP manager.
Default = 0.0.0.0
See Descr.
String[15]
13.1.13
Valid Range
Voice Streaming Parameters

The table below lists and describes the Voice Streaming parameters contained in the
Version 4.8
383
January 2006
Mediant 3000
Table 13-13: Voice Streaming Parameters

Host/Manual
Default Value
ini File Field Name
Description
EnableVoiceStreaming
Enables/disables HTTP and NFS

voice streaming. When enabled, the
module requires some system
resources, such as tasks and
memory allocation.
Valid
Range
0 or 1
0 or 1
VoiceStreamUploadMethod
Defines the HTTP request type for

uploading the voice stream to the file
server.
0 = POST; 1 = PUT
VoiceStreamUploadPostUri
13.1.14
Defines the URI used on the POST

request, to upload voice data from
the media server to a Web server.
SCTP Parameters
The table below lists and describes the SCTP parameters contained in the ini file. Use
Table 13-14: SCTP Parameters

Host/Manual
Default Value
Valid Range
Defines the maximum number

of Stream Control
Transmission Protocol
(SCTP) associations that can
be opened.
1 to 8
SCTPPortsNum

of SCTP endpoints that can
be opened.
1 to 5
SCTPDNetNum

of association transport
addresses that can be active.
1 to 3
SCTPISTRMNum

of incoming streams.
10
1 to 200
SCTPOSTRMNum

of outgoing streams.
10
1 to 200
SCTPOutChunksNum

of outgoing chunks
630
50 to 630
ini File Field Name
Description
SCTPAssociationsNum
User's Manual
384
User's Manual
Table 13-14: SCTP Parameters

Host/Manual
Default Value
Valid Range

of SCTP association
retransmission attempts.
10
5 to 20
SCTPMaxAssocInit
Attempts

of SCTP association
initialization attempts.
5000
5 to 10000
SCTPHBInterval
Defines the SCTP heartbeat

interval.
30
1 to 3600
SCTPT4SAckTimer
Defines the SCTP T4 SACK

timer interval.
1 to 5
SCTPMaxDataChunk
Size
Defines the maximum length

of SCTP data chunks.
500
50 to 1504
SCTPChecksumMethod
Stream Control Transmission

Protocol (SCTP) uses a
checksum mechanism in
order to authenticate packets
on both sides (the receiving
side and the transmitting
side).
Presently, two checksum
mechanisms are available:
0 = adler32 checksum
mechanism
1 = crc32c checksum
mechanism (improved
mechanism)
0 or 1
SCTPHOSTNAME
When this parameter is set to

any value other than an empty
string, SCTP (Stream Control
Transmission Protocol) uses
the value as the value of the
FQDN (Fully Qualified
Domain Name) parameter
attached to the INIT chunk. In
this case, the FQDN
parameter replaces any IP
address parameters in the
INIT chunk.
This feature enables
overcoming NAT problems
where the original IP
addresses belonging to the
endpoint supports are
converted into pseudo
addresses. When this
parameter is not set (default),
the INIT chunk is sent without
any FQDN parameter
NULL
String[42]
ini File Field Name
Description
SCTPMaxAssocRet
Version 4.8
385
January 2006
Mediant 3000
13.1.15
VoATM Parameters
The table below lists and describes the VoATM parameters contained in the ini file.
Table 13-15: VoATM Parameters

Host/Manual
Default Value
ini File Field Name
Description
ATMtransmissionMode
Determines the ATM port mode.

0 = SDH
1 = SONET
Valid
Range
0, 1
1 to 3
SB-6310, TP-6310, M3K Only

ATMApplicationType
Defines the ATM application type. This

parameter is used by H.248 to
determine which AAL (ATM Adaptation
Layer) to use for the call when the
H.248 command does not explicitly
specify the AAL layer.
1 = AAL1
2 = AAL2 (I.366.2)
3 = AAL2 (UMTS) (Default)
SB-6310, TP-6310, M3K Only
User's Manual
386
User's Manual
14. Appendix - Table Parameters
14
Appendix - Table Parameters
14.1
ini File Table Parameters

The following ini file Table Parameters are provided:
14.1.1
SS7 ini File Table Parameters

SS7 Table Parameters
"SS7 Signaling Nodes Table Parameters" below
'SS7 Signaling Node Timers Table Parameters' on page 387
'SS7 Signaling LinkSet Timers Table Parameters' on page 391
'SS7 Signaling Link Table Parameters' on page 392
'SS7 Signaling LinkSets Table Parameters' on page 395
'SS7 Signaling LinkSet-Links Table Parameters' on page 396
'SS7 RouteSets Table Parameters' on page 397
'SS7 RouteSet-Routes Table Parameters' on page 397
'SigTran Interface Groups Table Parameters' on page 398
'SigTran Interface IDs Table Parameters' on page 399
ATM Port Table Parameters
'ATM Port Table' on page 399
NFS Server Table Parameters
'NFS Server Table' on page 405
T3 Configuration Table Parameters
14.1.1.1
'T3 Configuration Table Parameters' on page 406
SS7 Signaling Nodes Table Parameters
Table 14-1: SS7 Signaling Nodes Table Parameters

ini File Field Name
Default Value
SS7_SN_INDEX
SS7_SN_NAME
"SN
Version 4.8
Valid Range
Description
0 to
Index Field for line
(MAX_SN_PER_CARD-1)
String name for SN
387
January 2006
Mediant 3000

ini File Field Name
SS7_SN_TRACE_
LEVEL
SS7_SN_OPERATIO
NAL_STATE
Default Value
Valid Range
Description
0 or 1
Trace level of signaling

node (level 3)
L3_OFFLINE
0-2
Operational state of
signaling node
0 = L3_OFFLINE
1 = L3_BUSY
2 = L3_INSERVICE
SS7_SN_MTC_BUS
Y_STATUS
0 or 1
Manual busy status of

signaling node
SS7_SN_
ADMINISTRATIVE_
STATE
L3_OFFLINE
0 or 2
Administrative state of
signaling node
0 = L3_OFFLINE
2 = L3_INSERVICE
SS7_SN_VARIANT
NET_VARIANT_ITU
0 to 3
Variant of signaling
node
1=
NET_VARIANT_ITU
2=
NET_VARIANT_ANSI
3=
NET_VARIANT_CHINA
SS7_SN_NI
NET_INDICATOR_INT
ERNATIONAL
0 to 3
Network Indicator of
signaling node
0 = INTERNATIONAL
1=
INTERNATIONAL_SPA
RE
2 = NATIONAL
3 = NATIONAL_SPARE
SS7_SN_SP_STP
SN_FUNCTION_IS_S
P
0 to 1
Routing function of
signaling node
0 = SP
1 = STP
SS7_SN_TFC
0 or 1
Currently not supported
SS7_SN_OPC
0 to 4294967295
Origination (local) pointcode of signaling node
SS7_SN_ROUTESE
T_CONGESTION_
WINSIZE
0 to 255
User's Manual
388
RouteSet Congestion
Size (messages) of
signaling node
User's Manual

ini File Field Name
Default Value
Valid Range
Description
Index of SNTimers
tables used for this
signaling node
SS7_SN_TIMERS_I
NDEX
0 to
(MTP3_SN_TIMER_SET
S-1)
SS7_SN_ISUP_APP
MTP3_NIL_APP
0 or 4
Level 4 application that

handles ISUP traffic for
this signaling node
0 = NIL
4 = UAL
SS7_SN_SCCP_AP
P
MTP3_NIL_APP
0 or 4

handles SCCP traffic
for this signaling node
0 = NIL
4 = UAL
SS7_SN_BISUP_AP
P
MTP3_NIL_APP
0 or 4

handles BISUP traffic
0 = NIL
4 = UAL
SS7_SN_ALCAP_AP
P
MTP3_NIL_APP
0,4 or 5

handles ALCAP traffic
0 = NIL
4 = UAL
5 = ALCAP
14.1.1.2
SS7 Signaling Node Timers Table Parameters
Table 14-2: SS7 Signaling Node Timers Table Parameters

ini File Field Name
Default Value
SS7_SNTIMERS_IN
DEX
SS7_SNTIMERS_NA
ME
"SN_Timers
SS7_SNTIMERS_T6
1200
Version 4.8
Valid Range
Description
0 to
(MTP3_SN_TIMER_SE
TS-1)
String name for SN

timer-set
500 to 4294967295
389
Delay to avoid message

mis-sequencing on
controlled rerouting
January 2006
Mediant 3000

ini File Field Name
Default Value
Valid Range
Description
SS7_SNTIMERS_T8
1200
500 to 4294967295
Transfer prohibited
inhibition timer (transient
solution)
SS7_SNTIMERS_T1
0
60000
500 to 4294967295
Waiting to repeat
signaling route set test
message
SS7_SNTIMERS_T1
1
90000
500 to 4294967295
Transfer restricted timer
SS7_SNTIMERS_T1
5
3000
500 to 4294967295
Waiting to start signaling

route set congestion test
SS7_SNTIMERS_T1
6
2000
500 to 4294967295
Waiting for route set

congestion status update
SS7_SNTIMERS_T1
8_ITU
20000
500 to 4294967295
Timer within a signaling

point whose MTP
restarts for supervising
link and link set
activation as well as the
receipt of routing
information
SS7_SNTIMERS_T1
9_ITU
67000
500 to 4294967295
Supervision timer during

MTP restart to avoid
possible ping-pong of
TFP, TFR and TRA
messages
SS7_SNTIMERS_T2
0_ITU
60000
500 to 4294967295
Overall MTP restart

timer at the signaling
point whose MTP
restarts
SS7_SNTIMERS_T2
1_ITU
65000
500 to 4294967295
Overall MTP restart

timer at a signaling point
adjacent to one whose
MTP restarts
SS7_SNTIMERS_T2
4_ITU
500
500 to 4294967295
Stabilizing timer after

removal of local
processor outage, used
in LPO latching to RPO
(national option)
SS7_SNTIMERS_T2
2_ANSI
180000
500 to 4294967295
Timer at restarting SP
waiting for signaling links
to become available
SS7_SNTIMERS_T2
3_ANSI
180000
500 to 4294967295
Timer at restarting SP,

started after T22, waiting
to receive all traffic
restart allowed
messages
User's Manual
390
User's Manual

ini File Field Name
Default Value
Valid Range
Description
SS7_SNTIMERS_T2
4_ANSI
5000
500 to 4294967295
with transfer function,
started after T23, waiting
to broadcast all traffic
restart allowed
messages
SS7_SNTIMERS_T2
5_ANSI
30000
500 to 4294967295
Timer at SP adjacent to
restarting SP waiting for
traffic restart allowed
message
SS7_SNTIMERS_T2
6_ANSI
12000
500 to 4294967295
waiting to repeat traffic
restart waiting message
SS7_SNTIMERS_T2
8_ANSI
3000
500 to 4294967295
Timer at SP adjacent to
restarting SP waiting for
traffic restart waiting
message
SS7_SNTIMERS_T2
9_ANSI
60000
500 to 4294967295
Timer started when TRA

sent in response to
unexpected TRA or
TRW
SS7_SNTIMERS_T3
0_ANSI
30000
500 to 4294967295
Timer to limit sending of

TFPs and TFRs in
response to unexpected
TRA or TRW
14.1.1.3
SS7 Signaling LinkSet Timers Table Parameters
Table 14-3: SS7 Signaling LinkSet Timers Table Parameters

ini File Field Name
Default Value
Valid Range
Description
0 to
(MTP3_LKSET_TI
MER_SETS-1)
SS7_LKSETTIMERS
_INDEX
SS7_LKSETTIMERS
_NAME
"SN_Timers
SS7_LKSETTIMERS
_T2SLT
30000
500 to
4294967295
Interval timer for sending

signaling link test messages
SS7_LKSETTIMERS
_T1
1000
500 to
4294967295
Delay to avoid message missequencing on changeover
SS7_LKSETTIMERS
_T2
2000
500 to
4294967295
Waiting for changeover

acknowledgement
Version 4.8
String name for SN timer-set
391
January 2006
Mediant 3000
Table 14-3: SS7 Signaling LinkSet Timers Table Parameters

ini File Field Name
Default Value
Valid Range
Description
SS7_LKSETTIMERS
_T3
1200
500 to
4294967295
Time controlled diversion-delay

to avoid mis-sequencing on
changeback
SS7_LKSETTIMERS
_T4
1200
500 to
4294967295
Waiting for changeback

acknowledgement (first attempt)
SS7_LKSETTIMERS
_T5
1200
500 to
4294967295
Waiting for changeback

acknowledgement (second
attempt)
SS7_LKSETTIMERS
_T7
2000
500 to
4294967295
Waiting for signaling data link

connection acknowledgement
SS7_LKSETTIMERS
_T12
1200
500 to
4294967295
Waiting for uninhibit

acknowledgement
SS7_LKSETTIMERS
_T13
1300
500 to
4294967295
Waiting for force uninhibit
SS7_LKSETTIMERS
_T14
3000
500 to
4294967295
Waiting for inhibition

acknowledgement
SS7_LKSETTIMERS
_T17
1500
500 to
4294967295
Delay to avoid oscillation of

initial alignment failure and link
restart
SS7_LKSETTIMERS
_T22_ITU
180000
500 to
4294967295
Local inhibit ITU test timer
SS7_LKSETTIMERS
_T23_ITU
180000
500 to
4294967295
Remote inhibit ITU test timer
SS7_LKSETTIMERS
_T20_ANSI
90000
500 to
4294967295
Local inhibit ANSI test timer
SS7_LKSETTIMERS
_T21_ANSI
90000
500 to
4294967295
Remote inhibit ANSI test timer
Table 14-4: SS7 Signaling Link Table Parameters

ini File Field Name
Default Value
SS7_LINK_INDEX
SS7_LINK_NAME
"LINK
SS7_LINK_OPERAT
IONAL_STATE
L3_OFFLINE
Valid Range
Description
0 to
(MAX_SIGNALIN
G_LINKS_PER_C
ARD-1)
String name for Link Params

0 to 2
Operational state of signaling

link
0 = L3_OFFLINE
User's Manual
392
User's Manual

ini File Field Name
Default Value
Valid Range
Description
1 = L3_BUSY,
2 = L3_INSERVICE
SS7_LINK_ADMINIS
TRATIVE_STATE
L3_OFFLINE
0 or 2
Administrative state of signaling

link
0 = L3_OFFLINE
2 = L3_INSERVICE
SS7_LINK_TRACE_
LEVEL
0 or 1
Trace level of signaling link

(level 2)
SS7_LINK_L2_TYP
E
SS7_SUBLINK_
L2_TYPE_NON
E
1 to 3
Link layer type - defines level 2

media of signaling link
1=
SS7_SUBLINK_L2_TYPE_MTP
2
2=
SS7_SUBLINK_L2_TYPE_M2U
A_MGC
3=
SS7_SUBLINK_L2_TYPE_SAA
L
SS7_LINK_L3_TYP
E
SS7_SUBLINK_
L3_TYPE_NON
E
1 to 3
Link high layer type - defines

level 3 or L2 high layer of
signaling link
1=
SS7_SUBLINK_L3_TYPE_M2U
A_SG
2=
3
3=
2_TUNNELING
SS7_LINK_TRUNK_
NUMBER
0 to
MAX_TRUNK_CA
PACITY - 1
Trunk number of signaling link

(TDM)
SS7_LINK_TIMESL
OT_NUMBER
16
0 to 31
Time-Slot number of signaling

link (TDM)
SS7_LINK_MTC_BU
SY
0 or 1
Link local busy indicator - if set,

indicates link is busy due to local
mtc action
SS7_LINK_INHIBITI
ON
L3_LINK_UNIN
HIBITED
0 or 1
Link inhibit indicator - if set,

indicates link is inhibited
Version 4.8
393
January 2006
Mediant 3000

ini File Field Name
Default Value
SS7_LINK_LAYER2
_VARIANT
NET_VARIANT_
ITU
Valid Range
1 to 3
Description
Variant (layer 2) of signaling link
(TDM)
1 = NET_VARIANT_ITU
2 = NET_VARIANT_ANSI
3 = NET_VARIANT_CHINA
SS7_LINK_MTP2_A
TTRIBUTES
0 to
MAX_C7_MTP2_
PARAMS_INDEX
MTP2 attributes of signaling link

(TDM)
SS7_CONGESTION
_LOW_MARK
0 to 255
Link congestion low mark of

signaling link (TDM)
SS7_CONGESTION
_HIGH_MARK
20
0 to 255
Link congestion high mark of

signaling link (TDM)
SS7_LINK_M2UA_I
F_ID
0 to 4294967295
Interface ID of signaling link
SS7_LINK_GROUP
_ID
0 to 0xFFFF
ATM_SAAL_LINK_P
ROFILE_NUM
0 to
MAX_SAAL_PRO
FILES
ATM SAAL Link profile number
ATM_SAAL_LINK_T
YPE
ATM_VCC_TYP
E_PVC
0 to 1
ATM SAAL link Type PVC/SVC
Group ID of signaling link
0 = ATM_UNI_LINK_TYPE
1 = ATM_NNI_LINK_TYPE
ATM_SAAL_LINK_P
ORT_NUM
0 to
ATMDB_ATM_MA
X_INTERFACES_
RANGE
ATM SAAL link port num
ATM_SAAL_LINK_V
PI
0 to 255
ATM SAAL link VPI
ATM_SAAL_LINK_V
CI
0 to 0xFFFF
ATM SAAL link VCI
SS7_LINK_TNL_MG
C_LINK_NUMBER
0
toMAX_SIGNALIN
G_LINKS_PER_C
ARD -1
SS7_LINK_TNL_ALI
GNMENT_MODE
M3B_ALIGNME
NT_EMERGEN
CY
0 to 255
MTP2 Tunneling: MGC link

number (MTP2 \other side\ of
signaling link
MTP2 Tunneling: Alignment
mode of signaling links in tunnel
0=
M3B_ALIGNMENT_NORMAL
1=
M3B_ALIGNMENT_EMERGEN
CY
User's Manual
394
User's Manual

ini File Field Name
Default Value
SS7_LINK_TNL_CO
NGESTION_MODE
M3B_CONGEST
ION_ACCEPT
Valid Range
0 to 255
Description
MTP2 Tunneling: Congestion
mode of signaling links in tunnel
0=
M3B_CONGESTION_ACCEPT
1=
M3B_CONGESTION_DISCARD
SS7_LINK_TNL_WA
IT_START_COMPL
ETE_TIMER
30000
500 to
4294967295
MTP2 Tunneling Timer: wait

start complete
SS7_LINK_TNL_OO
S_START_DELAY_
TIMER
5000
500 to
4294967295
MTP2 Tunneling Timer: OOS

start delay
SS7_LINK_TNL_WA
IT_OTHER_SIDE_IN
SV_TIMER
30000
500 to
4294967295
MTP2 Tunneling Timer: wait

other side inservice
14.1.1.4
SS7 Signaling LinkSets Table Parameters
Table 14-5: SS7 Signaling LinkSets Table Parameters

ini File Field Name
Default Value
Valid Range
Description
SS7_LINKSET_SN_I
NDEX
0 to
(MAX_SN_PER_C
ARD-1)
First Index Field for line
SS7_LINKSET_LINK
SET_INDEX
0 to
(MAX_LINKSETS
_PER_SN-1)
Second Index Field for line
SS7_LINKSET_NAM
E
"LINKSET
SS7_LINKSET_OPE
RATIONAL_STATE
L3_OFFLINE
String name for LinkSet Params

0 to 2

LinkSet
0 = L3_OFFLINE
1 = L3_BUSY,
2 = L3_INSERVICE
SS7_LINKSET_MTC
_BUSY_STATUS
0 or 1
Manual busy status of signaling

LinkSet
SS7_LINKSET_ADM
INISTRATIVE_STAT
E
L3_OFFLINE
0 or 2

LinkSet
Version 4.8
0 = L3_OFFLINE
395
January 2006
Mediant 3000
Table 14-5: SS7 Signaling LinkSets Table Parameters

ini File Field Name
Default Value
Valid Range
Description
2 = L3_INSERVICE
SS7_LINKSET_DPC
Destination Point-Code of
signaling LinkSet
SS7_LINKSET_MAS
K
15
0 to 255
Mask for links within signaling

LinkSet
SS7_LINKSET_ALT
ERNATE_MASK
240
0 to 255
Alternate mask for links within

signaling LinkSet
SS7_LINKSET_TIM
ERS_INDEX
0 to
(MTP3_LINKSET_
TIMER_SETS-1)
Timers Index of signaling

LinkSet
Table 14-6: SS7 Signaling LinkSet-Links Table Parameters
ini File Field Name
Default
Value
Valid
Range
Description
SS7_LINKSETLINK_SN_INDEX
0 to
(MAX_SN_
PER_CARD
-1)
First Index Field for line:

Signaling Node Number
SS7_LINKSETLINK_LINKSET_INDE
X
0 to
(MAX_LINK
SETS_PER
_SN-1)
Second Index Field for line:

Signaling LinkSet Number
SS7_LINKSETLINK_INNER_LINK_I
NDEX
0 to
(MAX_LINK
S_PER_LIN
KSET-1)
Third Index Field for line:

Inner Link Index in
Signaling LinkSet
SS7_LINKSETLINK_LINK_NUMBER
MTP3_LINK
_NIL
0 to
MAX_SIGN
ALING_LIN
KS_PER_C
ARD-1
Physical number of
signaling link which is part
of the LinkSet
0 to
MTP3_MAX
_SLC
Signaling Link Code of

signaling link which is part
of the LinkSet
SS7_LINKSETLINK_LINK_SLC
User's Manual
396
User's Manual
14.1.1.5
SS7 RouteSets Table Parameters
Table 14-7: SS7 RouteSets Table Parameters

ini File Field Name
Default Value
Valid Range
Description
SS7_ROUTESET_S
N_INDEX
0 to
(MAX_SN_PER_C
ARD-1)
First Index Field for line: Signaling

Node Number
SS7_ROUTESET_I
NDEX
0 to
(MAX_ROUTESE
TS_PER_SN-1)

Signaling RouteSet Number
SS7_ROUTESET_N
AME
"ROUTESET
SS7_ROUTESET_O
PERATIONAL_STA
TE
L3_OFFLINE
String name for RouteSet Params

0 to 2

RouteSet
0 = L3_OFFLINE
1 = L3_BUSY,
2 = L3_INSERVICE
SS7_ROUTESET_A
DMINISTRATIVE_S
TATE
L3_OFFLINE
0 or 23

RouteSet
0 = L3_OFFLINE
2 = L3_INSERVICE
SS7_ROUTESET_D
PC
SS7_ROUTESET_M
ASK
15
14.1.1.6
Destination Point-Code of
signaling RouteSet
0 to 255
Mask for routes within signaling

RouteSet
SS7 RouteSet-Routes Table Parameters
Table 14-8: SS7 RouteSet-Routes Table Parameters

ini File Field Name
Default Value
Valid Range
Description
SS7_ROUTESETRO
UTE_SN_INDEX
0 to
(MAX_SN_PER_C
ARD-1)
First Index Field for line:

Signaling Node Number
SS7_ROUTESETRO
UTE_ROUTESET_I
NDEX
0 to
(MAX_ROUTESE
TS_PER_SN-1)

Signaling RouteSet Number
SS7_ROUTESETRO
UTE_INNER_ROUT
E_INDEX
0 to
(MAX_LINKSETS
_PER_ROUTESE
Third Index Field for line: Inner

Route Index in Signaling
RouteSet
Version 4.8
397
January 2006
Mediant 3000
Table 14-8: SS7 RouteSet-Routes Table Parameters

ini File Field Name
Default Value
Valid Range
Description
T-1)
SS7_ROUTESETRO
UTE_LINKSET_NU
MBER
MTP3_LINKSET
_NIL
0 to
MAX_LINKSETS_
PER_SN-1
SS7_ROUTESETRO
UTE_PRIORITY
0 to 254
Number of signaling LinkSet

which is part of the RouteSet
Priority of route within RouteSet
Table 14-9: SigTran Interface Groups Table Parameters

ini File Field Name
Default Value
SS7_SIG_IF_GR_IN
DEX
0 to 7
65534
0 to 65535
SS7_SIG_SG_MGC
83
77(MGC), 83(SG)
SS7_SIG_LAYER
0 to 4
SigTran group layer (No layer,IUA,

M2UA, M3UA, M2TN)
SS7_SIG_TRAF_M
ODE
1 to 3
SigTran group traffic mode.
SS7_SIG_T_REC
2000
0 to 10000000
SigTran group T recovery
SS7_SIG_T_ACK
2000
0 to 10000000
SigTran group T Acknowledge
SS7_SIG_T_HB
2000
0 to 10000000
SigTran group T Heartbeat
SS7_SIG_MIN_ASP
1 to 10
SS7_SIG_BEHAVIO
UR
0 to 4294967294
SS7_SCTP_INSTAN
CE
65534
0 to 65534
SigTran group SCTP instance
SS7_LOCAL_SCTP
_PORT
65534
0 to 65534
SigTran group local SCTP port
SS7_SIG_NETWOR
K
1 to 3
SS7_DEST_SCTP_
PORT
65534
0 to 65534
0 to 4294967294
SS7_IF_GR_ID
SS7_DEST_IP
Valid Range
Description
SigTran group id
UAL group function
SigTran group minimal ASP number

SigTran group Behavior bit field
SigTran group Network

(ITU,ANSI,CHINA)
SigTran group destination SCTP port
SigTran group destination IP
Address
(Valid only for MGC or NAT
User's Manual
398
User's Manual
Table 14-9: SigTran Interface Groups Table Parameters

ini File Field Name
Default Value
Valid Range
Description
application)
SS7_MGC_MX_IN_
STREAM
2 to 65534
SigTran max number of SCTP

inbound streams
SS7_MGC_NUM_O
UT_STREAM
2 to 65534
SigTran max number of SCTP

outbound streams
Table 14-10: SigTran Interface IDs Table Parameters

ini File Field Name
Default Value
Valid Range
Description
SS7_SIG_IF_ID_IN
DEX
0 to 15
SS7_SIG_IF_ID_VA
LUE
0 to 4294967294
SS7_SIG_IF_ID_NA
ME
INT_ID
--
SigTran interface Id string name
SS7_SIG_IF_ID_O
WNER_GROUP
0 to 65534
SigTran interface Id owner group

field
SS7_SIG_IF_ID_LA
YER
0 to 5
SigTran interface Id layer

(NO_LAYER,IUA, M2UA, M3UA,
M2TN)
SS7_SIG_IF_ID_NAI
65534
0 to 65534
SigTran interface Id value field
SigTran interface Id NAI field

When SS7_SIG_IF_ID_LAYER
= M2UA, NAI is physical link
number.
When SS7_SIG_IF_ID_LAYER
= M3UA, NAI is SN number
SS7_SIG_M3UA_SP
C
14.1.2
0 to 4294967294
SigTran M3UA SN local point

code
ATM Port Table PARAMS

The following is a list of ATM ini File Table Parameters:
Version 4.8
ATM Port Table on page 400
ATM Port Loopback Table on page 400
ATM Remote Gateway Table on page 402
ATM AAL2 PVC Table on page 403

399
January 2006
Mediant 3000
14.1.2.1
ATM SVC Profile Table on page 404
ATM Port Table

This table provides the definition for all provisioned ATM ports. Through it, the current
administrative state as well as the associated NSAP address for the ATM port, are
stored.
Table 14-11: ATM Port Table Parameters

ini File Field Name
Default Value
Valid Range
Description
ATM_PORT_INDEX
0 to 2
First Index Field for line
ATM_PORT_ADMI
N_STATE
0 to 2
The ATM port administrative state

0 = LOCKED
1 = SHUTINGDOWN
2 = UNLOCKED
ATM_PORT_ADMI
N_NSAP_ADDR
14.1.2.2
No default
Valid 20 bytes
ATM address
The NSAP Address of the ATM PORT.

This ATM address is for the port admin
and is assigned to the port if ILMI is either
not detected or disabled. If the ILMI
address is registered with the network,
then the ILMI address takes precedence.
ATM Port Loopback Table

This table defines the loopback mode to be used for each ATM port.
Table 14-12: ATM Port Loopback Table Parameters

ini File Field Name
Default Value
Valid Range
Description
AtmPortLoopbackC
onfigPortNumber
0 to 2
The port number associated with

the optical port which is being
described.
ATMPortLoopback
ConfigIsUsed
0 to 1
This field specifies whether or not

the port loopback is used. If the
port is available on the board, this
parameter is configured as one of
the following:
0 = No
1 = Yes
AtmPortLoopbackC
onfigMode
0 to 2
This is the mode in which the

loopback functions:
0 = No loopback, calls cannot
originate or terminate to the port
User's Manual
400
User's Manual

ini File Field Name
Default Value
Valid Range
Description
over ATM
1 = UNI loopback (User-Network
Interface loopback), the loopback
is accomplished using looped
SVCs
2 = Virtual Path loopback, the
loopback is accomplished using a
looped virtual path provisioned on
the network side
AtmPortLoopbackC
onfigOutBoundVirtu
alPath
1 to 16
If the ATM Loopback Mode is VP

(Virtual Path), this chosen the VP
identity for the cells going toward
the ATM edge switch.
AtmPortLoopbackC
onfigInBoundVirtual
Path
1 to 16
If the ATM Loopback Mode is

chosen as VP (Virtual Path), this
specifies the VP identity for the
cells coming from the ATM edge
switch.
AtmPortLoopbackC
onfigVciRangeFirst
100
0 to FFFF

specifies the minimum VCIs
(Virtual Channel Identifiers) within
the inbound and outbound VP
which may be used.
AtmPortLoopbackC
onfigVciRangeLast
400
0 to FFFF

specifies the maximum VCIs
(Virtual Channel Identifiers), within
the inbound and outbound VP,
which may be used.
AtmPortLoopbackC
onfigServiceCatego
ry
1 or 2
This category is limited to Constant

Bit Rate (CBR) traffic or real-time
Variable Bit Rate (rtVBR) for this
release.
1 = CBR (Constant Bit Rate)
2 = rtVBR (real-time Variable Bit
Rate).
AtmPortLoopbackC
onfigPCR
Version 4.8
5000
0 to 2147483647
401
This defines the Peak Cell Rate

(PCR) associated with the
Switched Virtual Channel (SVC).
It's used for Constant Bit Rate
(CBR) traffic. For AAL2 (ATM
Adaptation Layer 2), this includes
bandwidth for all CIDs (Channel
Identifiers) within the SVC. For
AAL1, there is only one channel
per SVC (and no concept of a
January 2006
Mediant 3000

ini File Field Name
Default Value
Valid Range
Description
CID).
AtmPortLoopbackC
onfigSCR
5000
0 to 2147483647
This defines the Sustained Cell

Rate (SCR) associated with the
Switched Virtual Channel (SVC).
It's used for real-time Variable Bit
Rate (rtVBR) traffic. For AAL2
(ATM Adaptation Layer 2), this
includes bandwidth for all CIDs
(Channel Identifiers) within the
SVC. For AAL1, there is only one
channel per SVC (and no concept
of a CID).
AtmPortLoopbackC
onfigMBS
0 to 2147483647
This defines the Maximum Burst

Size (MBS) associated with the
switched virtual channel (SVC).
This is used in real-time Variable
Bit Rate (rtVBR) traffic. The unit for
this parameter is ATM cells.
14.1.2.3
ATM Remote Gateway Table

This table lists all the provisioned remote gateways. It would be required to be used
when, for instance, provisioning PVCs.
Table 14-13: ATM Remote Gateway Table Parameters

Default
Value
Valid Range
Description
ATM_REMOTE_GWIN
DEX
0 to 99
ATM_REMOTE_GATE
WAY_NAME
No default
Name maximum
of 20 characters
The string name for ATM remote

gateway
ATM_REMOTE_GATE
WAY_NSAP_ADDR
No default
20 bytes ATM
address
The NSAP Address of the ATM

remote gateway.
ATM_REMOTE_GATE
WAY_ALCAP_INSTAN
CE_NUM
0 to 32
The Alcap instance number that

works against the ATM remote
gateway.
ini File Field Name
User's Manual
402
User's Manual
Table 14-13: ATM Remote Gateway Table Parameters
ini File Field Name
Default
Value
Valid Range
Description
1 = VCCManager
ATM_REMOTE_GATE
WAY_DATA_OWNER
14.1.2.4
ATM AAL2 PVC Table

This table is used to define the ATM AAL2 PVC.
Table 14-14: ATM AAL2 PVC Table Parameters

ini File Field Name
Default Value
Valid Range
Description
ATM_AAL2_PVC_
PORT_NUM
Index Field for line (0 for now)
ATM_AAL2_PVC_
VPI
0 to 16
The ATM AAL2 PVC VPI
ATM_AAL2_PVC_
VCI
No default
0 to FFFF
The ATM AAL2 PVC VCI
ATM_AAL2_PVC_
TRAFFIC_SERVIC
E
rtVBR
1 or 2
The ATM AAL2 PVC traffic

category (for traffic parameter)
Rate).
ATM_AAL2_PVC_
PATH_ID
No default
0 to 4095
This is the ATM AAL2 PVC VCCI.
ATM_AAL2_PVC_
REM_GW_NUM
No default
0 to 99
This is the remote gateway index

as specified from the ATM Remote
Gateway table.
ATM_AAL2_PVC_
OWNER
The ATM AAL2 PVC owner
ATMAAL2PVC_DA
TA_OWNER
This value should be set to 1.
ATM_AAL2_PVC_
MaxNumOfCID
247
1 to 248
The maximum number of CIDs

supported by the PVC.
Version 4.8
0 = AMS
403
January 2006
Mediant 3000
Table 14-14: ATM AAL2 PVC Table Parameters

ini File Field Name
Default Value
Valid Range
Description
ATM_AAL2_PVC_
PCR
No default
0 to 2147483647

(PCR) associated with the PVC.
This is for the traffic parameter.
ATM_AAL2_PVC_
SCR
No default
0 to 2147483647

PVC. This is for the traffic
parameter.
ATM_AAL2_PVC_
MBS
0 - 2147483647

parameter.
14.1.2.5
ATM SVC Profile Table

This table defines the ATM SVC profile used when establishing AAL2 Switched Virtual
Circuits (SVCs).
Table 14-15: ATM SVC Profile Table Parameters

ini File Field Name
Default Value
Valid Range
Description
Atm_SVCProfileInd
ex
AtmSVCProfileIsUs
ed
0 or 1
This field specifies whether or not

the SVC profile is used. If the
profile is available on the board,
this parameter is configured as one
of the following:
0 = No
1 = Yes
AtmSVCProfileMax
NumOfCids
1 to 248
The maximum number of AAL2

CIDs supported by the SVC
AtmSVCProfilePCR
800
0 to 2147483647

(PCR) associated with the SVC.
This is for the traffic parameter.
AtmSVCProfileSCR
800
0 to 2147483647

SVC. This is for the traffic
parameter.
User's Manual
404
User's Manual
Table 14-15: ATM SVC Profile Table Parameters

ini File Field Name
Default Value
Valid Range
Description
AtmSVCProfileMB
S
0 to 2147483647

parameter.
AtmSVCProfilePers
istence
180
0 to 600
This defines the persistence

timeout (in seconds), the time the
SVC can remain idle before it is
dropped, for the SVC.
AtmSVCProfileServ
iceCategory
rtVBR
1 or 2
This defined the ATM SVC traffic

category and is limited to Constant
Bit Rate (CBR) traffic or real-time
Variable Bit Rate (rtVBR).
Rate).
14.1.3
NFS Servers Table

This table defines the attributes to use when accessing remote NFS file systems. Note
that one NFS file server can share multiple file systems. There should be a separate
line in this table for each file system.
Table 14-16: NFS Servers Table Parameters

ini File Field Name
Default Value
Valid Range
Description
NFSServers_Index
N/A
0 to 4
Row index into the table
NFSServers_HostO
rIP
None
See description
The domain name or IP address of

the NFS server. If a domain name
is provided, then a DNS server
must be configured.
NFSServers_RootP
ath
None
string
The path to the root of the exported

file system.
NFSServers_NfsVe
rsion
2 or 3
The NFS version to use in

accessing this remote NFS file
system.
NFSServers_AuthT
ype
0 to 1
Identifies the authentication

method to use in accessing this
remote NFS file system:
0 = AUTH_NULL
1 = AUTH_UNIX
Version 4.8
405
January 2006
Mediant 3000
Table 14-16: NFS Servers Table Parameters

ini File Field Name
Default Value
Valid Range
Description
NFSServers_UID
0 to 65537
The numerical User ID (UID) to be

used for authentication if
AUTH_UNIX (1) is selected.
NFSServers_GID
0 to 65537
The numerical Group ID (GID) to

be used in authentication if
AUTH_UNIX is selected.
NFSServers_VlanT
ype
0 to 1
The VLAN identifier to use when

accessing this remote NFS file
system. This parameters applies
only if multiple IP addresses are
configured on this board
0 = OAM
1 = Media
14.1.4
T3 Configuration Table Parameters
Note:
'T3' and 'DS3' are terms used interchangeably.
Table 14-17: T3 Configuration Table Parameters

ini File Field Name
Default Value
Valid Range
Description
DS3CONFIG_Fram
ingMethod
0 or 1
Used to select the physical T3

framing method for the
interface.
Applicable only to the TP6310/T3.
0 = M23 framing
1 = C Bit Parity
DS3CONFIG_Cloc
kSource
0 to 1
Selects the T3 Clock mode

board for the interface.
Applicable only to the TP6310/DS3.
0 = DS3Clock is recovered from
the line
1 = DS3 trunk clock source is
provided by the board's internal
clock
User's Manual
406
User's Manual
Table 14-17: T3 Configuration Table Parameters

ini File Field Name
Default Value
Valid Range
Description
DS3CONFIG_Line
BuildOut
0 or 1
Used to select the DS3 line

build out.
Applicable only to the TP6310/DS3.
0 = For a physical DS3 line
longer than 225 feet
1 = For a line shorter than 225
feet
14.1.5
Example of T3 INI file Selection :

[ DS3CONFIG ]
;FramingMethod = acFRAMING_METHOD_DS3_M23(0)
acFRAMING_METHOD_DS3_CBIT_PARITY(1)
;PSTNDS3ClockSource = EXTERNAL(0) LOCAL_BOARD(1)
;LineBuildOut = acLINE_BUILT_OUT_ABOVE_225(0)
acLINE_BUILT_OUT_BELOW_225(1)
FORMAT DS3CONFIG_Index = DS3CONFIG_FramingMethod,
DS3CONFIG_ClockSource, DS3CONFIG_LineBuildOut ;
DS3CONFIG 0 = 0, 0, 1 ;
DS3CONFIG 1 = 0, 0, 1 ;
DS3CONFIG 2 = 0, 0, 1 ;
[ \DS3CONFIG ]
In this example, the line with the FORMAT expression defines a sequence of
parameters for each T3 interface, which is- not to be changed.
For each T3 interface a line DS3CONFIG defines parameter values.
For example, for the first interface the configuration is set by the following expression:
DS3CONFIG 0 = 0, 0, 1 ;
This means that the interface should be configured with framing method M23, using
External clock source and line built-out below 225 feet.
Version 4.8
407
January 2006
User's Manual
15
15. Appendix - Auxiliary Files
Appendix - Auxiliary Files

This appendix details the following auxiliary files:
15.1
Call Progress Tone and User-Defined Tone Auxiliary Files
Prerecorded Tones (PRT) Auxiliary File
Coder Table File
Call Progress Tone and User-Defined Tone

Auxiliary Files
The auxiliary source file for Call Progress Tones and User-Defined Tones contains the
definitions of the Call Progress Tones and User-Defined Tones to be
detected/generated by the Mediant 3000. The Call Progress Tones are mostly used
for Telephony In-Band Signaling applications (e.g., Ring Back tone). Each tone can
be configured as one of the following types:
Continuous
Cadence (up to 4 cadences)
Burst
A tone can also be configured for Amplitude Modulated (AM) (only 8 of the Call
Progress Tones can be AM tones). The Call Progress Tones frequency range is 300
Hz to 1890 Hz.
The User-Defined Tones are general purpose tones to be defined by the user. They
can be set only as 'Continuous' and their frequency range is 300 Hz to 3800 Hz. The
maximum number of tones that may be configured for the User Defined and Call
Progress Tones together is 32. The maximum frequencies that may be configured in
the User Defined and Call Progress Tones together is 64. The Mediant 3000 sample
configuration file supplied by AudioCodes can be used to construct your own file.
The Call Progress Tones and User-Defined Tones file used by the Mediant 3000 is a
binary file with the extension tone.dat. Only this binary tone.dat file can be loaded to a
Mediant 3000. Users can generate their own tone.dat file by opening the modifiable
tone.ini file (supplied with the tone.dat file as part of the software package on the CD
accompanying the Mediant 3000) in any text editor, modify it, and convert the modified
tone.ini back into a binary tones.dat file using the DConversion Utility supplied with the
Mediant 3000 software package. (Refer to the Appendix, ''Utilities'' on page 495 for a
description of the procedure for generating and downloading the Call Progress Tone
file using this utility.)
To load the Call Progress Tones and User-Defined Tones configuration file to the
Mediant 3000, correctly define their parameters in the Mediant 3000's ini file. (Refer
to' 'Initialization ('ini') Files'' on page 91 for the ini file structure rules and ini file
example.)
15.1.1.1.1
Format of the Call Progress Tones Section in the Auxiliary Source File
The format of the Call Progress Tones section in the auxiliary source file starts from
the following string:
Version 4.8
409
January 2006
Mediant 3000
[NUMBER OF CALL PROGRESS TONES] - containing the following key only:
Number of Call Progress Tones - defines the number of Call Progress Tones to
be defined in the file.
[CALL PROGRESS TONE #X] - containing the Xth tone definition (starting from 0 and
not exceeding the number of Call Progress Tones -1 defined in the first section) using
the following keys:
Tone Type - Call Progress Tone type

Basic Tone Type Indices
1.
Dial Tone
2.
Ringback Tone
3.
Busy Tone
4.
Congestion Tone
5.
N/A
6.
Warning Tone
7.
Reorder Tone
8.
Confirmation Tone
9.
Call Waiting Tone
For a full tone indices list, refer to enum definition in the VoPLib API Reference
Manual, Document #: LTRT-840xx.
User's Manual
Tone Modulation Type The tone may be either Amplitude Modulated (1) or
regular (0).
Tone Form The format of the tone may be one of the following indices:
Continuous
Cadence
Burst
Low Freq [Hz] - Frequency in Hertz of the lower tone component for a dual
frequency tone, or the frequency of the tone for a single tone. This parameter is
relevant only in case the tone is not Amplitude Modulated.
High Freq [Hz] - Frequency in Hertz of the higher tone component for of a dual
frequency tone, or zero (0) for a single tone. This parameter is relevant only in
case the tone is not modulated.
Low Freq Level [-dBm] - Generation level 0 dBm to -31 dBm. This parameter is
relevant only in case the tone is not Amplitude Modulated.
High Freq Level [-dBm] - Generation level. 0 to -31 dBm. The value should be
zero (0) for a single tone. This parameter is relevant only in case the tone is not
Amplitude Modulated.
First Signal On Time [10 msec] - Signal On period (in 10 msec units) for the
first cadence ON-OFF cycle, for cadence tone. When a tone is configured to be
continuous, this parameter defines the tone On event detection time. When a
tone is configured to be burst tone, it defines the tones duration.
First Signal Off Time [10 msec] - Signal Off period (in 10 msec units) for the
first cadence ON-OFF cycle, for cadence tone. In case of burst tone, this
parameter defines the off time required after burst tone ended until the tone
410
User's Manual

detection is reported. For a continuous tone, this parameter is ignored.
Second Signal On Time [10 msec] - Signal On period (in 10 msec units) for
the second cadence ON-OFF cycle. This may be omitted if there is no second
cadence.
Second Signal Off Time [10 msec] - Signal Off period (in 10 msec units) for
the second cadence ON-OFF cycle. This may be omitted if there is no second
cadence.
Third Signal On Time [10 msec] - Signal On period (in 10 msec units) for the
third cadence ON-OFF cycle. This may be omitted if there is no third cadence.
Third Signal Off Time [10 msec] - Signal Off period (in 10 msec units) for the
third cadence ON-OFF cycle. This may be omitted if there is no third cadence.
Fourth Signal On Time [10 msec] - Signal On period (in 10 msec units) for the
fourth cadence ON-OFF cycle. This may be omitted if there is no fourth cadence.
Fourth Signal Off Time [10 msec] - Signal Off period (in 10 msec units) for the
fourth cadence ON-OFF cycle. This may be omitted if there is no fourth cadence.
Carrier Freq [Hz] the Carrier signal frequency in case the tone is Amplitude
Modulated.
Modulation Freq [Hz] The Modulated signal frequency in case the tone is
Amplitude Modulated (valid range from 1 Hz to 128 Hz).
Signal Level [-dBm] the tone level in case the tone is Amplitude Modulated.
AM Factor [steps of 0.02] Amplitude modulation factor. Valid values: 1 to 50.

Recommended values: 10 to 25.
Default Duration [msec] - The default duration (in 1 msec units) of the
generated tone.
Note 1: When defining the same frequencies for both a continuous tone and a
cadence tone, the Signal On Time parameter of the continuous tone should
have a value that is greater than the Signal On Time parameter of the
cadence tone. Otherwise the continuous tone is detected instead of the
cadence tone.
Note 2: The tone frequency should differ by at least 40 Hz from one tone to other
defined tones.
Note 3: For more information on generating the Call Progress Tones Configuration
file, refer to 'Converting a CPT ini File to a Binary dat File' in the Appendix,'
'Utilities'' on page 495.
Note 4: When constructing a CPT dat file, the Use dBm units for Tone levels
checkbox must be marked. This checkbox enables defining the levels in [dBm] units.
15.1.1.1.2
Format of the User Defined Tones Section

The format of the User Defined Tones section of the Call Progress Tone source
auxiliary file starts from the following string:
[NUMBER OF USER DEFINED TONES] - containing the following key only:
Version 4.8
411
January 2006
Mediant 3000
Number of User Defined Tones - defines the number of User Defined Tones to
be defined in the file.
[USER DEFINED TONE #X] - containing the Xth tone definition (starting from 0 and
not exceeding the number of User Defined Tones -1 defined in the first section) using
the following keys:
Tone Type User Defined Tone type
Basic Tone Type Indices

1.
Dial Tone
2.
Ringback Tone
3.
Busy Tone
4.
Congestion Tone
5.
N/A
6.
Warning Tone
7.
Reorder Tone
8.
Confirmation Tone
9.
Call Waiting Tone
For a full tone indices list, refer to enum definition in the VoPLib API Reference
15.1.1.1.3
Low Freq [Hz] - Frequency in Hertz of the lower tone component for a dual
frequency tone, or the frequency of the tone for a single tone.
High Freq [Hz] - Frequency in Hertz of the higher tone component for of a dual
frequency tone, or zero (0) for a single tone.
Low Freq Level [-dBm] - Generation level 0 dBm to -31 dBm.
High Freq Level [-dBm] - Generation level. 0 to -31 dBm. The value should be
zero (0) for a single tone.
Default Duration [msec] - The default duration (in 1 msec units) of the
generated tone.
Default Template for Call Progress Tones

The Mediant 3000 is initialized with the default Call Progress Tones configuration. To
change one of the tones, edit the default call progress txt file. The table below lists the
default call progress tones.
User's Manual
412
User's Manual
Table 15-1: Default Call Progress Tones

[NUMBER OF CALL PROGRESS TONES]
Number of Call Progress Tones=9
#Dial tone
Tone Type=1
[CALL PROGRESS TONE #0]
Tone Form = 1 (Continuous)

Low Freq [Hz]=350
High Freq [Hz]=440
Low Freq Level [-dBm]=13 (-13dBm)
High Freq Level [-dBm]=13
First Signal On Time [10msec]=300
#Dial tone
Tone Type=1
Tone Form = 1 (Continuous)

Low Freq [Hz]=440
High Freq [Hz]=0
#Ringback
Tone Type=2
Tone Form = 2 (Cadence)

Low Freq [Hz]=440
High Freq [Hz]=480
First Signal Off Time [10msec]=400
#Ringback
Tone Type=2

Low Freq [Hz]=440
High Freq [Hz]=0
Version 4.8
413
January 2006
Mediant 3000

#Busy
Tone Type=3

Low Freq [Hz]=480
High Freq [Hz]=620
#Busy
Tone Type=3

Low Freq [Hz]=440
High Freq [Hz]=0
#Reorder tone
Tone Type=7

Low Freq [Hz]=480
High Freq [Hz]=620
#Confirmation tone
Tone Type=8

Low Freq [Hz]=350
High Freq [Hz]=440
User's Manual
414
User's Manual

#Call Waiting Tone
Tone Type=9

Low Freq [Hz]=440
High Freq [Hz]=0
15.1.2
Modifying the Call Progress Tones File

Customers are supplied with a modifiable Call Progress Tone auxiliary source file
(with ini file extension) and a non-modifiable Call Progress Tone dat binary file in the
software package under Auxiliary_Files\Sample_Call_Progress_Files\.
Only the binary dat file can be sent to the Mediant 3000.
In the auxiliary source file, customers can modify Call Progress Tone levels, Call
Progress Tone frequencies to be detected/generated by the Mediant 3000, to suit
customer-specific requirements. An example of a Call Progress Tone ini file name is
call_progress_defaults.dat. Note that the word 'tones' is defined in the Call Progress
Tone ini file name, to differentiate it from the Mediant 3000's ini file.
The default call progress tones configuration is found on call_progress_defaults.ini file.
To change one of the tones, edit the default call progress txt file.
For example: to change the dial tone to 440 Hz only, replace the #Dial tone section in
the table below with the following text:
#Dial tone
Tone Type=1
Tone Form = 1
Low Freq [Hz]=440
High Freq [Hz]=0
First Signal On Time [10msec]=300; the dial tone is detected after 3 sec
Users can specify several tones of the same type using Tone Type definition. These
additional tones are used only for tone detection. Generation of specific tone is
according to the first definition of the specific tone. For example, the user can define
an additional dial tone by appending the second dial tone definition lines to the tone
Version 4.8
415
January 2006
Mediant 3000
ini file. The Mediant 3000 reports dial tone detection if either one of the two tones is
detected.
To modify these ini files and send the dat file to the Mediant 3000,
take these 4 steps:
15.1.3
1.
Open the CPT ini file (it opens in Notepad or in a customer-defined text file
editor.)
2.
Modify the file in the text file editor according to your specific requirements.
3.
Save your modifications and close the file.
4.
Convert the file with the DConversion Utility into a binary dat file (refer to
"Converting a Modified CPT ini File to a dat File with the Download Conversion
Utility" below).
Converting a Modified CPT ini File to a dat File with the

Download Conversion Utility
After modifying the original CPT ini file (supplied with the Mediant 3000's software
package), you can use the Download Conversion Utility to convert the modified file
into a dat binary file. You can send only the dat file to the Mediant 3000; the ini file
cannot be sent.
To convert a modified CPT ini file to a binary dat file, Run the executable Download
Conversion Utility file, DConvert240.exe. For more information, refer to the Appendix,'
'Utilities'' on page 495.
After making the dat file, send it to the Mediant 3000 using one of the folliwing:
The Embedded Web Server GUI's Auxiliary Files. (Refer to ''Auxiliary Files
Download'' on page 272.)
or
The BootP/TFTP Server to send to the Mediant 3000 the Mediant 3000's ini file
(which simultaneously downloads the Call Progress Tone dat file, provided that
the Mediant 3000's ini file parameter CallProgressTonesFilename is defined and
provided that both files are located in the same directory.) (Refer to the
Appendix, ''BootP/TFTP Server'' on page 307).
or
15.2
For cPCI boards, refer to the appropriate section in the VoPLib Application
Developer's Manual, Document #: LTRT-844xx.
Playing the Prerecorded Tones (PRT) Auxiliary

File
The Call Progress Tones and the User-Defined Tones mechanisms have several
limitations such as limited number of predefined tones, or limited number of frequency
integrations in one tone. To solve these problems and provide a more flexible tone
generation capability, prerecorded tones and play can be downloaded to the Mediant
3000 and be played using regular tones generation commands.
User's Manual
416
User's Manual
15.2.1.1.1
PRT File Configuration

The PRT file that should be downloaded to the Mediant 3000 is a binary dat file, which
was created using AudioCodes' DConvert utility. The tones should be recorded (or
created using a Signaling Editor) if the user intends to download them in separate
PCM files. The PCM files should include the following characteristics:
Coder:
G.711 A-law, G.711 -law or Linear PCM.
Rate:
8 kHz
Resolution:
8-bit
Channels:
mono
The PRT module plays the recorded tone repeatedly. This provides the ability to
record only part of the tone, while still playing it for a full duration. For example, if a
tone has a cadence of 2 seconds on and 4 seconds off, the recorded file should
contain only the 6 seconds of the cadence. The PRT module repeatedly plays this
cadence for the configured duration. In the same manner, a continuous tone can be
played by repeating only part of it.
After the PCM files are properly prepared, these files should be converted into one dat
file using the DConvert utility For more information regarding the DConvert utility, and
how to make a dat PRT file, refer to the Appendix, ''BootP/TFTP Server'' on page 307.
Note: The maximum number of prerecorded tones that can be stored in one dat
file is 40.
15.2.1.1.2
Downloading the PRT dat File

Downloading the PRT dat file into the Mediant 3000 can be done using one of the
following:
HTTP
TFTP
VoPLib API
For HTTP and TFTP download, refer to ''Software Upgrade Wizard'' on page 266.
For VoPLib API download, refer to the Playing Prerecorded Tones (PRT) section of
the VoPLib Application Developer's Manual, Document #: LTRT-844xx.
Note 1: The maximum PRT buffer size is 1 MB.
Note 2: If the same tone type was defined as PRT and as Call Progress Tone or
User-Defined Tone, the Mediant 3000 plays it using the PRT module.
Version 4.8
417
January 2006
Mediant 3000
15.3
Coder Table File

The Coder Table file defines which coders are to be supported by the Mediant 3000. It
is limited to the supported coders according to the loaded DSP template. Other coders
can not be added.
The following is an example of an ini file that includes these Coder Table definitions.
This ini file is converted (using the DConvert utility) to a binary file, and loaded to the
Mediant 3000. . If no such file is loaded, the default settings are used.
[Internal name]
[Coder name] [Txpayload] [RxPayload] [Ptime]
PCMA
PCMA
8
8
20
PCMU
PCMU
0
0
20
G726-16
G726-16
35
35
20
G726-24
G726-24
36
36
20
G726-32
G726-32
2
2
20
G726-40
G726-40
38
38
20
X-G727-16
X-G727-16
39
39
20
X-G727-24-16
X-G727-24-16
40
40
20
X-G727-24
X-G727-24
41
41
20
X-G727-32-16
X-G727-32-16
42
42
20
X-G727-32-24
X-G727-32-24
43
43
20
X-G727-32
X-G727-32
44
44
20
X-G727-40-16
X-G727-40-16
45
45
20
X-G727-40-24
X-G727-40-24
46
46
20
X-G727-40-32
X-G727-40-32
47
47
20
G723HIGH
G723
4
4
30
G723LOW
G723
80
80
30
G729
G729
18
18
20
G728
G728
15
15
20
GSM
GSM
3
3
20
X-CCD
X-CCD
56
56
20
iLBC13
iLBC
100
100
30
iLBC15
iLBC
101
101
20
BV16
BV16
102
102
20
EVRC_C
EVRC
103
103
20
telephone-event telephone-event
96
96
20
RED
RED
104
104
20
CN
CN
13
13
20
The first field is a text representation of the internal coder name. The second field is
free text, and contains the name that is to be used in the SDP. The two payload fields
define the default payload for this coder. The PTIME field defines the default to be
used for this coder. The maximal value is the basic packet size (i.e., 20) multiplied by
6.
15.3.1.1.1
15.3.1.1.2
New Coders Introduced with the Table
EVRC0 This is actually not a new coder, it was called until now EVRC in our
SDP. The correct name (according to RFC 3558) is EVRC0, as this is what our
board supports.
BV16 and iLBC Both are supported for BCT only.
Coders Support Level

The application defines the following support levels for coders:
User's Manual
418
User's Manual
None - A coder with support level "None" is not supported. An error is generated
if an attempt is made to use the coder.
Full - A coder with support level "Full" is valid for all type of calls.
BCT - A coder with support level "BCT" (a new feature) is valid ONLY for BCT
calls. The coders iLBC and BV16 belong to this feature. Other coders that appear
in the file, but are not supported in the current DSP template, also receive this
support level.
The support level is defined internally by the board.
15.3.2
Converting a Modified CoderTable ini File to a dat File Using

DConvert Utility
After modifying the original CoderTable (Tbl) ini file (originally supplied with the
Mediant 3000's software package), you can use the DConvert Utility to convert the
modified file into a dat binary file. (The ini file cannot be sent.) For more information,
refer to the Appendix,' Utilities' on page 495. You can only send the dat file to the
Mediant 3000.
After creating the dat file, send it to the Mediant 3000 using one of the following:
The Embedded Web Server GUI's Auxiliary Files (Refer to 'Auxiliary Files
Download' on page 272.)
or
15.3.3
The BootP/TFTP Server - used to send the ini file (which simultaneously
downloads the CoderTbl dat file, to the Mediant 3000, The ini file parameter
CoderTblFilename must be enabled and both the ini file and CoderTbl dat file
must be located in the same directory.) (Refer to the Appendix, 'BootP/TFTP
Server' on page 307).
Default Coder Table (Tbl) ini file

The following is the default file for building the Coder Table (Tbl) dat file:
[Internal name]
[Coder name] [Txpayload] [RxPayload] [Ptime]
PCMA
PCMA
8
8
20
PCMU
PCMU
0
0
20
G726-16
G726-16
35
35
20
G726-24
G726-24
36
36
20
G726-32
G726-32
2
2
20
G726-40
G726-40
38
38
20
X-G727-16
X-G727-16
39
39
20
X-G727-24-16
X-G727-24-16
40
40
20
X-G727-24
X-G727-24
41
41
20
X-G727-32-16
X-G727-32-16
42
42
20
X-G727-32-24
X-G727-32-24
43
43
20
X-G727-32
X-G727-32
44
44
20
X-G727-40-16
X-G727-40-16
45
45
20
X-G727-40-24
X-G727-40-24
46
46
20
X-G727-40-32
X-G727-40-32
47
47
20
G723HIGH
G723
4
4
30
G723LOW
G723
80
80
30
G729
G729
18
18
20
G728
G728
15
15
20
GSM
GSM
3
3
20
X-CCD
X-CCD
56
56
20
NETCODER_4_8
X-NETCODER
49
49
20
NETCODER_5_6
X-NETCODER
50
50
20
Version 4.8
419
January 2006
Mediant 3000
NETCODER_6_4
X-NETCODER
NETCODER_7_2
X-NETCODER
NETCODER_8
X-NETCODER
NETCODER_8_8
X-NETCODER
NETCODER_9_6
X-NETCODER
EVRC
EVRC0
X-EVRC-TFO
X-EVRC-TFO
X-EVRC-TTY
X-EVRC-TTY
X-QCELP-8
X-QCELP-8
X-QCELP-8-TFO
X-QCELP-8-TFO
QCELP
QCELP
X-QCELP-TFO
X-QCELP-TFO
G729E
G729E
AMR_4_75
AMR
AMR_5_15
AMR
AMR_5_9
AMR
AMR_6_7
AMR
AMR_7_4
AMR
AMR_7_95
AMR
AMR_10_2
AMR
AMR_12_2
AMR
GSM-EFR
GSM-EFR
iLBC13
iLBC
iLBC15
iLBC
BV16
BV16
EVRC_C
EVRC
telephone-event telephone-event
RED
RED
X-MODEM-RELAY
X-MODEM-RELAY
CN
CN
Image/T38
Image/T38
User's Manual
420
51
52
53
54
55
60
81
85
61
82
62
83
63
64
65
66
67
68
69
70
71
84
100
101
102
103
96
104
254
13
254
51
52
53
54
55
60
81
85
61
82
62
83
63
64
65
66
67
68
69
70
71
84
100
101
102
103
96
104
254
13
254
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
30
20
20
20
20
20
20
20
20
User's Manual
16
16. Appendix - RTP/RTCP Payload Types
Appendix - RTP/RTCP Payload Types

Latest RTP Payload Types are defined in RFC 3551. For coders that should have
dynamic Payload types, proprietary default values out of the dynamic Payload type
range have been defined. These defaults are appropriate when working with
AudioCodes products only. However, it is recommended to set a dynamic Payload
type for them, which is usually done by higher applications during call setup. Be sure
not to overload dynamic Payload types.
Note: Refer to the Release Notes for the supported coders.
16.1
Payload Types Defined in RFC 3551

Table 16-1: Payload Types Defined in RFC 3551
Payload Type
Description
Basic Packet Rate [msec]
G.711 -Law
20
G.726-32
20
GSM & GSM-EFR
20
G.723 (6.3/5.3 kbps)
30
G.711 A-Law
20
15
G.728
20
18
G.729
20
35
G.726-16
20
36
G.726-24
20
38
G.726-40
20
62
QCELP (13.3 kbps)
20
63
G729E
20
200
RTCP Sender Report
Randomly, approximately
every 5 sec (when packets are
sent by channel)
201
RTCP Receiver Report
Randomly, approximately
every 5 sec (when channel is
only receiving)
202
RTCP SDES packet
Version 4.8
421
January 2006
Mediant 3000
Table 16-1: Payload Types Defined in RFC 3551

Payload Type
Description
203
RTCP BYE packet
204
RTCP APP packet
Note: QCELP-13 default value (63) is not equal to the RFC 3551 value (12) due
to backward compatible problem.
16.2
Payload Types Not Defined in RFC 3551

Table 16-2: Payload Types Not Defined in RFC 3551
Payload Type
Description
39
G.727 16 kbps
20
40
G.727 24-16 kbps
20
41
G.727 24 kbps
20
42
G.727 32-16 kbps
20
43
G.727 32-24 kbps
20
44
G.727-32 kbps
20
45
G.727 40-16 kbps
20
46
G.727 40-24 kbps
20
47
G.727 40-32 kbps
20
51
NetCoder 6.4 kbps
20
52
NetCoder 7.2 kbps
20
53
NetCoder 8.0 kbps
20
54
NetCoder 8.8 kbps
20
55
NetCoder 9.6 kbps
20
56
Transparent PCM
20
60
EVRC
20
61
QCELP (8 Kbps)
20
64
AMR 4.75 Kbps
20
65
AMR 5.15 Kbps
20
66
AMR 5.9 Kbps
20
User's Manual
422
User's Manual
16. Appendix - RTP/RTCP Payload Types
Table 16-2: Payload Types Not Defined in RFC 3551

Payload Type
Description
67
AMR 6.7 Kbps
20
68
AMR 7.4 Kbps
20
69
AMR 7.95 Kbps
20
70
AMR 10.2 Kbps
20
71
AMR 12.2 Kbps
20
72
Vox ADPCM
20
90
Linear PCM
20
65
iLBC
20/30
78
BV16
20
16.3
Default Dynamic Payload Types Which are Not

Voice Coders
Table 16-3: Dynamic Payload Types Not Defined in RFC 3551
16.4
Payload Type
Description
96
RFC 2833
102
Fax Bypass
103
Modem Bypass
104
RFC 2198
105
NSE
Default RTP/RTCP/T.38 Port Allocation

The following table shows the default RTP/RTCP/T.38 port allocation.
Table 16-4: Default RTP/RTCP/T.38 Port Allocation

Channel Number
RTP Port
RTCP Port
T.38 Port
4000
4001
4002
4010
4011
4012
Version 4.8
423
January 2006
Mediant 3000
Table 16-4: Default RTP/RTCP/T.38 Port Allocation

Channel Number
RTP Port
RTCP Port
T.38 Port
4020
4021
4022
4030
4031
4032
4040
4041
4042
4050
4051
4052
4060
4061
4062
4070
4071
4072
4000 + 10(n-1)
4001 + 10(n-1)
4002 + 10(n-1)
120
5190
5191
5192
192
5910
5911
5912
384
7830
7831
7832
480
8790
8791
8792
Note the changed port allocation from earlier releases, for channel #5 and above.
User's Manual
424
User's Manual
17. Appendix - DTMF, Fax & Modem Transport Modes
17
Appendix - DTMF, Fax & Modem

Transport Modes
17.1
DTMF/MF Relay Settings

Users can control the way DTMF/MF digits are transported to the remote Endpoint,
using the DTMFTransport/MFTransport configuration parameters. The following four
modes are supported:
17.2
DTMF/MFTransportType= 0 (MuteDTMF/MF) In this mode, DTMF/MF digits are

erased from the audio stream and are not relayed to the remote side. Instead,
silence is sent in the RTP stream.
DTMF/MFTransportType= 2 (TransparentDTMF/MF) In this mode, DTMF/MF

digits are left in the audio stream and the DTMF/MF relay is disabled.
DTMF/MFTransportType= 3 (acRelayDTMFOverRTP/ acRFC2833RelayMF) In

this mode, DTMF/MF digits are relayed to the remote side using the RFC 2833
Relay syntax.
DTMFTransportType = 7 (acRFC2833RelayDecoderMute) In this mode, DTMF

digits are relayed to the remote side using the RFC 2833 Relay syntax. RFC
2833 digit packets that are received from the remote side are muted on the audio
stream.
Fax/Modem Settings
Users may choose from one of the following transport methods for Fax and for each
modem type (V.22/V.23/Bell/V.32/V.34):
fax relay - demodulation / remodulation
bypass - using a high bit rate coder to pass the signal
transparent - passing the signal in the current voice coder
transparent with events - transparent + issues fax/modem events
When the fax relay mode is enabled, distinction between fax and modem is not
immediately possible at the beginning of a session. Therefore, the channel is in
Answer Tone mode until a distinction is determined. The packets being sent to the
network at this stage are Fax relay T.38 packets.
17.3
Configuring Fax Relay Mode

When FaxTransportType= 1 (relay mode), upon detection of fax, the channel
automatically switches from the current voice coder to answer tone mode, and then to
Fax T.38 relay mode.
When Fax transmission has ended, the reverse switching from fax relay to voice is
performed. This switching automatically mode occurs at both the local and remote
Endpoints.
Version 4.8
425
January 2006
Mediant 3000
The fax rate can be limited by using the FaxRelayMaxRate parameter and the ECM
Fax Mode can be enabled/disabled using the FaxRelayECMEnable parameter
settings.
The (proprietary) redundancy mode that was specially designed to improve protection
against packet loss through the EnhancedFaxRelayRedundancyDepth parameter.
Although this is a proprietary redundancy scheme, it is compatible with other T.38
decoders. The depth of the redundancy (that is, the number of repetitions) is defined
by the FaxRelayRedundancyDeoth configuration parameter.
Note: T.38 mode currently supports only the T.38 UP syntax.
17.4
Configuring Fax/Modem ByPass Mode

When VxxTransportType= 2 (FaxModemBypass, Vxx can be one of the following:
V32/V22/V21/Bell/V34/Fax), then on detection of Fax/Modem, the channel
automatically switches from the current voice coder to a high bit-rate coder, as defined
by the user in the FaxModemBypassCoderType configuration parameter.
If relay is enabled for one of the modes (Fax/Modem), the Answer Tone mode packets
are relayed as Fax relay packets.
When the EnableFaxModemInbandNetworkDetection parameter is enabled under the
conditions discussed above, a detection of an Answer Tone from the network triggers
a switch to bypass mode in addition to the local Fax/Modem tone detections.
However, only a high bit-rate coder voice session effectively detects the Answer Tone
sent by a remote Endpoint
During the bypass period, the coder uses the packing factor (by which a number of
basic coder frames are combined together in the outgoing WAN packet) set by the
user in the FaxModemBypassM configuration parameter. The user can also configure
the basic frame size by through the FaxModemBypassBasicRTPPacketInterval
configuration parameter. The network packets generated and received during the
bypass period are regular RTP voice packets (as per the selected bypass coder) but
with a different RTP Payload type.
When Fax/Modem transmission ends, the reverse switching, from bypass coder to
regular voice coder, is performed.
Note: When Fax relay is enabled, V21TransportType must be set to disable
(Transparent) mode.
17.5
Configuring Fax/Modem Bypass NSE mode

Setting the NSEMode to 1 configures the answering Fax/Modem channel to send NSE
packets to the calling Fax/Modem channel to switch to Bypass. Using the
NSEPayloadType parameter, the user can control the NSE RTP packets Payload
type (default = 105). Note that the value of this parameter should be within the RTP
Dynamic Payload Type range (96 to 127).
User's Manual
426
User's Manual
17.6
17. Appendix - DTMF, Fax & Modem Transport Modes
Supporting V.34 Faxes

Unlike the T.30 fax machines, the V.34 fax machines have no relay standard to
transmit the data over IP to the remote side. Therefore AudioCodes provides the
following operation modes for transporting the V.34 fax data over the IP.
Note: For all the setups described below, the CNG tone detector is disabled.
17.6.1
Using Bypass Mechanism for V.34 Fax Transmission

Configuration:
Fax transport mode - Relay/Bypass
Vxx modem mode - Bypass
Expected events for V.34 Fax to V.34 Fax - Bypass Mode are shown in the table
below.
Table 17-1: V.34 Fax to V.34 Fax - Bypass Mode

Calling
Answering
EV_DETECT_MODEM (2100 AM + Reversal)
EV_DETECT_MODEM
EV_DETECT_FAX
EV_DETECT_FAX (Refer to Note 1 below)
EV_END_FAX
EV_END_FAX
Note: The board changes its status to bypass mode upon receiving fax bypass
packet from the remote side.
Note that if the fax transport type is set to relay, the fax relay benefits for the T.30 fax
machines and, in parallel, are a variable when using a V.34 fax with its full rate.
Therefore, AudioCodes recommends this setup. Also note that if CNG relay is used,
in some cases, such as for manual answering machine, the fax may revert to T.30 fax
with a speed of 14400 bps.
17.6.2
Using Events Only Mechanism for V.34 Fax Transmission

Use events only mode to transmit V.34 fax with its maximum capabilities:
Configuration:
Version 4.8
Fax transport mode - Events only mode
Vxx modem mode - Events only mode

427
January 2006
Mediant 3000
Expected events for V.34 Fax to V.34 Fax - Events Only Mode are shown in the table
below.
Table 17-2: V.34 Fax to V.34 Fax - Events Only Mode

Calling
Answering
EV_DETECT_ANSWER_TONE
EV_DETECT_FAX
17.6.3
Using Relay Mode for Various Fax Machines (T.30 and V.34)
The user can force the V.34 fax machines to revert to T.30 and work at relay mode.
Configuration:
Fax transport mode - Relay
Vxx modem mode - Disable
CNG detectors mode - Disable
In this mode, the fax events are identical to the regular T.30 fax session over T.38
protocol.
Expected events for V.34 Fax to V.34 Fax - Relay Mode are shown in the table below.
Table 17-3: V.34 Fax to V.34 Fax - Relay Mode

Calling
Answering
EV_DETECT_ANSWER_TONE
EV_DETECT_FAX
EV_DETECT_FAX
EV_END_FAX
User's Manual
EV_END_FAX
428
User's Manual
18. Appendix - CAS Protocol Table
18
Appendix - CAS Protocol Table
18.1
Constructing a CAS Protocol Table

Constructing or Modifying a CAS Protocol Table for CAS-Terminated Protocols
The protocol table file is a text file containing the protocols state machine that defines
the entire protocol process. It is constructed of States, pre-defined Actions/Events,
and pre-defined functions. With this file, the user has full control of the CAS protocol
and can define or modify any CAS protocol by writing the protocol state machine in a
text file according to the AudioCodes defined rules.
To generate the protocol file, take these 5 steps:
18.2
1.
Learn the protocol text file rules (rules detailed in this manual and their syntax are
based on C pre-processor commands).
2.
Get the AudioCodes example.
3.
Build the specific protocol/script text (xxx.txt) file and its related numerical value h
file (xxx.h).
4.
Compile the xxx.txt with the TrunkPack Downloadable conversion utility to

produce the xxx.dat file. Refer to 'API Demonstration Utilities' on page 495 for a
detailed description of the utility usage.
5.
Download the User_protocol.dat file to the board via acOpenBoard() command at

initialization phase.
Table Elements
CASSetup.h - File includes all the pre-defined tools needed to build a new protocol
text file or modifying an existing one. The protocol table file is composed of the
following bricks:
18.2.1
INIT variables
INIT variables - Numeric values in UserProt_defines_xxx.h, defined by the user. For
example, INIT_RC_IDLE_CAS defines the ABCD bits expected to be received in the
IDLE state, INIT_DTMF_DIAL defines the On-time and Off-time for the DTMF digits
generated towards the PSTN. See the detailed list in CASSetup.h and in the sample
protocol text file. Refer to the following ST_INIT detailed explanation.
18.2.2
Actions
Actions (i.e., protocol table events) - Actions are protocol table events activated either
by the DSP (e.g., EV_CAS_01) or by the user (e.g., EV_PLACE_CALL,
EV_TIMER_EXPIRED1). The full list of the possible pre-defined events can be found
in the CASSetup.h file.
Version 4.8
429
January 2006
Mediant 3000
18.2.3
Functions
Functions - Define a certain procedure that can be activated in any state or in the
transition from one state to another. The available functions include, for example,
SET_TIMER (timer number, timeout in ms.) SEND_CAS (AB value, CD value). A full
list of the possible pre-defined functions can be found in the CASSetup.h file.
18.2.4
States
States - Each Protocol table consists of several states that it switches between during
the call setup and tear-down process. Every state definition begins with the prefix ST_
followed by the state name and colons. The body of the state is composed of up to 4
unconditional performed functions and list of actions that may trigger this state.
As an example, the table below was taken from an E&M wink start table protocol file:
Table 18-1: ST_DIAL: Table Elements

Action
Function
Parameter
Next State
#1
#2
Extra Delay
Before Dial
None
DO
None
None
NO_STATE
No Answer Time
None
ST_DIAL_ENDED
FUNCTION0
SET_TIMER
EV_TIMER_
EXPIRED2
SEND_DES
T_NUM
None
EV_DIAL_
ENDED
SET_TIMER
#3
When the state machine reaches the dial state, it sets timer number 2 and then waits
for one of the two possible actions to be triggered: either timer 2 expiration or end of
dial event. When timer 2 expires, the protocol table executes SEND_DEST_NUM
function and remains in the same state (NEXT_STATE=NO_STATE). When the dial
event ends, the protocol table sets timer 4 and moves to ST_DIAL_ENDED written in
the NEXT_STATE field.
Although users can define their own states, there are two states defined in the
CASSetup.h file and must appear in every protocol table created.
The two states are ST_INIT and ST_IDLE.
User's Manual
ST_INIT - When channels initialization is selected, the table enters the Init state.
This state contains functions that initialize the following global parameters:
RC_IDLE_CAS - Defines the ABCD bits expected to be received in the IDLE

state in the specific protocol.
TX_IDLE_CAS - Defines the ABCD bits transmitted on IDLE state in the

specific protocol.
DIAL_PLAN - A change regarding the issue of an incoming call dialed

number is implemented in revision 3.21 as opposed to revision 3.2 and
earlier. In revision 3.2 and earlier, users were required to pre-define the
expected number of digit to receive an incoming call. If a lower number of
digits than expected were received, the call setup would have failed.
430
User's Manual
Revisions 3.21 and later, process the incoming call detection event by declaring end
of digit reception in the following ways (both for ADDRESS/destination number and
ANI/source number):
Receiving # digit (in MF or DTMF)
The number of digits collected reaches its maximum value as defined in

the DIAL_PLAN Parameter #1 and #2 for destination and ANI numbers
respectively
A pre-defined time-out value defined in the DIAL_PLAN Parameter #3

elapses
Note: This method is not used when working with MFC/R2 protocols. MFC/R2
uses expected number of digits defined in ProtUser_defines_xxx.h.
Version 4.8
DTMF_DIAL - Defines the On-time and Off-time for the DTMF digits
generated towards the PSTN.
COMMA_PAUSE_TIME - Defines the delay between each digit when a

comma is used as part of the dialed number string. (See acPSTNPlaceCall
for further explanation).
DTMF_DETECTION - Defines the minimum/maximum On-time for DTMF

digit dialing detection.
PULSE_DIAL_TIME - Not supported by current stack version. Defines the

Break and Make time for pulse dialing.
PULSE_DIAL - Not supported by the current stack version. Defines the

Break and Make ABCD bits for pulse dialing.
DEBOUNCE - Defines the interval time of CAS to be considered as a hit.
COLLECT_ANI - Enables or Disables reception of ANI in a specific protocol.
DIGIT_TYPE - Defines the dialing method used (DTMF, MF). On MFC/R2

protocols this parameter is not applicable (digits are assumed to be R2
digits).
NUM_OF_EVENT_IN_STATE - Inserted for detection on

TOTAL_NUMBER_OF_EVENTS_IN_STATE (CASSetup.h).
INIT_MGCP_REPORT - Enables the event for MGCP. These tables are

specifics and relevant for MGCP only. Do not use it otherwise.
INIT_GLOBAL_TIMERS - Initiates specific timers, is used with Parameter#1

for metering pulse timer duration.
INIT_VERSION - Defines the version number. The version number is related

to the release version number.
INIT_SIZE_OF_TABLE_PARAM - Users must insert the definition of

TOTAL_NUMBER_OF_EVENTS_IN_STATE from the CASSetup.h.
ST_IDLE - When no active call is established or in the process of being

established, the table resides in Idle state, allowing it to start the process of
incoming or outgoing calls. When the call is cleared, the state machine table
returns to its idle state.
431
January 2006
Mediant 3000
18.3
Reserved Words
For reserved words, such as DO, NO_STATE, etc.
CASSetup.h.
18.4
Refer to the detailed list in
States Line Structure

Each text line in the body of each state is composed of 6 columns:
18.5
1.
action/event
2.
function
3.
parameter #1
4.
parameter #2
5.
parameter #3
6.
next state
Action/Event
Action/event is the name of the tables events that are the possible triggers for the
entire protocol state machine. Those can be selected from the list of events in the
CASSetup.h file (e.g., EV_DISCONNECT_INCOMING).
At the beginning of the state, there can be up to 4 special unconditional action/events
called FUNCTION. They events are functions that are unconditionally performed when
the table reaches the state. These actions are labeled FUNCTION0 to FUNCTION3.
The following is the list of available protocols table actions (events to the state
machine):
1.
User's Manual
User Command Oriented:
EV_PLACE_CALL - When using acPSTNPlaceCall().
EV_ANSWER - When using acPSTNAnswerCall().
EV_DISCONNECT_OUTGOING - When using the function

acPSTNDisconnectCall() and the call is outgoing.
EV_DISCONNECT_INCOMING - When using the function

acPSTNDisconnectCall() and the call is incoming.
EV_RELEASE_CALL - When using acPSTNReleaseCall()
EV_USER_BLOCK_COMND - When using acCASBlockChannel(), this

event handled for blocking or unblocking the channel.
EV_MAKE_METERING_PULSE - When using acCASMeteringPulse it

triggers the start of the metering pulse while using the SET_PULSE_TIMER
function to start the timer to get the Off event (refer to the
EV_METERING_TIMER_PULSE_OFF below.).
EV_METERING_TIMER_PULSE_OFF - event after timer

(SET_PULSE_TIMER function) expires. (Refer to
EV_MAKE_METERING_PULSE above.)
EV_MAKE_FLASH_HOOK - When using acCASFlashHook, a flash hook is

triggered.
432
User's Manual
2.
3.
4.
5.
6.
Version 4.8
CAS Change Oriented:
EV_CAS_1_1 - a new CAS A,B bits are received (A=1, B=1, was stable for
the bouncing period).
Timer Oriented:
EV_TIMER_EXPIRED1 - timer 1 that was previously set by table has

expired.

expired.

expired.

expired.

expired.

expired.

expired.

expired.
Counter Oriented:
EV_COUNTER1_EXPIRED - counter 1 value has reached 0.
EV_COUNTER2_EXPIRED - counter 2 value has reached 0.
IBS oriented:
EV_RB_TONE_STARTED - Ring back tone as defined in the call progress

ini file (type and index) is detected.
EV_RB_TONE_STOPPED - Ring back tone as defined in the call progress

ini file (type and index) is stopped after it has been previously detected.
EV_DIAL_TONE_DETECTED - Dial tone as defined in the call progress ini

file (type and index) is detected.
EV_DIAL_TONE_STOPPED - Dial tone as defined in the call progress ini

file (type and index) was stopped after it has been previously detected.
MF Oriented (MFCR2 protocol related):
EV_MFRn_1 - MF digit 1 is detected.

433
January 2006
Mediant 3000
User's Manual
EV_MFRn_1_STOPPED - MF digit 1 previously detected, is now stopped.
EV_MFRn_2_ STOPPED - MF digit 2 previously detected, is now stopped.
EV_MFRn_10_ STOPPED - MF digit 10 previously detected, is now

stopped.

stopped.

stopped.

stopped.

stopped.

stopped.
EV_END_OF_MF_DIGIT - When using DialMF() and no more dialed number

digits are available. (They already have been sent. For example, the far side
requests the next ANI digit, but all digits already have been sent). This event
usually appears in MFR2 tables.
EV_NO_ANI - When using DialMF() and no ANI was specified by the

outgoing user in the acPSTNPlaceCall() function. (MFCR2 protocols
specifications should define what to do when no ANI digits are available.
Usually I-12 is sent).
434
User's Manual
Note: MF digit is MF R1 or R2-FWD or R2-BWD according to the context, protocol

type and call direction.
7.
18.6
EV_ACCEPT - When using acCASAcceptCall (used only in MFC/R2) with

CALLED_IDLE as its reason parameter.
EV_REJECT_BUSY - When using acCASAcceptCall with CALLED_BUSY

as its reason parameter.
EV_REJECT_CONGESTION - When using acCASAcceptCall with

CALLED_CONGESTION as its reason parameter.
EV_REJECT_UNALLOCATED - When using acCASAcceptCall with

CALLED_UNALLOCATED as its reason parameter.
EV_REJECT_RESERVE1 - When using acCASAcceptCall with

CALLED_RESERVE1 as its reason parameter.
EV_REJECT_RESERVE2 - When using acCASAcceptCall with

CALLED_RESERVE2 as its reason parameter.
Miscellaneous:
EV_DIALED_NUM_DETECTED - (Incoming call) dialed destination number

is collected after START_COLLECT was previously activated and the
condition for incoming_call_detected event is satisfied (see ST_INIT for
conditions details).
EV_DIAL_ENDED - Dialing initiated by table SEND_DEST_NUM is

completed (last digit has been sent).
EV_ANI_NUM_DETECTED - This action is used to inform the script file of a

successful reception of the ANI digits string, or when timeout of digit waiting
occurs. This is reported at the incoming call detected event, when the ANI
flag is YES.
EV_FIRST_DIGIT - Reception of first digit out of the incoming digit string.

Used in the FXO protocols, where informing the script of receiving of the first
digit, enables the script to use the SEND_PROG_TON function to stop the
dial tone.
Function
The function column holds the name of the function to be activated when the action
specified in the action/events field occurs. Select the functions from the list of eight
functions defined in CasSetup.h. (e.g., START_COLLECT). When NONE is specified
in this column, no function is executed.
18.7
Parameters
Table 18-2: CAS Parameters
Parameter #1
Parameter #2
These columns are used as the functions parameters. The list of global
parameters can be found in CasSetup.h.
If a parameter is not essential, the parameter is marked None.
Parameter #3
Version 4.8
435
January 2006
Mediant 3000
List of available user-functions and their parameters:
SET_TIMER (timer number, timeout) - Set timers that are managed per Bchannel, and their expiration triggers the state machine table. Each protocol
table/state machine can use up to 8 timers per B-channel/call, (timeout in msec).
SEND_CAS (AB value, CD value) - ABCD bits are sent as line signaling for the
specific channel when the call is setup.
SEND_EVENT (event type, cause) - The specific event type is sent to the
host/user and retrieved by applying acGetEvent().
SEND_DEST_NUM - Enbloc dialing: Enbloc dialing: refers to the digits string

located in the acPSTNPlaceCall function. Three types are available: (1)
DestPhoneNum (2) InterExchangePrefixNum (3) SourcePhoneNum.
DEL_TIMER (timer number) - Delete specific or all timers (0 for all) for the Bchannel.
START_COLLECT - Initiates the collection of address information i.e. the dialed

(destination) number for incoming calls where appropriate according to the
protocol. At the time between START_COLLECT and STOP_COLLECT, no digit
is reported to the user (EV_DIGIT is blocked) and the destination number is
reported in the EV_INCOMING_CALL_DETECTED event.
STOP_COLLECT - See START_COLLECT.
SET_COUNTER (counter number, counter value or NONE) - Set counters that

are managed per B-channel and their expiration triggers the state machine. The
counter initialization value should be a non-negative number. To delete all timers,
perform this function with 0 in the counter number field.
DEC_COUNTER (counter number) - Decreases counter value by 1. When the

counter value reaches 0, EV_COUNTERx_EXPIRES is sent to the table (The x
represent the counter number).
SEND_MF (MF type, MF digit or index or NONE, MF sending time) - This

function is used only with MFC/R2 protocols.
The Channel Parameter structure contains three parameters regarding sending digits.
1.
User's Manual
AddressVector and ANIDigitVector - These parameters are initialized when

using a PlaceCall function. When the code reaches the dialing section, it sends
MF digit according to the MF type specified in the MF type cell (the types are
defined in CASSetup.h file):
ADDRESS - Sends the digit from the address vector (destination number)
according to the index requested. (Refer to the Index definition).
ANI - Sends the digit from the ANI vector (source number) according to the
index requested.
SPECIFIC - Sends the MF digit specified in the Parameter #2 rubric.
SOURCE_CATEGORY - Sends the pre-defined source category MF digit.

The source category digit is set as the SourceNumberingType parameter
when using a PlaceCall function. The second and third parameters have no
use when using this type.
TRANSFER_CAPABILITY - Send the pre-defined line category MF digit.

The line category digit is set as the TransferCapability parameter when using
a PlaceCall function. The second and third parameters have no use when
using this type.
436
User's Manual
2.
3.
Index - Specifies the Offset of the next digit to be sent from the vector
(ADDRESS or ANI types described above):
Index 1 - Used to send the next digit in the vector.
Index -n - Used to send the last n digit. Underflow can occur if n is greater
than the number of digits sent so far.
Index 0 - Used to send the last sent digit.
Index SEND_FIRST_DIGIT - Used to start sending the digits vector from the
beginning.
(Refer to CASSetup.h.)
MF Send Time - This send time parameter specifies the maximum transmission
time of the MF.
STOP_SEND_MF - Stops sending the current MF.
SEND_PROG_TON - Operation, Tone or NONE.
- Two operations are available.
18.8
Sends the Call Progress Tone specified in the Parameter #2 rubric (The
second parameter can be taken from CASsetup.h).
Stops sending the last parameter.
CHANGE_COLLECT_TYPE (Collect Type) - Used only in MFCR2 protocol

by the incoming user to indicate his waiting for the reception of the MF digit
of the requested type. The type can be one of the following:
ADDRESS - The user is waiting for the reception of address digits.
ANI - The user is waiting for the reception of ANI digits.
SOURCE_CATEGORY - The user is waiting for the reception of the source

category.
TRANSFER_CAPABILITY - The user is waiting for the reception of the

source transfer capability (line category).
Next State
The Next State column contains the next state the table moves to after executing the
function for that action/event line. When the user selects to stay in the same state,
insert NO_STATE or use the current state.
Note the difference between NO_STATE and the current state name in this field. If the
user selects to stay in the same current state, the unconditional actions (FUNCTION0)
at the beginning of the state are performed. In contrast, NO_STATE skips these
functions and waits for another action to come.
Reserved word DO must be written in the next state field if the unconditional actions
(FUNCTION0) at the beginning of the state are used.
18.9
Changing the Script File
18.9.1
General
Version 4.8
CAS bouncing is filtered globally for each received CAS for each channel. The
437
January 2006
Mediant 3000
User defines the time for the filtering criteria in the protocol table file (see
INIT_DEBOUNCE), and this is above the bouncing in the DSP detection of 30
msec.
18.9.2
User's Manual
ANI/CLI is enabled using ST_INIT ANI parameter with 'YES'. ANI/CLI is

supported using EV_ANI_NUM_DETECTED as the table action for collecting the
ANI number in an incoming call. For outgoing calls, the table's function
SEND_DEST_NUM with ANI parameter l initiates ANI dialing. The ANI number is
provided by the User in the Source phone number parameter of
acPSTNPlaceCall().
MFC R2 protocol
Use the SEND_MF script function to generate the outgoing call destination
number. In this case, the first parameter should be ADDRESS (or ANI for source
phone number) and the second parameter -3 to 1 (+1), indicating which digit is
sent out of the number that the string conveyed by the User in the
acPSTNPlaceCall().
(+1) implies sending of next digit, 0 implies repeat of last digit, and -1 implies last
but one digit. This parameter actually changes the pointer to the phone number
string of digits. Thus, a one-to-one mapping with the MF backward signals of the
R2 protocol exists.
Using the parameter SEND_FIRST_DIGIT initiates resending the string from the
beginning, (change the pointer back to first digit and then proceed as above).
This parameter is defined in CASSetup.h.
When MFC/R2 protocol is used, the two detectors (opened by default) are the
Call Progress Tones and MFC/R2 Forward MF. When the User invokes outgoing
call via acPSTNPlaceCall(), MFC/R2 Forward MF detector is replaced with
MFC/R2 Backward MF detector, since only two detectors per DSP channel are
permitted to operate simultaneously.
The correct MF is automatically generated according to the call direction Forward for outgoing calls and Backward for incoming calls.
MFC/R2 protocol fault could cause a channel block. In this case, the script file
provided by AudioCodes releases the call to enable the User to free the call
resources and be notified about being in blocking state.
START_COLLECT and STOP_COLLECT must be used in the script file for MF

collecting both in outgoing and incoming calls. Warning: If this script function isn't
used, the script gets stuck and forward\backward MF are not detected.
The Ringback Call Progress Tone is translated to a unique event

acEV_PSTN_ALERTING, since the Ringback tone is actually used in all
AudioCodes protocols' state machines. All other Call Progress Tones are
conveyed via the acEV_TONE_DETECTED, and retrieved by the User according
to their type and index (note that the Ringback tone should be defined in the Call
Progress Tones table with the relevant type in order to get this event).
When the tone detection event is received, Users can perform any action. For
example, if the event is received with BUSY tone indication, Users can invoke
acPSTNDisconnectCall() to end the call.
The MFR2 destination number is collected using:

EXPECTED_NUM_OF_DIGITS_MINUS_1 parameter for SET_COUNTER that
the User defines at UserProt_defines_R2_MF.h. The counter function is used to
trigger the script file for the last-but-one received, after receiving the last digit, the
438
User's Manual

script file (acting as the outgoing register) initiates the A6/A3 FWD MF. Normally
variant supports end of digit information (MF15) or silence at the end of the
dialing (when MF15 is not used), a short pulse of MF3 (A3) is sent to indicate that
the entire string of digits (according to Q442, 476) is received.
Sending Group B digit by an incoming register requires invoking

acCASAcceptCall() with a certain reason parameter. Six reason parameters are
available:
1.
CALLED_IDLE - Subscribers line is free. Continue the call sequence. Usually

should be followed by accept or reject.
2.
CALLED_BUSY - Subscriber line is busy. Perform disconnect procedures.
3.
CALLED_CONGESTION - Congestion encountered. Perform disconnect

procedures.
4.
CALLED_UNALLOCATED - Dial number was not allocated. Perform

disconnect procedures.
5.
CALLED_RESERVE1 - Reserved for additional group B (user additional

requirements).
6.
CALLED_RESERVE2 - Reserved for additional group B (user additional

requirements).
Each reason generates a specific action, defined by the User, who modifies the
script file. The action is then used to generate/respond with a group B MF (free,
busy, etc.).
Transfer Capability - This parameter of acPSTNPlaceCAll() function is used by

the outgoing register to generate the service nature of the originating equipment.
In most variants (countries) this is the same as the Calling Subscriber Categories
but in some countries it is different, such as in R2 china protocol, it is referred to
as the KD (Group II) digit.
Note: This parameter only receives the MF values from the

acTISDNTransferCapability enumerator. Choose the MF digit according to
the service type that should be sent.
Source Category - This parameter of acPSTNPlaceCall() function determines the

calling subscriber category. For example: subscriber with priority, subscriber
without priority etc. This parameter is usually sent as part of the Group II forward
digits (except for R2 china where it is sent as the KA digit using Group I forward
digits).
Note: Applicable only to MFC-R2 protocol type.
Version 4.8
439
January 2006
User's Manual
19
19. Appendix - CAS to Analog Mapping Protocol
Appendix - CAS to Analog Mapping

Protocol
This appendix describes the BOARD_TYPE implementation of the AudioCodes
proprietary CAS to Analog Mapping Protocol.
Note 1: There is no standard protocol that defines how to map CAS to Analog.
Note 2: This mapping protocol is only supported in MEGACO.
Note 3: Currently only MelCAS, Ground Start and Loop Start CAS protocols are
supported.
When configuring the BOARD_TYPE to work in this mode (when the physical PSTN
layer is CAS) the gateway will appear as a regular Analog Gateway to the GWC (GW
controller). The gateway will support Analog packages and will translate them to CAS
commands (signals).
Figure 19-1: CAS to Analog Mapping Protocol
In this configuration, the following line to trunk/b-channel mapping is described in the

table below.
Version 4.8
441
January 2006
Mediant 3000
Table 19-1: Trunk/B-channel Mapping

Trunking Channels
Analog Channels
Trunk 1
b-channel 1
line 1
Trunk 1
b-channel 2
line 2
...
...
...
Trunk 1
b-channel 15
line 15
Trunk 1
b-channel 16
- (see note below)
Trunk 1
b-channel 17
line 16
Trunk 1
b-channel 18
line 17
...
...
...
Trunk 2
b-channel 1
line 31
Trunk 2
b-channel 2
Line 32
Trunk 3
b-channel 1
Line 61
Note: B-Channel 16 in each trunk is skipped as it used for CAS signaling.
Table 19-2: Mapping Table

CAS
User's Manual
Analog
442
MEGACO
User's Manual
Table 19-2: Mapping Table

CAS
Analog
MEGACO
Incoming CAS -->
Analog relevant
detection -->
MEGACO relevant event
Clear Back/Forward
On Hook
al/on event
Release
On Hook
al/on event
Answer/Re-Answer
Off Hook
al/of event
Seize
Off Hook
al/of event
Flash On/Off
Flash Hook
al/fl event
Outgoing CAS
<- Analog relevant

generation
<-- MEGACO relevant

signals/command
Block
Option 1:
Modify physical termination state to
InService command
Option 2:
Service Change on physical
termination with Force method
command
Unblock
Option 1:
Modify physical termination state to
OutOfService command
Option 2:
Service Change on physical
termination with Restart method
command
Answer
Line side answer
xal/las signal
Clear (Back)
Network disconnect
xal/nd signal
Release process
subtract physical termination command
Ring On/Off
Ringing
alert/ri signal
Version 4.8
443
January 2006
Mediant 3000
19.1
ini File Configuration

To enable CAS to Analog mapping, take these 3 steps:
19.2
1.
Configure the board as a CAS gateway with the relevant PSTN configuration and
CAS table.
2.
Configure the MEGACO relevant parameters.
3.
Set the TrunkingToAnalogFunctionalityProfile to 1.
MELCAS Call Flow Examples

The following are a number of different MELCAS Call Flow examples.
19.2.1
Establishing a Normal Call

The following examples relate to establishing a Normal Call.
19.2.1.1
PSTN Originate
The following is an example of a PSTN Originate call.
Figure 19-2: Establishing Normal Call - PSTN Originate
End User
MUX
MEGACO
IDLE (1101)()
On Hook()
IDLE (1101)()
Idle state
T=495{C=1001{MF=tp1{SG{alert/ri{pattern=1,NC={TO,IBE,IBS,OR}}}}}}()
Ring On (1011 for 350ms)()
Ring On()
Ring Off (1001 for 220ms)()
Ring Off()
Loop of Ring On <-> Ring Off

400ms, 200ms, 400ms, 2000ms.
Off Hook()
Answer (0101)()
Connected (0101)()
T=4{C=1001{N=tp1{OE=137{al/of{init=off}}}}}()
Call in process
User's Manual
444
User's Manual
19.2.1.2
PSTN Terminate
The following is an example of a PSTN Terminate call.
Figure 19-3: Establishing Normal Call - PSTN Terminate
End User
MEGACO
MUX
IDLE (1101)()
On Hook()
IDLE (1101)()
Idle state
Off Hook()
Seize (0101)()
T=17{C=-{N=tp0{OE=123{al/of{init=off}}}}}()
T=487{C=${A=tp0{M{O{MO=RC,tdmc/gain=0 }},E=128{al/on{strict=state},g/sc,xdd/xce{DM={(E|F)}}},SG{cg/dt}}}}()
Dial Tone()
Dial Tone()
Dial()
DTMF/MFR1 (0101) OR DP (0101/1101)()
Dial ended - await answer()
Wait For Answer (0101)()
T=3{C=1000{N=tp0{OE=128{timestamp:xdd/xce{ds="5201701",Meth=FM}}}}}()
T=487{C=${Modify=tp0{SG{xal/las}}}}()
Answer (0101)()
T=497{C=1001{MF=tp1{M{O{MO=SR,tdmc/gain=0 }},E=140{g/sc}}}}()
Call in process
19.2.2
Disconnect Process
The following examples relate to the Disconnect Process.
Version 4.8
445
January 2006
Mediant 3000
19.2.2.1
TEST Clear the Call

The following is an example of TEST Clear the Call.
Figure 19-4: Disconnect Process - TE Clear the Call
End User
MUX
MEGACO
Call in process
On Hook()
Clear back/forward (1101)()
T=6{C=1006{N=tp0{OE=140{al/on}}}}()
T=502{C=1006{S=tp0{AT{}}}}()
Disconnect Clear (0001 for 480ms)()
Release (1101)()
Idle state
19.2.2.2
PSTN Clear with Explicit Disconnect Signal

The following is an example of PSTN Clear with Explicit Disconnect Signal.
Figure 19-5: Disconnect Process - PSTN Explicit Disconnect Signal.
End User
MUX
MEGACO
Call in process
T=502{C=1000{MF=tp0{S{xal/nd}}}}()
Clear (1101)()
Clear (Forward or Backward)()
On Hook()
Release (1101)()
T=6{C=1006{N=tp0{OE=140{al/on}}}}()
T=502{C=1006{S=tp0{AT{}}}}()
Release (1101)()
Idle state
User's Manual
446
User's Manual
19.2.2.3
Release Call Without Explicit Disconnect Signal

The following is an example of Release Call Without Explicit Disconnect Signal.
Figure 19-6: Release Call Without Explicit Disconnect Signal
End User
MEGACO
MUX
Call in process
T=502{C=1006{S=tp0{AT{}}}}()
Clear (1101)()
Clear (Forward or Backward)()
On Hook()
Release (1101)()
T=6{C=1006{N=tp0{OE=140{al/on}}}}()
Release (1101)()
Idle state
19.2.3
Re-Answer Scenario
The following examples relate to the Re-answer scenario.
19.2.3.1
PSTN Originate
The following is an example of PSTN Originate.
Figure 19-7: Re-answer Scenario - PSTN Originate
End User
MEGACO
MUX
Call in process
On Hook()
Clear Back (1101)()
T=6{C=-{N=tp0{OE=140{al/on}}}}()
Off Hook()
Re-Answer (0101)()
T=17{C=-{N=tp0{OE=123{al/of{init=off}}}}}()
Call in process
Version 4.8
447
January 2006
Mediant 3000
19.2.3.2
PSTN Terminate
The following is an example of PSTN Terminate.
Figure 19-8: Re-answer Scenarion - PSTN Terminate
End User
MEGACO
MUX
Call in process
T=502{C=1000{MF=tp0{S{xal/nd}}}}()
Clear Back (1101)()
T=502{C=1000{MF=tp0{S{xal/las}}}}()
Connected (0101)()
Call in process
19.2.4
Flash Hook Detection
The following examples relate to Flash Hook Detection.

Figure 19-9: Flash Hook Detection
End User
MEGACO
MUX
Call in process
Flash()
Flash On (0001 for 53ms to 103ms)()
Flash Off (0101)()
T=6{C=1006{N=tp0{OE=140{al/fl}}}}()
Call in process
User's Manual
448
User's Manual
19.2.5
Blocking and Unblocking Process

The following examples relate to the Blocking and Unblocking Process.
Figure 19-10: Blocking and Unblocking Process
End User
MUX
MEGACO
Idle state
T=478{C=-{SC=tp0{SV{MT=FO,RE="906",TimeStamp}}}}()
Block (1111)()
T=479{C=-{SC=tp0{SV{MT=RS,RE="900",TimeStamp}}}}()
UnBlock (1101)()
Idle state
19.3
Pulse Dial Detection

Pulse Dial detection is the detection of pulse dialed digits via the ABCD CAS bits.
This feature provides pulse dial signaling detection to be able to work with pulse dial
telephone endpoints.
Note 1: Pulse dial detection does not prevent the detection of digits that were dialed
via any other method (e.g., DTMF).
Note 2: There is NO generation of dial pulses, only detection.
19.4
ini File Configuration

To
enable
the
pulse
dial
detection,
the
user
TrunkingToAnalogFunctionalityProfile INI file the parameter to 1.
19.5
must
set
the
CAS Table Configuration

To configure a CAS table to work with pulse dial detection, refer to the CAS Protocol
Table Appendix, in the User Manual .
In order to work with pulse dial detection, some parameters must be exist and initiated
in the UserProt_defines_xxx.h file, as described in sub clause 3.1 in the CAS Protocol
Table appendix.
The parameters are:
ABCD_DURING_BREAK - the ABCD CAS bits pattern during the break interval.
ABCD_DURING_MAKE - the ABCD CAS bits pattern during the make interval.
Version 4.8
449
January 2006
Mediant 3000
PULSE_DIAL_BREAK_MINIMUM_TIME the minimum break interval time.

PULSE_DIAL_BREAK_MAXIMUM_TIME the maximum break interval time.
PULSE_DIAL_MAKE_MAXIMUM_TIME the minimum make Interval time.
PULSE_DIAL_INTER_DIGIT_MINIMUM_TIME - The minimum time between 2 pulse
dial digits.
PULSE_DIAL_INTER_DIGIT_MAXIMUM_TIME - The maximum time between 2 pulse
dial digits in the same dialed number.
When a pulse dial digit is detected, a timer is set for this time. If another digit is
detected before the timer expires, the new digit is considered part of the same dialed.
When this timer expires, the last digit that was detected will be considered as the last
digit of the dialed number and an appropriate event will be sent to the host.
Note 1: When enabling pulse dial detection (by setting the TrunkingTo
AnalogFunctionalityProfile INI file the parameter to 1) these parameters
MUST exist and be initiated in the CAS table, otherwise the trunk will not be
configured.
These parameters are already configured in the MelCAS CAS table.
User's Manual
450
User's Manual
20
20. Appendix - Security
Appendix - Security
This appendix describes the Mediant 3000's implementation of security protocols.
The following list specifies the available security protocols and their purposes:
IPSec
IKE
The IPSec and IKE protocols are part of the IETF standards for security issues. IPSec
and IKE are used together on the media gateway to provide security for control and
management protocols. The IPSec protocol is responsible for securing the data
streams. The IKE protocol (Internet Key Exchange) is responsible for obtaining the
IPSec encryption keys and encryption profile (known as IPSec Security Association).
IPSec is used by Mediant 3000 to assure confidentiality, authentication and integrity
for the following media types:
Control traffic, such as H.248 and MGCP
Management traffic, such as SNMP and HTTP
Note: Some Security features are optional and can be ordered or upgraded at a
future time.
Note: The RTP and RTCP streams cannot be secured by IPSec.
SSL/TLS - Secures Web access (HTTPS) and Telnet access.
RADIUS - Is utilized by the Embedded Web Server and Telnet server for
authentication.
Media Security - Allows encryption of voice traffic on the IP network.
Internal Firewall Allows filtering unwanted inbound traffic.
This section also contains network port usage information (useful for firewall
administrators) and recommended practices for keeping your network secure.
20.1
IPSec and IKE

IPSec and IKE protocols are part of the IETF standards for establishing a secured IP
connection between two applications (also referred to as peers). Providing security
services at the IP layer, IPSec and IKE are transparent to IP applications.
Note: Using IPSec reduces the channel capacity of the Mediant 3000 by 24
channels.
Version 4.8
451
January 2006
Mediant 3000
IPSec and IKE are used in conjunction to provide security for control (e.g., SIP) and
management (e.g., SNMP and Web) protocols but not for media (i.e., RTP, RTCP and
T.38).
IPSec is responsible for securing the IP traffic. This is accomplished by using the
Encapsulation Security Payload (ESP) protocol to encrypt the IP payload (illustrated in
the figure below). The IKE protocol is responsible for obtaining the IPSec encryption
keys and encryption profile (known as IPSec Security Association (SA)).
Figure 20-1: IPSec Encryption
20.1.1
IKE
IKE is used to obtain the Security Associations (SA) between peers (the gateway and
the application its trying to contact). The SA contains the encryption keys and profile
used by the IPSec to encrypt the IP stream. The IKE table lists the IKE peers with
which the gateway performs the IKE negotiation (up to 20 peers are available).
The IKE negotiation is separated into two phases: main mode and quick mode. The
main mode employs the Diffie-Hellman (DH) protocol to obtain an encryption key
(without any prior keys), and uses a pre-shared key to authenticate the peers. The
created channel secures the messages of the following phase (quick mode) in which
the IPSec SA properties are negotiated.
The IKE negotiation is as follows:
Main mode (the main mode creates a secured channel for the quick mode)
SA negotiation The peers negotiate their capabilities using four proposals.

Each proposal includes three parameters: Encryption method, Authentication
protocol and the length of the key created by the DH protocol. The keys
lifetime is also negotiated in this stage. For detailed information on
configuring the four-main mode proposals, refer to 'IKE Configuration' on
page 453.
Key exchange (DH) The DH protocol is used to create a phase-1 key.
Authentication The two peers authenticate one another using the preshared key (configured by the parameter IKEPolicySharedKey).
Quick mode (quick mode negotiation is secured by the phase-1 SA)
SA negotiation The peers negotiate their capabilities using four proposals.

Each proposal includes two parameters: Encryption method and
Authentication protocol. The lifetime is also negotiated in this stage. For
detailed information on configuring the four-quick mode proposals, refer to
the SPD table under 'IPSec Configuration' on page 457.
Key exchange a symmetrical key is created using the negotiated SA.
IKE Specifications:
User's Manual
452
User's Manual
20.1.2
Authentication mode - pre-shared key only
Main mode is supported for IKE Phase 1
Supported IKE SA encryption algorithms - DES and 3DES
Hash types for IKE SA - SHA1 and MD5
IPSec
IPSec is responsible for encrypting and decrypting the IP streams.
The IPSec Security Policy Database (SPD) table defines up to 20 IP peers to which
the IPSec security is applied. IPSec can be applied to all packets designated to a
specific IP address or to a specific IP address, port (source or destination) and
protocol type.
Each outgoing packet is analyzed and compared to the SPD table. The packet's
destination IP address (and optionally, destination port, source port and protocol type)
are compared to each entry in the table. If a match is found, the gateway checks if an
SA already exists for this entry. If it doesnt, the IKE protocol is invoked (refer to
Section 1.1.1 above) and an IPSec SA is established. The packet is encrypted and
transmitted. If a match is not found, the packet is transmitted un-encrypted.
Note 1: An incoming packet whose parameters match one of the entries of the SPD
table but is received un-encrypted, is dropped.
Note 2: IPSec does not function properly if the gateways IP address is changed
on-the-fly. Therefore, reset the gateway after you change its IP address.
IPSec Specifications:
20.1.3
Transport mode only
Encapsulation Security Payload (ESP) only
Support for Cipher Block Chaining (CBC)
Supported IPSec SA encryption algorithms - DES and 3DES
Hash types for IPSec SA are SHA1 and MD5
Configuring IPSec and IKE

To enable IPSec and IKE on the Mediant 3000 set the ini file parameter EnableIPSec
to 1.
20.1.3.1
IKE Configuration
The parameters described in the table below are used to configure the first phase
(main mode) of the IKE negotiation for a specific peer. A different set of parameters
can be configured for each of the 20 available peers.
Version 4.8
453
January 2006
Mediant 3000
Table 20-1: IKE Table Configuration Parameters

Parameter Name
Description
Shared Key
Determines the pre-shared key (in textual format).
[IKEPolicySharedKey]
Both peers must register the same pre-shared key for the
authentication process to succeed.
Note 1: The pre-shared key forms the basis of IPSec security and
should therefore be handled cautiously (in the same way as sensitive
passwords). It is not recommended to use the same pre-shared key
for several connections.
Note 2: Since the ini file is in plain text format, loading it to the
Mediant 3000 over a secure network connection is recommended,
preferably over a direct crossed-cable connection from a
management PC. For added confidentiality, use the encoded ini file
option (described in Encoding Mechanism on page 96).
Note 3: After it is configured, the value of the pre-shared key cannot
be obtained via Web, ini file or SNMP.
First to Fourth Proposal

Encryption Type
Determines the encryption type used in the main mode negotiation

for up to four proposals.
[IKEPolicyProposal
Encryption_X]
X stands for the proposal number (0 to 3).

The valid encryption values are:
Not Defined (default)
DES-CBC
[1]
Triple DES-CBC
[2]

Authentication Type
Determines the authentication protocol used in the main mode

negotiation for up to four proposals.
[IKEPolicyProposal
Authentication_X]

The valid authentication values are:
HMAC-SHA1-96)
[2]
HMAC-MD5-96 [4]
First to Fourth Proposal DH
Group
Determines the length of the key created by the DH protocol for up to

four proposals.
[IKEPolicyProposal
DHGroup_X]

The valid DH Group values are:
IKE SA LifeTime (sec)

[IKEPolicyLifeInSec]
DH-786-Bit
[0]
DH-1024-Bit
[1]
Determines the time (in seconds) the SA negotiated in the first IKE
session (main mode) is valid. After the time expires, the SA is renegotiated.
The default value is 28800 (8 hours).
User's Manual
454
User's Manual
Table 20-1: IKE Table Configuration Parameters

Parameter Name
Description
IKE SA LifeTime (KB)
Determines the lifetime (in kilobytes) the SA negotiated in the first

IKE session (main mode) is valid. After this size is reached, the SA is
re-negotiated.
[IKEPolicyLifeInKB]
The default value is 0 (this parameter is ignored).

The lifetime parameters (IKEPolicyLifeInSec and IKEPolicyLifeInKB) determine the duration the SA
created in the main mode phase is valid. When the lifetime of the SA expires, it is automatically
renewed by performing the IKE first phase negotiations. To refrain from a situation where the SA
expires, a new SA is being negotiated while the old one is still valid. As soon as the new SA is
created, it replaces the old one. This procedure occurs whenever an SA is about to expire.
If no IKE methods are defined (Encryption / Authentication / DH Group), the default

settings (shown in the table below) are applied.
Table 20-2: Default IKE First Phase Proposals

Encryption
Authentication
DH Group
Proposal 0
3DES
SHA1
1024
Proposal 1
3DES
MD5
1024
Proposal 2
3DES
SHA1
786
Proposal 3
3DES
MD5
786
To configure the IKE table using the ini file:

The IKE parameters are configured using ini file tables (described in 'Tables in the
Uploaded ' on page 96ini 'File' on page 96). Each line in the table refers to a different
IKE peer.
The Format line (IKE_DB_INDEX in the example below) specifies the order in which
the actual data lines are written. The order of the parameters is irrelevant. Parameters
are not mandatory unless stated otherwise. To support more than one Encryption /
Authentication / DH Group proposals, for each proposal specify the relevant
parameters in the Format line. Note that the proposal list must be contiguous. The
following is an example of an IKE Table.
[IPSec_IKEDB_Table]
Format IKE_DB_INDEX = IKEPolicySharedKey,
IKEPolicyProposalEncryption_0, IKEPolicypRoposalAuthentication_0,
IKEPolicyProposalDHGroup_0, IKEPolicyProposalEncryption_1,
IKEPolicypRoposalAuthentication_1, IKEPolicyProposalDHGroup_1,
IKEPolicyLifeInSec;
IPSEC_IKEDB_TABLE 0 = 123456789, 1, 2, 0, 2, 2, 1, 28800;
Version 4.8
455
January 2006
Mediant 3000
[\IPSEC_IKEDB_TABLE]
In the example above, a single IKE peer is configured. Its pre-shared key is
123456789. Two security proposals are configured: DES/SHA1/786DH and
3DES/SHA1/1024DH. In addition, a lifetime of 28800 seconds is applied.
To configure the IKE table using the Embedded Web Server, take
these 7 steps:
1.
Access the Mediant 3000 Embedded Web Server (refer to 'Embedded Web
2.
Open the Security Settings screen (Advanced Configuration menu > Network
Settings > Security Settings option). The Security Settings screen is displayed.
3.
Open the IKE Table screen by clicking the arrow sign (-->) to the right of the IKE
Table label. The IKE Table screen is displayed.
Figure 20-2: IKE Table Screen
User's Manual
4.
In the Policy Index drop-down list, select the peer you want to edit (up to 20
peers can be configured).
5.
Configure the IKE parameters according to the table, ''IKE Table Configuration
Parameters'' on page 454.
6.
Press the button Create; a row is created in the IKE table.
456
User's Manual
7.
Burn to flash and reboot.
To delete a peer from the IKE table, select it in the Policy Index drop-down list, press
the Delete button and, at the prompt, press OK.
20.1.3.2
IPSec Configuration
The parameters described in the table below are used to configure the SPD table. A
different set of parameters can be configured for each of the 20 available IP
destinations.
Table 20-3: SPD Table Configuration Parameters

Parameter Name
Description
Remote IP Address
Defines the destination IP address (or a

FQDN) the IPSec mechanism is applied
to.
[IPSecPolicyRemoteIPAddress]
This parameter is mandatory.

Note: When a FQDN is used, a DNS
server must be configured
(DNSPriServerIP).
Local IP Address Type
If multiple IPs/Vlans are configured, the

user should define the required local
[IPSecPolicyLocalIPAddressType]
interface on which to apply encryption.
Valid Address Type values are:
OAM interface
[0]
Control interface
[2]
Default value is 0 (Control interface)

Source Port
[IPSecPolicySrcPort]
Defines the source port the IPSec

mechanism is applied to.
The default value is 0 (any port).
Destination Port
[IPSecPolicyDstPort]
Defines the destination port the IPSec

IPSec is applied to
outgoing packets
whose IP address,
destination port,
source port and
protocol type match
the values defined
for these four
parameters.
The default value is 0 (any port).

Protocol
[IPSecPolicyProtocol]
Defines the protocol type the IPSec

0 = Any protocol (default)
17 = UDP
6 = TCP
Or any other protocol type defined by
IANA (Internet Assigned Numbers
Authority).
Related Key Exchange Method

Determines the index for the corresponding IKE entry. Note that
Index
several policies can be associated with a single IKE entry.
[IPsecPolicyKeyExchangeMethod
The valid range is 0 to 19. The default value is 0.
Index]
Version 4.8
457
January 2006
Mediant 3000
Table 20-3: SPD Table Configuration Parameters

Parameter Name
Description
IKE Second Phase Parameters (Quick Mode)

SA Lifetime (sec)
[IPsecPolicyLifeInSec]
Determines the time (in seconds) the SA negotiated in the

second IKE session (quick mode) is valid. After the time
expires, the SA is re-negotiated.
The default value is 28800 (8 hours).
SA Lifetime (KB)
[IPSecPolicyLifeInKB]
Determines the lifetime (in kilobytes) the SA negotiated in the

second IKE session (quick mode) is valid. After this size is
reached, the SA is re-negotiated.
The default value is 0 (this parameter is ignored).
The lifetime parameters (IPsecPolicyLifeInSec and IPSecPolicyLifeInKB) determine the duration an

SA is valid. When the lifetime of the SA expires, it is automatically renewed by performing the IKE
second phase negotiations. To refrain from a situation where the SA expires, a new SA is being
negotiated while the old one is still valid. As soon as the new SA is created, it replaces the old one.
This procedure occurs whenever an SA is about to expire.
First to Fourth Proposal Encryption
Type
Determines the encryption type used in the quick mode

[IPSecPolicyProposalEncryption
_X]

The valid encryption values are:
None
[0] = No encryption
DES-CBC
[1]
Triple DES-CBC
[2]

Authentication Type
Determines the authentication protocol used in the quick mode

[IPSecPolicyProposal
Authentication_X]

The valid authentication values are:
HMAC-SHA-1-96
[2]
HMAC-MD5-96
[4]
If no IPsec methods are defined (Encryption / Authentication), the default settings

(shown in the table below) are applied.
Table 20-4: Default IKE Second Phase Proposals

Encryption
Authentication
Proposal 0
3DES
SHA1
Proposal 1
3DES
MD5
Proposal 2
DES
SHA1
User's Manual
458
User's Manual
Table 20-4: Default IKE Second Phase Proposals

Encryption
Proposal 3
Authentication
DES
MD5
To configure the SPD table using the ini file:

SPD table is configured using ini file tables (described in ini' File Structure' on page
91). Each line in the table refers to a different peer/traffic type combination.
The Format line (SPD_INDEX in the example below) specifies the order in which the
actual data lines are written. The order of the parameters is irrelevant. Parameters are
not mandatory unless stated otherwise. To support more than one Encryption /
Authentication proposals, for each proposal specify the relevant parameters in the
Format line. Note that the proposal list must be contiguous. The following is an
example of an SPD Table
[ IPSEC_SPD_TABLE ]
Format SPD_INDEX = IPSecPolicyRemoteIPAddress, IpsecPolicySrcPort,
IPSecPolicyDStPort,IPSecPolicyProtocol, IPSecPolicyLifeInSec,
IPSecPolicyProposalEncryption_0,
IPSecPolicyProposalAuthentication_0,
IPSecPolicyProposalEncryption_1,
IPSecPolicyProposalAuthentication_1,
IPSecPolicyKeyExchangeMethodIndex, IPSecPolicyLocalIPAddressType;
IPSEC_SPD_TABLE 0 = 10.11.2.21, 0, 0, 17, 900, 1,2, 2,2 ,1,0;
[ \IPSEC_SPD_TABLE ]
In the SPD example above, all packets designated to IP address 10.11.2.21 and
originating from the OAM interface (regardless to their destination and source ports)
and whose protocol is UDP, are encrypted. The SPD also defines an SA lifetime of
900 seconds and two security proposals: DES/SHA1 and 3DES/SHA1.
To configure the SPD table using the Embedded Web Server, take
these 7 steps:
Version 4.8
1.
Access the Mediant 3000 Embedded Web Server (refer to 'Embedded Web
2.
Open the Security Settings screen (Advanced Configuration menu > Network
Settings > Security Settings option). The Security Settings screen is displayed.
459
January 2006
Mediant 3000
3.
Open the IPSec Table screen by clicking the arrow sign (-->) to the right of the
IPSec Table label. The IPSec Table screen is displayed.
Figure 20-3: IPSec Table Screen
4.
In the Policy Index drop-down list, select the rule you want to edit (up to 20 rules
can be configured).
5.
Configure the SPD parameters according to the table, ''SPD Table Configuration
Parameters'' on page 457.
6.
Press the button Create;.a row is created in the SPD table.
7.
Burn to flash and Re-boot.
To delete a peer from the SPD table, select it in the Policy Index drop-down list,
press the Delete button and, in the prompt, press OK.
20.1.3.3
IPSec and IKE Configuration Tables Confidentiality

Since the pre-shared key parameter of the IKE table must remain undisclosed,
measures are taken by the Mediant 3000 ini file, the Embedded Web Server and
SNMP agent to maintain this parameters confidentiality. On the Embedded Web
Server a list of asterisks is displayed instead of the pre-shared key. On SNMP, the
pre-shared key parameter is a write-only parameter and cannot be read. In the ini file,
the following measures to assure the secrecy of the IPSec and IKE tables are taken:
User's Manual
Hidden IPSec and IKE tables - When uploading the ini file from the gateway the
IPSec and IKE tables are not available. Instead, the notifications (shown in the
example below) are displayed. The following is an example of an ini File
Notification of Missing Tables.
460
User's Manual
;
; *** TABLE IPSEC_IKEDB_TABLE ***
; This table contains hidden elements and will not be exposed.
; This table exists on board and will be saved during restarts
;
;
; *** TABLE IPSEC_SPD_TABLE ***
; This table contains hidden elements and will not be exposed.
; This table exists on board and will be saved during restarts
;
Preserving the values of the parameters in the IPSec and IKE tables from
one ini file loading to the next The values configured for the parameters in
the IPSec tables in the ini file are preserved from one loading to another. If a
newly loaded ini file doesnt define IPSec tables, the previously loaded tables
remain valid. To invalidate a previously loaded ini file's IPSec tables, load a new
ini file with an empty IPSec table.
i.e.
[IPSec_IKEDB_Table]
[\IPSec_IKEDB_Table]
[IPSEC_SPD_TABLE]
[\IPSEC_SPD_TABLE]
20.2
SSL/TLS
SSL (the Secure Socket Layer), also known as TLS (Transport Layer Security), is the
method used to secure the Mediant 3000's Embedded Web Server and Telnet server.
The SSL protocol provides confidentiality, integrity and authenticity of the Web server.
Specifications for the SSL/TLS implementation:
20.2.1
Supported transports: SSL 2.0, SSL 3.0, TLS 1.0
Supported ciphers: DES, RC4 compatible
Authentication: X.509 certificates; CRLs are not supported
Web Server Configuration

For additional security, you can configure the Web server to accept only secure
(HTTPS) connections. This is done by changing the ini file parameter, HTTPS Only or
via the Embedded Web Server, Network Settings screen (refer to ''Network Settings''
on page 218). You can also change the port number used for the secure Web server
(by default 443) by changing the ini file parameter, HTTPSPort.
20.2.2
Using the Secure Web Server

To use the secure Web server, take these 3 Steps:
1.
Version 4.8
Navigate your browser to the following URL:

461
January 2006
Mediant 3000
https://[hostname] or [ip address]

Depending on the browser's configuration, a security warning dialog may be
displayed. The reason for the warning is that the Mediant 3000's initial certificate is not
trusted by your PC. The browser may allow you to install the certificate, thus skipping
the warning dialog the next time you connect to the Mediant 3000
2.
If you are using Internet Explorer, click View Certificate and then Install
Certificate.
3.
The browser also warns you if the host name used in the URL is not identical to
the one listed in the certificate. To overcome this, add the IP address and host
name (ACL_nnnnnn where nnnnnn is the serial number of the Mediant 3000) to
your hosts file, located at /etc/hosts on UNIX or
C:\WINDOWS\SYSTEM32\DRIVERS\ETC\hosts on Windows; then use the host
name in the URL, e.g., https://ACL_280152 .Below is an example of a host file:
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.

# Location: C:\WINDOWS\SYSTEM32\DRIVERS\ETC\hosts
#
127.0.0.1
localhost
10.31.4.47
ACL_280152
20.2.3
Secure Telnet
The Mediant 3000 has an embedded Telnet server allowing easy command-line
access to the device configuration and management interface. The Telnet server is
disabled by default. To enable it, set the parameter, TELNETServerEnable to 1
(standard mode) or 2 (SSL mode).
No information is transmitted in the clear when using SSL mode.
If the Telnet server is set to SSL mode, a special Telnet client is required on your PC
to connect to the Telnet interface over a secure connection; examples include CKermit for UNIX, Kermit-95 for Windows, and AudioCodes' acSSLTelnet utility for
Windows (which requires prior installation of the free OpenSSL toolkit).
20.2.4
Server Certificate Replacement

The Mediant 3000 is shipped with a working SSL configuration consisting of a unique
self-signed server certificate. When a Mediant 3000 is upgraded to firmware version
4.6, a unique self-signed server certificate is created. If an organizational PKI (public
key infrastructure) is in place, you may wish to replace this certificate with one
provided by your security administrator.
To replace this certificate, take these 9 steps:

1.
Your network administrator should allocate a unique DNS name for the Mediant
3000 (e.g., dns_name.corp.customer.com). This name is used to access the
device, and should therefore be listed in the server certificate.
2.
Navigate your browser to the following URL (case-sensitive):
https://dns_name.corp.customer.com/SSLCertificateSR
Note that you should use the DNS name provided by your network administrator. The
Certificate Signing Request Web page is displayed.
User's Manual
462
User's Manual
3.
Enter the DNS name as the certificate subject (in the input box), and click
Generate CSR. The Web page displays a textual certificate signing request,
which contains the SSL device identifier
4.
Copy this text and send it to your security provider.
The security provider (also known as Certification Authority or CA) signs this request
and send you a server certificate for the device.
5.
Save the certificate in a file (e.g., cert.txt) and make sure it is a plain-text file with
the "BEGIN CERTIFICATE" header. Below is an example of a Base64-Encoded
X.509 Certificate.
-----BEGIN CERTIFICATE----MIIDkzCCAnugAwIBAgIEAgAAADANBgkqhkiG9w0BAQQFADA/MQswCQYDVQQGEwJG
UjETMBEGA1UEChMKQ2VydGlwb3N0ZTEbMBkGA1UEAxMSQ2VydGlwb3N0ZSBTZXJ2
ZXVyMB4XDTk4MDYyNDA4MDAwMFoXDTE4MDYyNDA4MDAwMFowPzELMAkGA1UEBhMC
RlIxEzARBgNVBAoTCkNlcnRpcG9zdGUxGzAZBgNVBAMTEkNlcnRpcG9zdGUgU2Vy
dmV1cjCCASEwDQYJKoZIhvcNAQEBBQADggEOADCCAQkCggEAPqd4MziR4spWldGR
x8bQrhZkonWnNm+Yhb7+4Q67ecf1janH7GcN/SXsfx7jJpreWULf7v7Cvpr4R7qI
JcmdHIntmf7JPM5n6cDBv17uSW63er7NkVnMFHwK1QaGFLMybFkzaeGrvFm4k3lR
efiXDmuOe+FhJgHYezYHf44LvPRPwhSrzi9+Aq3o8pWDguJuZDIUP1F1jMa+LPwv
REXfFcUW+w==
-----END CERTIFICATE-----
6.
Before continuing, set the parameter, HTTPSOnly = 0 to make sure you have a
method of accessing the device in case the new certificate is not working.
Restore the previous setting after testing the configuration.
7.
In the SSLCertificateSR Web page, locate the server certificate upload section.
8.
Click Browse and locate the cert.txt file, then click Send File.
9.
When the operation is complete, save the configuration and restart the device.
The Web server now uses the provided certificate.
Note 1: The certificate replacement process may be repeated as necessary, e.g.,

when the new certificate expires.
Note 2: It is possible to set the subject name to the IP address of the device (e.g.,
10.3.3.1) instead of a qualified DNS name. This practice is not
recommended, since the IP address is subject to changes and may not
uniquely identify the device.
20.2.5
Client Certificates
By default, Web servers using SSL provide one-way authentication. The client is
certain that the information provided by the Web server is authentic. When an
organizational PKI is in place, two-way authentication may be desired: both client and
server should be authenticated using X.509 certificates. This is achieved by installing
a client certificate on the management PC, and uploading the same certificate (in
base64-encoded X.509 format) to the Mediant 3000's Trusted Root Certificate Store.
The Trusted Root Certificate file should contain both the certificate of the authorized
user, and the certificate of the CA.
Since X.509 certificates have an expiration date and time, the Mediant 3000 must be
configured to use NTP (Network Time Protocol) to obtain the current date and time.
Without a correct date and time, client certificates cannot work.
Version 4.8
463
January 2006
Mediant 3000
To install a client certificate, take these 5 steps:

1.
Before continuing, set HTTPSONLY=0 to make sure you have a method of

accessing the device in case the client certificate is not working. Restore the
previous setting after testing the configuration.
2.
To upload the Trusted Root Certificate file, go to the Certificates Web page as
shown above and locate the trusted root certificate upload section.
3.
Access the Certificates screen (Advanced ConfigurationSecurity

SettingsCertificates).
4.
In the Certificates Web page, locate the server certificate upload section.
5.
Click Browse and locate the file, then click Send File.
6.
When the operation is complete, set the ini file parameter,

HTTPSRequireClientCertificates = 1.
7.
Save the configuration and restart the device.

When a user connects to the secure Web server:
If the user has a client certificate from a CA listed in the Trusted Root
Certificate file, the connection is accepted and the user is prompted for the
system password.
If both the CA certificate and the client certificate appear in the Trusted Root
Certificate file, the user is not prompted for a password (thus providing a
single-sign-on experience - the authentication is performed using the X.509
digital signature).
If the user does not have a client certificate from a listed CA, or does not
have a client certificate at all, the connection is rejected.
Note : The process of installing a client certificate on your PC is beyond the scope
of this document. For more information, refer to your Web browser or
operating system documentation, and/or consult your security administrator.
20.3
RADIUS Support
Users can enhance the security and capabilities of logging to the gateways Web and
Telnet embedded servers by using a Remote Authentication Dial-In User Service
(RADIUS) to store numerous usernames, passwords and access level attributes (Web
only), allowing multiple user management on a centralized platform. RADIUS (RFC
2865) is a standard authentication protocol that defines a method for contacting a
predefined server and verifying a given name and password pair against a remote
database, in a secure manner.
When accessing the Web and Telnet servers, users must provide a valid username
and password. When RADIUS authentication isnt used, the username and password
are authenticated with the Embedded Web Servers usernames and passwords of the
primary or secondary accounts or with the Telnet servers username and password
stored internally in the gateways memory. When RADIUS authentication is used, the
gateway doesnt store the username and password but simply forwards them to the
pre-configured RADIUS server for authentication (acceptance or rejection). The
internal Web / Telnet passwords can be used as a fallback mechanism in case the
RADIUS
server
doesnt
respond
(configured
by
the
parameter
BehaviorUponRadiusTimeout). Note that when RADIUS authentication is performed,
User's Manual
464
User's Manual

the Web / Telnet servers are blocked until a response is received (with a timeout of 5
seconds).
RADIUS authentication requires HTTP basic authentication, meaning the username
and password are transmitted in clear text over the network. Therefore, users are
recommended to set the parameter HttpsOnly = 1 to force the use of HTTPS, since
the transport is encrypted.
20.3.1
Setting Up a RADIUS Server

The following examples refer to FreeRADIUS, a free RADIUS server that can be
downloaded from http://www.freeradius.org. Follow the directions on that site for
information on installing and configuring the server. If you use a RADIUS server from
a different vendor, refer to its appropriate documentation.
To set up a RADIUS server, take these 5 steps:

1.
Define the gateway as an authorized client of the RADIUS server, with a

predefined shared secret (a password used to secure communication) and a
vendor ID. The figure below displays an example of the file clients.conf
(FreeRADIUS client configuration).
Example of the File clients.conf (FreeRADIUS Client Configuration)

#
# clients.conf - client configuration directives
#
client 10.31.4.47 {
secret
= FutureRADIUS
shortname
= tp1610_master_tpm
}
2.
If access levels are required, set up a VSA dictionary for the RADIUS server and
select an attribute ID that represents each user's access level. The following
example shows a dictionary file for FreeRADIUS that defines the attribute ACLAuth-Level with ID=35.
Example of a Dictionary File for FreeRADIUS (FreeRADIUS Client Configuration)

#
# AudioCodes VSA dictionary
#
VENDOR AudioCodes 5003
ATTRIBUTE ACL-Auth-Level 35 integer AudioCodes
VALUE ACL-Auth-Level ACL-Auth-UserLevel 50
VALUE ACL-Auth-Level ACL-Auth-AdminLevel 100
VALUE ACL-Auth-Level ACL-Auth-SecurityAdminLevel 200
#
# AudioCodes VSA dictionary
#
VENDOR AudioCodes 5003
ATTRIBUTE ACL-Auth-Level 35 integer AudioCodes
VALUE ACL-Auth-Level ACL-Auth-UserLevel 50
VALUE ACL-Auth-Level ACL-Auth-AdminLevel 100
3.
Version 4.8
In the RADIUS server, define the list of users authorized to use the gateway,
using one of the password authentication methods supported by the server
465
January 2006
Mediant 3000
implementation. The following example shows a user configuration file for
FreeRADIUS using a plain-text password.
Example of a User Configuration File for FreeRADIUS Using a Plain-Text
Password
# users - local user configuration database
john
Auth-Type := Local, User-Password == "qwerty"

Service-Type = Login-User,
ACL-Auth-Level = ACL-Auth-SecurityAdminLevel
larry
Auth-Type := Local, User-Password == "123456"

Service-Type = Login-User,
ACL-Auth-Level = ACL-Auth-UserLevel
20.3.2
4.
Record and retain the IP address, port number, shared secret, vendor ID and
VSA access level identifier (if access levels are used) used by the RADIUS
server.
5.
Configure the gateways relevant parameters according to the section below.
Configuring RADIUS Support

To configure RADIUS support on the gateway via the Embedded
Web Server, take these 13 steps:
1.
Access the Embedded Web Server (refer to 'Embedded Web Server' on page
202).
2.
Open the General Security Settings screen (Advanced Configuration menu >
Security Settings > General Security Settings option); the General Security
Settings screen is displayed.
3.
Under section General RADIUS Settings, in the field Enable RADIUS Access
Control, select Enable; the RADIUS application is enabled.
4.
In the field Use RADIUS for Web / Telnet Login, select Enable; RADIUS
authentication is enabled for Web and Telnet login.
5.
Enter the RADIUS server IP address, port number and shared secret in the
relevant fields.
6.
Under section RADIUS Authentication Settings, in the field Device Behavior

Upon RADIUS Timeout, select the gateways operation if a response isnt
received from the RADIUS server after the 5 seconds timeout expires:
Deny Access the gateway denies access to the Web and Telnet
embedded servers.
Verify Access Locally the gateway checks the local username and
password.
7.
In the field Local RADIUS Password Cache Timeout, enter a time (in seconds);
when this time expires, the username and password verified by the RADIUS
server becomes invalid and a username and password must be re-validated with
the RADIUS server.
8.
In the field Local RADIUS Password Cache Mode, select the gateways mode of
operation regarding the above-mentioned Local RADIUS Password Cache
Timer option:
User's Manual
Reset Timer Upon Access upon each access to a Web screen, the timer
466
User's Manual

resets (reverts to the initial value configured in the previous step).
9.
Absolute Expiry Timer - when you access a Web screen, the timer doesnt
reset but rather continues decreasing.
In the field RADIUS VSA Vendor ID, enter the vendor ID you configured in the
RADIUS server.
10. When using the Web access-level mechanism, perform one of the following
options:
When RADIUS responses include the access level attribute:

In the field RADIUS VSA Access Level Attribute, enter the code that
indicates the access level attribute in the Vendor Specific Attributes (VSA)
section of the received RADIUS packet.
When RADIUS responses dont include the access level attribute:

In the field Default Access Level, enter the default access level that is
applied to all users authenticated by the RADIUS server.
11. In the field Require Secured Web Connection (HTTPS), select HTTPS only.
It is important you use HTTPS (secure Web server) when connecting to the
gateway over an open network, since the password is transmitted in clear text.
For Telnet, use SSL TelnetServerEnable = 2.
12. Save the changes so they are available in case of a power failure.
13. Reset the gateway. Click the Reset button on the main menu bar; the Reset
screen is displayed. Click the button Reset.
After reset, when accessing the Web or Telnet servers, use the username and
password you configured in the RADIUS database. The local system password is still
active and can be used when the RADIUS server is down.
To configure RADIUS support on the gateway using the ini file:

1.
Add the following parameters to the ini file. For information on modifying the ini
file, refer to 'Modifying 'ini 'File Parameters via the AdminPage' on page 604.
EnableRADIUS = 1
WebRADIUSLogin = 1
RADIUSAuthServerIP = IP address of RADIUS server
RADIUSAuthPort = port number of RADIUS server, usually 1812
SharedSecret = your shared secret'
HTTPSOnly = 1
BehaviorUponRadiusTimeout = 1
RadiusLocalCacheMode = 1
RadiusLocalCacheTimeout = 300
RadiusVSAVendorID = your vendors ID
RadiusVSAAccessAttribute = code that indicates the access level attribute
DefaultAccessLevel = default access level (0 to 200)
The following table lists the different RADIUS Authentication Settings.
Version 4.8
467
January 2006
Mediant 3000
Table 20-5: RADIUS Authentication Settings

Device Behavior Upon
RADIUS Timeout
[BehaviorUponRadiusTimeou
t]
Defines the gateways operation if a response isnt received from the

RADIUS server after the 5 seconds timeout expires:
0 (Deny access) = the gateway denies access to the Web and Telnet
embedded servers.
1 (Verify Access locally) = the gateway checks the local username and
password (default).
Local RADIUS Password

Cache Mode
[RadiusLocalCacheMode]
Defines the gateways mode of operation regarding the timer (configured

by the parameter RadiusLocalCacheTimeout) that determines the validity
of the username and password (verified by the RADIUS server).
0 (Absolute Expiry Timer) = when you access a Web screen, the timeout
doesnt reset but rather continues decreasing.
1 (Reset Timer Upon Access) = upon each access to a Web screen, the
timeout always resets (reverts to the initial value configured by
RadiusLocalCacheTimeout).
Local RADIUS Password

Cache Timeout
[RadiusLocalCacheTimeout]
Defines the time (in seconds) the locally stored username and password
(verified by the RADIUS server) are valid. When this time expires, the
username and password becomes invalid and a must re-verified with the
RADIUS server.
The valid range is 1 to 0xFFFFFF. -1 = Never expires. 0 = Each request
requires RADIUS authentication.
The default value is 300 (5 minutes).
RADIUS VSA Vendor ID

[RadiusVSAVendorID]
Defines the vendor ID the gateway accepts when parsing a RADIUS

response packet.
The valid range is 0 to 0xFFFFFFFF. The default value is 5003.
RADIUS VSA Access Level

Attribute
[RadiusVSAAccessAttribute]
Defines the code that indicates the access level attribute in the Vendor
Specific Attributes (VSA) section of the received RADIUS packet.
The valid range is 0 to 255. The default value is 35.
Default Access Level

[DefaultAccessLevel]
Defines the default access level for the gateway when the RADIUS
(authentication) response doesnt include an access level attribute.
The valid range is 0 to 255. The default value is 200 (Security
Administrator').
20.4
Internal Firewall
The Mediant 3000 accommodates an internal access list facility, allowing the security
administrator to define network traffic filtering rules. The access list provides the
following features:
User's Manual
Block traffic from known malicious sources
Only allow traffic from known friendly sources, and block all others
Mix allowed and blocked network sources
Limit traffic to a predefined rate (blocking the excess)
Limit traffic to specific protocols, and specific port ranges on the device
468
User's Manual
20.4.1
Internal Firewal
The access list consists of a table with up to 25 ordered lines. For each packet
received on the network interface, the table is scanned from the top until a matching
rule is found (or the table end is reached). This rule can either block the packet or
allow it; however it is important to note that subsequent rules will not be scanned. If
the table end is reached without a match, the packet is accepted.
Each rule is made up of the following fields:
Table 20-6: Internal Firewall Fields

Parameter
Description
Source IP
IP address (or DNS name) of source network, or

a specific host
[AccessList_Source_IP]
Mask
[AccessList_Net_Mask]
IP network mask. 255.255.255.255 for a single

host, or the appropriate value for the source IP
addresses
The IP address of the sender of the incoming
packet is bitwise ANDed with this mask and then
compared to the field Source IP.
Local Port Range

[AccessList_Start_Port]
[AccessList_End_Port]
The destination UDP/TCP ports (on this device)

to which packets are sent.
The valid range is 0 to 65535.
Note: When the protocol type is not TCP or UDP,
the entire range must be provided.
Protocol
[AccessList_Protocol]
The protocol type (e.g., UDP, TCP, ICMP, ESP or

Any), or the IANA protocol number (in the range
of 0 (Any) to 255).
Note: The protocol field also accepts the
abbreviated strings 'SIP', 'MGCP', 'MEGACO',
'HTTP'. Specifying these strings imply selection of
the TCP or UDP protocols, and the appropriate
port numbers as defined on the device.
Packet Size
[AccessList_Packet_Size]
Maximum allowed packet size.

The valid range is 0 to 65535.
Note: When filtering fragmented IP packets, the
Packet Size field relates to the overall
(reassembled) packet size, not to the size of each
fragment.
Byte Rate
[AccessList_Byte_Rate]
Expected traffic rate (bytes per second).
Burst Bytes
[AccessList_Byte_Burst]
Tolerance of traffic rate limit (number of bytes)
Action Upon Match

[AccessList_Allow_Type]
Action upon match (allow or block)
Match Count
[ACCESSLIST_MatchCount]
A read-only field that provides the number of

packets accepted / rejected by a specific rule.
Version 4.8
469
January 2006
Mediant 3000
The following is an example of an access list definition via ini file:

[ ACCESSLIST ]
FORMAT ACCESSLIST_Index = ACCESSLIST_Source_IP,
ACCESSLIST_Net_Mask, ACCESSLIST_Start_Port, ACCESSLIST_End_Port,
ACCESSLIST_Protocol, ACCESSLIST_Packet_Size, ACCESSLIST_Byte_Rate,
ACCESSLIST_Byte_Burst, ACCESSLIST_Allow_Type;
ACCESSLIST 10 =
0, 0, allow ;
ACCESSLIST 15 =
50000, block ;
ACCESSLIST 20 =
block ;
ACCESSLIST 22 =
block ;
[ \ACCESSLIST ]
mgmt.customer.com, 255.255.255.255, 0, 80, tcp, 0,

192.0.0.0, 255.0.0.0, 0, 65535, any, 0, 40000,
10.31.4.0, 255.255.255.0, 4000, 9000, any, 0, 0, 0,
10.4.0.0, 255.255.0.0, 4000, 9000, any, 0, 0, 0,
The following is an explanation of the example access list:
Rule #10: traffic from the host 'mgmt.customer.com' destined to TCP ports 0 to
80, is always allowed.
Rule #15: traffic from the 192.xxx.yyy.zzz subnet, is limited to a rate of 40 Kbytes
per second (with an allowed burst of 50 Kbytes). Note that the rate is specified in
bytes, not bits, per second; a rate of 40000 bytes per second, nominally
corresponds to 320kbps.
Rule #20: traffic from the subnet 10.31.4.xxx destined to ports 4000-9000 is
always blocked, regardless of protocol.
Rule #22: traffic from the subnet 10.4.xxx.yyy destined to ports 4000-9000 is
always blocked, regardless of protocol.
All other traffic are allowed.
More complex rules may be defined, relying on the "single-match" process described
below:
the following is an advanced example of an access list definition via ini file:
[ ACCESSLIST ]
FORMAT ACCESSLIST_Index = ACCESSLIST_Source_IP,
ACCESSLIST_Net_Mask, ACCESSLIST_Start_Port, ACCESSLIST_End_Port,
ACCESSLIST_Protocol, ACCESSLIST_Packet_Size, ACCESSLIST_Byte_Rate,
ACCESSLIST_Byte_Burst, ACCESSLIST_Allow_Type;
ACCESSLIST 10 = 10.0.0.0, 255.0.0.0, 0, 65535, any, 0, 40000,
50000, allow ;
ACCESSLIST 15 = 10.31.4.0, 255.255.255.0, 4000, 9000, any, 0, 0, 0,
allow ;
ACCESSLIST 20 = 0.0.0.0, 0.0.0.0, 0, 65535, any, 0, 0, 0, block;
[ \ACCESSLIST ]
The following is an explanation of the example access list:
This access list consists of three rules:
User's Manual
Rule #10: traffic from the subnet 10.xxx.yyy.zzz is allowed if the traffic rate does
not exceed 40KB/s.
Rule #15: If a packet didn't match rule #10, that is, the excess traffic is over
40KB/s, and coming from the subnet 10.31.4.xxx to ports 4000-9000, then it is
470
User's Manual

allowed.
Rule #20: all other traffic (which didn't match the previous rules), is blocked.
The internal firewall can also be configured via the Embedded Web Server (refer' to
the Firewall S' on page 248ettings). Note that when creating access rules via the
Embedded Web Server, it is necessary to click the Activate button after reviewing the
rule's fields.
20.5
Network Port Usage

The following table lists the default TCP/UDP network port numbers used by the
Mediant 3000. Where relevant, the table lists the ini file parameters that control the
port usage and provide source IP address filtering capabilities.
Table 20-7: Default TCP/UDP Network Port Numbers

Port number
Peer port
Application
Notes
Debugging interface
Always ignored
EtherDiscover
Open only on unconfigured devices
23
Telnet
Disabled by default
(TELNETSERVERENABLE).
Configurable (TELNETSERVERPORT),
access controlled by WebAccessList
68
67
DHCP
Active only if DHCPENABLE=1
80
Web server (HTTP)
Configurable (HTTPPORT), may be

disabled (DISABLEWEBTASK or
HTTPSONLY). Access controlled by
WEBACCESSLIST
161
SNMP GET/SET
Configurable (SNMPPORT), may be

disabled (DISABLESNMP). Access
controlled by SNMPTRUSTEDMGR
443
Web server (HTTPS)
Configurable (HTTPSPORT), may be

disabled (DISABLEWEBTASK). Access
controlled by WEBACCESSLIST
500
IPSec IKE
May be disabled (ENABLEIPSEC)
2422
2422
TPM LinkLayer
Used for internal synchronization

between the two TPMs on a board
(Applicable to 1610 boards only)
2423-2424
2423 and
up
TPNCP
Proprietary control protocol. Access

controlled by ENABLETPNCPSECURITY
and AUTHORIZEDTPNCPSERVERS
2427
2427
MGCP / Megaco
Configurable (GATEWAYMGCPPORT),
Access controlled by
PROVISIONEDCALLAGENTS and
MEGACOCHECKLEGALITYOFMGC
4000, 4010 and up
RTP traffic
Base port number configurable
Version 4.8
471
January 2006
Mediant 3000
Table 20-7: Default TCP/UDP Network Port Numbers

Port number
Peer port
Application
Notes
(BASEUDPPORT), fixed increments of
10. The number of ports used depends
on the channel capacity of the device.
4001, 4011 and up
RTCP traffic
Always adjacent to the RTP port number
4002, 4012 and up
T.38 traffic
Always adjacent to the RTCP port

number
32767
SCTP
If SCTP/IUA is available on the device
(random) > 32767
514
Syslog
May be disabled (ENABLESYSLOG).
(random) > 32767
Syslog ICMP
May be disabled (ENABLESYSLOG).
(random) > 32767
ARP listener
(random) > 32767
162
SNMP Traps
(random) > 32767
DNS client
20.6
Media Security
20.6.1
Packet Cable Security
May be disabled (DISABLESNMP)
The Mediant 3000 supports media encryption via TGCP (PacketCable extensions to
MGCP protocol) and via the proprietary VoPLib API. With media security, IP voice
traffic for some or all channels is encrypted using predefined session keys. No key
negotiation is performed for media security. Instead, the Mediant 3000 assumes
higher-level protocols handle key management.
Encryption specifications:
AES (Rijndael) cipher algorithm, in CBC mode
Key strength - 128 bit
Encryption key supplied by TGCP or manually via VoPLib API
The VoPLib API may be used over the network (TPNCP protocol). Media security over
TPNCP should be used with caution, since the TPNCP connection itself is not
encrypted, and sniffing techniques may be used to obtain the session key. The same
is applicable for TGCP connections. Physical security is required to make sure the
softswitch connection is protected from unauthorized sniffing.
Note : Using media security reduces the channel capacity of the device.
For further information regarding the VoPLib API, consult the VoPLib API Reference
User's Manual
472
User's Manual
20.6.2
Secured RTP
The Mediant 3000 supports Secured RTP (SRTP) as defined in RFC 3711. SRTP
provides confidentiality, message authentication, and replay protection to the RTP &
RTCP traffic.
Key negotiation is not part of SRTP. Instead, the Mediant 3000 assumes higher-level
protocols handle key management.
Specifications:
Encryption - AES 128 in Counter Mode
Authentication - HMAC-SHA1
Support of Key Derivation
Key management is provided via VoPLib API, MGCP & MECAGO
The VoPLib API may be used over the network (TPNCP protocol). Media security over
TPNCP should be used with caution, since the TPNCP connection itself is not
encrypted, and sniffing techniques may be used to obtain the session key. The same
is applicable for TGCP connections. Physical security is required to make sure the
softswitch connection is protected from unauthorized sniffing.
Note : Using media security reduces the channel capacity of the device.
For further information regarding the VoPLib API, consult the VoPLib API Reference
20.7
Recommended Practices
To improve network security, the following guidelines are recommended when
configuring the Mediant 3000:
Version 4.8
Set the management password to a unique, hard-to-guess string. Do not use the
same password for several devices, as a compromise of one may lead to the
compromise of others. Keep this password safe at all times, and change it
frequently.
If possible, use a RADIUS server for authentication. RADIUS allows you to set
different passwords for different users of the Mediant 3000, with centralized
management of the password database. Both Web and Telnet interfaces support
RADIUS authentication.
Use IPSec to secure traffic to all management and control hosts. Since IPSec
encrypts all traffic, hackers cannot capture sensitive data transmitted on the
network, and malicious intrusions are severely limited.
Use HTTPS when accessing the Web interface. Set HTTPSONLY=1 to allow only
HTTPS traffic (and block port 80). If you don't need the Web interface, disable the
Web server.
If you use Telnet, do not use the default port (23). Use SSL mode to protect
Telnet traffic from network sniffing.
If you use SNMP, do not leave the community strings at their default values, as
473
January 2006
Mediant 3000
they can be easily discovered by hackers. See the SNMP configuration chapter
for further details.
20.8
Use a firewall to protect your VoIP network from external attacks. Robustness of
the network may be compromised if the network is exposed to "denial of service"
(DoS) attacks; such attacks are mitigated by stateful firewalls. Do not allow
unauthorized traffic to reach the Mediant 3000.
Legal Notice
By default, the Mediant 3000 supports export-grade (40-bit and 56-bit) encryption, due
to U.S. government restrictions on the export of security technologies. To enable 128bit and 256-bit encryption on your device, contact your AudioCodes representative.
This product includes software developed by the OpenSSL Project for use in the
OpenSSL Toolkit. (http://www.openssl.org/)
This product includes
('eay@cryptsoft.com).
User's Manual
cryptographic
474
software
written
by
Eric
Young'
User's Manual
21
21. Appendix - SS7 Configuration Guide
Appendix - SS7 Configuration Guide

Several SS7 network elements are available. This section provides a brief description
of each network element, and corresponding configuration description.
Part of the various network elements described below includes the use of SigTran
(M2UA, M3UA), as implemented in products such as Mediant 3000.
Note: please refer to the description of SS7 configuration parameters in 'Table of
Parameter Value Constructs' on page 94 and in the Appendix, 'Table Parameters' on
page 387.
21.1
SS7 Network Elements

The SS7 network elements include 4 basic configurations:
21.1.1
SS7 M2UA - SG Side
SS7 M2UA Media Gateway Controller Side
SS7 MTP3 Node
SS7 MTP2 Tunneling
SS7 M2UA - SG Side

For the SS7 M2UA - SG side network element, the MTP2 link from the SS7 network
side is sent via SCTP (IP) to Media-Gateway side.
Figure 21-1: SS7 M2UA - SG Side
Soft-Switch
\
Layer 4 App.
M3UA
Layer
4 App.
M3UA
MTP3
MTP2
MTP1
Version 4.8
MTP2
MTP1
M2UA
SG
IP
IP
MTP3
M2UA MGC
IP
IP
SCTP
SCTP
475
January 2006
Mediant 3000
21.1.2

For the SS7 M2UA Media Gateway Controller side network element, the M2UA
Media Gateway Controller link is from the IP side. MTP3 is supported in the boards
software. The MTP3 payload is sent via M3UA to the Soft-Switch. (MTP3 can also
route MSUs to other SS7 network elements via other links).
Figure 21-2: SS7 M2UA - MGC Side
Soft-Switch
\
Layer 4 App.
M3UA
Layer
4 App.
M3UA
MTP3
MTP2
MTP2
MTP1
21.1.3
MTP1
M2UA
SG
IP
IP
MTP3
M2UA MGC
IP
IP
SCTP
SCTP
SS7 MTP3 Node

The SS7 MTP3 Node is a classic MTP3 over MTP2 configuration. Links are incoming
from the SS7 Network. MTP3 payload is sent via M3UA to the Soft-Switch or routed to
other SS7 network elements according to the MSU headers.
Figure 21-3: SS7 MTP3 Node
Soft-Switch
\
Layer 4 App.
M3UA
M3UA
IP
IP
MTP3
MTP2
MTP1
SS7 Links
User's Manual
476
User's Manual
21.1.4
SS7 MTP2 Tunneling

For the SS7 MTP2 Tunneling configuration, the MTP2 SS7 link payload is sent across
long distances (over the IP network). Both of its termination ends have SS7 MTP2
interfaces, which are unaware of the MTP2 Tunneling between them.
MTP2 Tunneling is a proprietary solution, based on SS7 and SigTran standards.
Figure 21-4: SS7 MTP2 Tunneling
Soft-Switch
\
Layer 4 App.
SS7 Tunnel
Remote Side
Layer
4 App.
MTP3
AudioCodes
M2TN
MTP3
MTP2
MTP2
MTP1
21.1.5
SS7 Tunnel
Central Side
MTP1
M2UA
SG
IP
IP
SCTP
M2UA
MGC
MTP2
MTP1
MTP2
MTP1
Configuration Extensions:
In addition to the basic SS7 configurations described above, the extensions below
provide more options:
21.1.6
1.
2 SS7 Nodes (SP/STP) can be configured per TPM
2.
MTP3 supports mixed SS7 link types, i.e. one MTP3 signaling node can have few
MTP2 links and a number of M2UA links
3.
Nodes can be configured as SP or STP
4.
Supported SS7 variants: ITU-T, ANSI, CHINA
5.
SS7 signaling links can be configured on any available timeslot of any trunk, so
that several SS7 signaling links can be configured on one E1/T1
6.
F-links are supported: any mixture of voice and signaling links can be configured
on any trunk (providing that the trunk type supports SS7 signaling links - refer to
the examples provided below).
Other dependencies in ini File:

Trunk Protocol Types
Trunks that carry SS7 Link(s) must be configured with protocol type:
T1_TRANSPARENT=4, E1_TRANSPARENT31=5 or E1_TRANSPARENT30=6
Version 4.8
477
January 2006
Mediant 3000
21.2
Examples of SS7 ini Files

This section provides examples of ini files for each of the SS7 network elements
described previously. Each example can be modified to fit the users field configuration
is accompanied by loading instructions for a testing/Lab mini-network environment.
21.2.1
SS7 M2UA - SG Side ini File Example

For the SS7 M2UA - SG Side ini file example, take into account the following notes:
There are 4 SS7 links of type: MTP2->M2UA SG.
There is 1 interface group (only 1 remote Media Gateway Controller).
There are 4 interface IDs defined: 1 per link.
This file is intended for ITU link variant (E1 trunks).
To load the SS7 M2UA - SG Side ini file example, take these 2
steps:
1.
This ini file is to be loaded on an MTP2 SG board. An MTP2 Media Gateway

Controller board should be connected (over IP) to the MTP2 SG board.
2.
Change the value of the SyslogServerIP parameter accordingly.
The following is an example of SS7 M2UA - SG Side ini File

; 1=aLaw 3=ulaw
PCMLawSelect=
1
; EXT_BUS=5
TDMBusType=
H110=4
2
QSLAC=3
FRAMERS=2
SC_BUS=1
MVIP_BUS=0
; 0=2048kbps, 2=4096kbps, 3=8192kbps

TDMBusSpeed=
3
;1 - internal, 3 - mvip, 4 - Network, 8 - h110a, 9 - h110b, 10 Netref
TDMBUSCLOCKSOURCE= 1
;e1_euro_isdn=1 t1_isdn=2 ;e1_cas_r2=8 (8 for fcd); e1_trans_31=5
ProtocolType = 5
TraceLevel
= 0
; acCLOCK_MASTER_ON =1
CLOCKMASTER= 1
;acUSER_TERMINATION_SIDE = 0
TerminationSide = 1
;acEXTENDED_SUPER_FRAME=0
FramingMethod = 0
;acB8ZS = 0
LineCode = 0
User's Manual
2 for E1_CAS - FCD
478
User's Manual
Q931RELAYMODE = 0
; 0=Internal Clock, 1=rx signal derived clk
PHYCLKSOURCE=0
[syslog]
SYSLOGSERVERIP = 168.100.0.1
ENABLESYSLOG = 1
WATCHDOGSTATUS = 0
[ SS7_LINK_TABLE ]
FORMAT SS7_LINK_INDEX = SS7_LINK_NAME, SS7_LINK_TRACE_LEVEL,
SS7_LINK_ADMINISTRATIVE_STATE,SS7_LINK_L2_TYPE, SS7_LINK_L3_TYPE,
SS7_LINK_TRUNK_NUMBER,SS7_LINK_TIMESLOT_NUMBER,SS7_LINK_M2UA_IF_ID,
SS 7_LINK_GROUP_ID;
SS7_LINK_TABLE
SS7_LINK_TABLE
SS7_LINK_TABLE
SS7_LINK_TABLE
0
1
2
3
=
=
=
=
new_link_0,
new_link_1,
new_link_2,
new_link_3,
0,
0,
0,
0,
2,
2,
2,
2,
1,
1,
1,
1,
1,
1,
1,
1,
1, 15, 50, 4;
2, 12, 12, 4;
4, 7, 18, 4;
5, 3, 1, 4;
[\SS7_LINK_TABLE]
[ SS7_SIG_IF_GROUP_TABLE ]
FORMAT SS7_SIG_IF_GR_INDEX = SS7_IF_GR_ID,SS7_SIG_SG_MGC,
SS7_SIG_LAYER, SS7_SIG_TRAF_MODE, SS7_SIG_T_REC, SS7_SIG_T_ACK,
SS7_SIG_T_HB, SS7_SIG_MIN_ASP, SS7_SIG_BEHAVIOUR,
SS7_LOCAL_SCTP_PORT, SS7_SIG_NETWORK;
SS7_SIG_IF_GROUP_TABLE 4 = 4,83, 2, 1, 2000, 2000, 30000, 1, 0,
2904, 1;
[ \SS7_SIG_IF_GROUP_TABLE ]
SS7_SIG_INT_ID_TABLE 8 = 12, AMSTERDAM, 4, 2, 1, 0;
SS7_SIG_INT_ID_TABLE 9 = 18, ROTERDAM , 4, 2, 2, 0;
SS7_SIG_INT_ID_TABLE 10 = 1, GAUDA
, 4, 2, 3, 0;
21.2.2
SS7 M2UA - Media Gateway Controller Side ini File Example

For the SS7 M2UA - Media Gateway Controller Side ini file example, take into
account the following notes:
Version 4.8
This ini file acts as the M2UA Media Gateway Controller (toward the remote
MTP2 side) and M3UA SG (toward the layer 4 application, e.g., Soft-Switch).
There are 4 SS7 links of type: MTP2 Media Gateway Controller->MTP3.
There is 1 SN (Signaling Node). Modify its point-code according to your network.
There is 1 LinkSet with 4 links.
There is 1 RouteSet.
The DPC of the RouteSet and LinkSet is the point-code of the remote end (to
which the MTP2 link on the MTP2 SG side is connected). Modify it on both
LinkSet and RouteSet tables.
479
January 2006
Mediant 3000
There are 2 interface groups: 1 interface group is used for the M2UA SG <=>
M2UA Media Gateway Controller connection, and the other one is used for the
M3UA SG <=> M3UA Media Gateway Controller connection.
There are 4 interface IDs defined: 1 per link (M2UA Media Gateway Controller
side) and one more interface Id for M3UA SG. The connection between the
interface ID and the Interface group is determined by the
SS7_SIG_IF_ID_OWNER_GROUP parameter.
To load the SS7 M2UA - Media Gateway Controller Side ini file
example, take these 4 steps:
1.
Load this ini file on an MTP2 Media Gateway Controller board. An MTP2 SG
board should be connected (over IP) to the MTP2Media Gateway Controller
board.
2.
3.
Change the SS7_DEST_IP parameter according to the actual IP address of the

M2UA SG board.
4.
Change the SS7_SIG_M3UA_SPC parameter of line 0 (M3UA related interface

ID line) according to the local SN point code.
The following is an example of SS7 M2UA - Media Gateway Controller Side ini File
; 1=aLaw 3=ulaw
PCMLawSelect=
1
; EXT_BUS=5
TDMBusType=
H110=4
2
QSLAC=3
FRAMERS=2
SC_BUS=1
MVIP_BUS=0
; 0=2048kbps, 2=4096kbps, 3=8192kbps

TDMBusSpeed=
3
ProtocolType = 5
CLOCKMASTER= 1
TerminationSide = 1
FramingMethod = 0
;acB8ZS = 0
LineCode = 0
2 for E1_CAS - FCD
Q931RELAYMODE = 0
[SS7]
SS7_MTP2_PARAM_TIMER_T7_0=2000
User's Manual
480
User's Manual
; 0=OC3, 1=UTOPIA (NO PHY)

ATMPHYTYPE=1
PHYCLKSOURCE=0
; 0=No loopback, 1=Internal loopback, 2=line loopback
ATMLOOPBACK=1
[syslog]
ENABLESYSLOG = 1
;FORCEEXCEPTIONDUMP = 1
WATCHDOGSTATUS = 0
; ****************************************
; SS7 TIMERS - ITU
; ****************************************
[SS7_SN_TIMERS_TABLE]
FORMAT SS7_SNTIMERS_INDEX = SS7_SNTIMERS_NAME, SS7_SNTIMERS_T6,
SS7_SNTIMERS_T8, SS7_SNTIMERS_T10, SS7_SNTIMERS_T11,
SS7_SNTIMERS_T15, SS7_SNTIMERS_T16, SS7_SNTIMERS_T18_ITU,
SS7_SNTIMERS_T19_ITU, SS7_SNTIMERS_T20_ITU, SS7_SNTIMERS_T21_ITU,
SS7_SNTIMERS_T24_ITU;
SS7_SN_TIMERS_TABLE 0 = TENERIFF_0, 800, 1000, 30000, 30000, 2000,
1400, 5000, 4000, 15000, 10000, 500;
[\SS7_SN_TIMERS_TABLE]
[SS7_LINKSET_TIMERS_TABLE]
FORMAT SS7_LKSETTIMERS_INDEX = SS7_LKSETTIMERS_NAME,
SS7_LKSETTIMERS_T1SLT, SS7_LKSETTIMERS_T2SLT, SS7_LKSETTIMERS_T1,
SS7_LKSETTIMERS_T2, SS7_LKSETTIMERS_T3, SS7_LKSETTIMERS_T4,
SS7_LKSETTIMERS_T22_ITU, SS7_LKSETTIMERS_T23_ITU;
SS7_LINKSET_TIMERS_TABLE 0 = DELHI_0, 8000, 30000, 800, 1400, 800,
800, 800, 1000, 1500, 800, 2000, 1500, 180000, 180000;
[\SS7_LINKSET_TIMERS_TABLE]
; ****************************************
; SS7 TIMERS - ANSI
; ****************************************
SS7_SNTIMERS_T15, SS7_SNTIMERS_T16, SS7_SNTIMERS_T22_ANSI,
SS7_SNTIMERS_T23_ANSI, SS7_SNTIMERS_T24_ANSI,
SS7_SNTIMERS_T30_ANSI;
SS7_SN_TIMERS_TABLE 1 = BABILON_0, 800, 1000, 30000, 30000, 2000,
1400, 180000, 180000, 5000, 30000, 12000, 3000, 60000, 30000;
SS7_LKSETTIMERS_T14, SS7_LKSETTIMERS_T17, SS7_LKSETTIMERS_T20_ANSI,
SS7_LKSETTIMERS_T21_ANSI;
SS7_LINKSET_TIMERS_TABLE 1 = HANOI_0, 8000, 30000, 800, 1400, 800,
800, 800, 1000, 1500, 2000, 1500, 90000, 90000;
Version 4.8
481
January 2006
Mediant 3000
[SS7_SN_TABLE]
FORMAT SS7_SN_INDEX = SS7_SN_NAME, SS7_SN_TRACE_LEVEL,
SS7_SN_ADMINISTRATIVE_STATE, SS7_SN_VARIANT, SS7_SN_NI,
SS7_SN_SP_STP, SS7_SN_OPC, SS7_SN_ROUTESET_CONGESTION_WINSIZE,
SS7_SN_TIMERS_INDEX, SS7_SN_ISUP_APP, SS7_SN_SCCP_APP,
SS7_SN_BISUP_APP, SS7_SN_ALCAP_APP;
SS7_SN_TABLE 0 = SN_0, 0, 2, 1, 0, 0, 11, 8, 0, 4, 4, 4, 4;
[\SS7_SN_TABLE]
[ SS7_LINK_TABLE ]
SS7_LINK_ADMINISTRATIVE_STATE,SS7_LINK_L2_TYPE,
SS7_LINK_L3_TYPE,SS7_LINK_GROUP_ID, SS7_LINK_M2UA_IF_ID;
SS7_LINK_TABLE 0 = link_0_SP_A, 0, 2, 2, 2, 4, 50;
SS7_LINK_TABLE 1 = link_1_SP_B, 0, 2, 2, 2, 4, 12;
SS7_LINK_TABLE 2 = link_2_SP_C, 0, 2, 2, 2, 4, 18;
SS7_LINK_TABLE 3 = link_3_SP_D, 0, 2, 2, 2, 4, 1;
[\SS7_LINK_TABLE]
[ SS7_LINKSET_TABLE ]
FORMAT SS7_LINKSET_SN_INDEX, SS7_LINKSET_LINKSET_INDEX =
SS7_LINKSET_NAME, SS7_LINKSET_ADMINISTRATIVE_STATE,
SS7_LINKSET_DPC, SS7_LINKSET_TIMERS_INDEX;
SS7_LINKSET_TABLE 0, 0 = lkset0_sp_A, 2, 10, 0;
[ \SS7_LINKSET_TABLE ]
[ SS7_LINKSETLINK_TABLE ]
FORMAT SS7_LINKSETLINK_SN_INDEX, SS7_LINKSETLINK_LINKSET_INDEX,
SS7_LINKSETLINK_INNER_LINK_INDEX = SS7_LINKSETLINK_LINK_NUMBER,
SS7_LINKSETLINK_LINK_SLC;
SS7_LINKSETLINK_TABLE 0, 0, 0 = 0, 0;
[ \SS7_LINKSETLINK_TABLE ]
[ SS7_ROUTESET_TABLE ]
FORMAT SS7_ROUTESET_SN_INDEX, SS7_ROUTESET_INDEX =
SS7_ROUTESET_NAME, SS7_ROUTESET_ADMINISTRATIVE_STATE,
SS7_ROUTESET_DPC;
SS7_ROUTESET_TABLE 0, 0 = RTESET0_SP_A, 2, 10;
[ \SS7_ROUTESET_TABLE ]
[ SS7_ROUTESETROUTE_TABLE ]
FORMAT SS7_ROUTESETROUTE_SN_INDEX,
SS7_ROUTESETROUTE_ROUTESET_INDEX,
SS7_ROUTESETROUTE_INNER_ROUTE_INDEX =
SS7_ROUTESETROUTE_LINKSET_NUMBER, SS7_ROUTESETROUTE_PRIORITY;
SS7_ROUTESETROUTE_TABLE 0, 0, 0 = 0, 0;
[ \SS7_ROUTESETROUTE_TABLE ]
;
; M3UA SG SIDE DEFINITION:
;
SS7_SIG_IF_GROUP_TABLE 2 = 2, 83, 3, 1, 2000, 2000, 30000, 1, 0,
2905, 1;
User's Manual
482
User's Manual
SS7_LOCAL_SCTP_PORT, SS7_SIG_NETWORK, SS7_DEST_SCTP_PORT,
SS7_DEST_IP, SS7_MGC_MX_IN_STREAM, SS7_MGC_NUM_OUT_STREAM;
;
; M2UA MGC SIDE DEFINITION:
;
2904, 1,2904,168.100.0.2,3,3;
SS7_SIG_INT_ID_TABLE 1 = 50, AMSTERDAM1, 4, 2, 0, 0;
SS7_SIG_INT_ID_TABLE 2 = 12, GAUDA,
4, 2, 1, 0;
SS7_SIG_INT_ID_TABLE 3 = 18, PRAGUE,
4, 2, 2, 0;
SS7_SIG_INT_ID_TABLE 4 = 1, PARIS ,
4, 2, 3, 0;
21.2.3
SS7 MTP3 Node ini File Example

For the SS7 MTP3 Node ini file example, take into account the following notes:
This ini file defines 2 MTP3 SNs (signaling nodes). These nodes are connected
to each other in an external loop, using E1 trunks.
There are 4 SS7 links of type: MTP2->MTP3.
There is 1 LinkSet per SN with 2 links.
There is 1 RouteSet per SN with 1 LinkSet.
There is 1 interface group - Both SNs are using it.
There are 2 interface Ids defined: 1 per SN.
To load the SS7 MTP3 Node ini file example, take these 2 steps:
1.
Load this ini file on an MTP3+M3UA board. A layer 4 application (such as SoftSwitch) should be connected (over IP) to the board.
2.
The following is an example of SS7 MTP3 Node ini File.

;DSPVERSIONTEMPLATENUMBER = 1
; 1=aLaw 3=ulaw
PCMLawSelect=
1
; EXT_BUS=5
TDMBusType=
Version 4.8
H110=4
2
QSLAC=3
483
FRAMERS=2
SC_BUS=1
MVIP_BUS=0
January 2006
Mediant 3000
; 0=2048kbps, 2=4096kbps, 3=8192kbps

TDMBusSpeed=
3
;BaseUDPPort=4000
[Bit Configuration]
;enablediagnostic=1
ProtocolType = 5
TraceLevel
= 0
CLOCKMASTER= 1
TerminationSide = 1
FramingMethod = 0
;acB8ZS = 0
2 for E1_CAS - FCD
LineCode = 0
Q931RELAYMODE = 0
; for ss7 configuration . 77 is for SS7 debug with TSL and 0 is
noth ing
; 7 is for M2ua DRAFT 7 ; 101 for UAL netbricks
PSTNRESERVED3= 101
;[T3 Configuration]
;0 = M23 framing method 1 = C_BIT Parity framing
;DS3FRAMINGMETHOD = 1
;0 = External (Line) 1 = Internal from board
;DS3CLOCKSOURCE = 1
;0 - Line in bigger then 225 ft 1 = Line in shorter then 225 ft
;DS3LINEBUILTOUT = 1
[MEGACO]
;DSPVERSIONTEMPLATENUMBER = 1
;MGCPDEFAULTCODER = 57
;MGCONTROLPROTOCOLTYPE = 0
;DIGITMAPNAME ='DMAP69'
;DIGITMAPPING = 1|11|[5-7]X|9XxXxxxX|fX|exx|91xXx|9011x.
[megaco conference support]
MGControlprotocoltype =2
; 0=OC3, 1=UTOPIA (NO PHY)
ATMPHYTYPE=1
PHYCLKSOURCE=0
; 0=No loopback, 1=Internal loopback, 2=line loopback
ATMLOOPBACK=1
[syslog]
User's Manual
484
User's Manual
ENABLESYSLOG = 1
;FORCEEXCEPTIONDUMP = 1
WATCHDOGSTATUS = 0
; ****************************************
; SS7 TIMERS - ITU
; ****************************************
SS7_SNTIMERS_T15, SS7_SNTIMERS_T16, SS7_SNTIMERS_T18_ITU,
SS7_SNTIMERS_T19_ITU, SS7_SNTIMERS_T20_ITU, SS7_SNTIMERS_T21_ITU,
SS7_SNTIMERS_T24_ITU;
SS7_SN_TIMERS_TABLE 0 = TENERIFF_0, 800, 1000, 30000, 30000, 2000,
1400, 5000, 4000, 15000, 10000, 500;
SS7_LKSETTIMERS_T22_ITU, SS7_LKSETTIMERS_T23_ITU;
SS7_LINKSET_TIMERS_TABLE 0 = DELHI_0, 8000, 30000, 800, 1400, 800,
800, 800, 1000, 1500, 800, 2000, 1500, 180000, 180000;
; ****************************************
; SS7 TIMERS - ANSI
; ****************************************
SS7_SNTIMERS_T15, SS7_SNTIMERS_T16, SS7_SNTIMERS_T22_ANSI,
SS7_SNTIMERS_T30_ANSI;
SS7_SN_TIMERS_TABLE 1 = BABILON_0, 800, 1000, 30000, 30000, 2000,
1400, 180000, 180000, 5000, 30000, 12000, 3000, 60000, 30000;
SS7_LKSETTIMERS_T14, SS7_LKSETTIMERS_T17, SS7_LKSETTIMERS_T20_ANSI,
SS7_LKSETTIMERS_T21_ANSI;
SS7_LINKSET_TIMERS_TABLE 1 = HANOI_0, 8000, 30000, 800, 1400, 800,
800, 800, 1000, 1500, 2000, 1500, 90000, 90000;
Version 4.8
485
January 2006
Mediant 3000
[SS7_SN_TABLE]
FORMAT SS7_SN_INDEX = SS7_SN_NAME, SS7_SN_TRACE_LEVEL,
SS7_SN_ADMINISTRATIVE_STATE, SS7_SN_VARIANT, SS7_SN_NI,
SS7_SN_SP_STP, SS7_SN_OPC, SS7_SN_ROUTESET_CONGESTION_WINSIZE,
SS7_SN_TIMERS_INDEX, SS7_SN_ISUP_APP, SS7_SN_SCCP_APP,
SS7_SN_BISUP_APP, SS7_SN_ALCAP_APP;
SS7_SN_TABLE 0 = SN_0, 0, 2, 1, 0, 0, 11, 8, 0, 4, 4, 4, 54;
SS7_SN_TABLE 1 = SN_1, 0, 2, 1, 0, 0,
[\SS7_SN_TABLE]
4, 8, 0, 4, 4, 4, 4;
[ SS7_LINK_TABLE ]
SS7_LINK_ADMINISTRATIVE_STATE, SS7_LINK_L2_TYPE, SS7_LINK_L3_TYPE,
SS7_LINK_TRUNK_NUMBER, SS7_LINK_TIMESLOT_NUMBER,
SS7_LINK_LAYER2_VARIANT, SS7_LINK_MTP2_ATTRIBUTES,
SS7_CONGESTION_LOW_MARK, SS7_CONGESTION_HIGH_MARK;
SS7_LINK_TABLE
SS7_LINK_TABLE
SS7_LINK_TABLE
SS7_LINK_TABLE
0
1
2
3
=
=
=
=
link_0_SP_A,
link_1_SP_B,
link_2_SP_A,
link_3_SP_B,
0,
0,
0,
0,
2,
2,
2,
2,
1,
1,
1,
1,
2,
2,
2,
2,
0,
1,
0,
1,
16,
16,
17,
17,
1,
1,
1,
1,
0,
0,
0,
0,
5,
5,
5,
5,
20;
20;
20;
20;
[\SS7_LINK_TABLE]
[ SS7_LINKSET_TABLE ]
FORMAT SS7_LINKSET_SN_INDEX, SS7_LINKSET_LINKSET_INDEX =
SS7_LINKSET_NAME, SS7_LINKSET_ADMINISTRATIVE_STATE,
SS7_LINKSET_DPC, SS7_LINKSET_TIMERS_INDEX;
;; for SN 0:
SS7_LINKSET_TABLE 0, 0 = lkset0_sp_A, 2, 4, 0;
;SS7_LINKSET_TABLE 0, 6 = lkset1, 2, 444, 0;
;; for SN 1:
SS7_LINKSET_TABLE 1, 0 = lkset0_sp1, 2, 11, 0;
[ \SS7_LINKSET_TABLE ]
[ SS7_LINKSETLINK_TABLE ]
FORMAT SS7_LINKSETLINK_SN_INDEX, SS7_LINKSETLINK_LINKSET_INDEX,
SS7_LINKSETLINK_INNER_LINK_INDEX = SS7_LINKSETLINK_LINK_NUMBER,
SS7_LINKSETLINK_LINK_SLC;
;; for SN 0:
;; for SN 1:
[ \SS7_LINKSETLINK_TABLE ]
[ SS7_ROUTESET_TABLE ]
FORMAT SS7_ROUTESET_SN_INDEX, SS7_ROUTESET_INDEX =
SS7_ROUTESET_NAME, SS7_ROUTESET_ADMINISTRATIVE_STATE,
SS7_ROUTESET_DPC;
; for SN 0:
SS7_ROUTESET_TABLE 0, 0 = RTESET0_SP_A, 2, 4;
; for SN 1:
User's Manual
486
User's Manual
SS7_ROUTESET_TABLE 1, 0 = RTESET0_SN1, 2, 11;

[ \SS7_ROUTESET_TABLE ]
[ SS7_ROUTESETROUTE_TABLE ]
FORMAT SS7_ROUTESETROUTE_SN_INDEX,
SS7_ROUTESETROUTE_ROUTESET_INDEX,
SS7_ROUTESETROUTE_INNER_ROUTE_INDEX =
SS7_ROUTESETROUTE_LINKSET_NUMBER, SS7_ROUTESETROUTE_PRIORITY;
; for SN 0:
; for SN 1:
[ \SS7_ROUTESETROUTE_TABLE ]
2905, 1;
SS7_SIG_M3UA_SPC;
SS7_SIG_INT_ID_TABLE 0 = 100, BELFAST12, 0, 3, 11;
SS7_SIG_INT_ID_TABLE 1 = 101, AMSTERDAM1, 0, 3, 4;
21.2.4
SS7 MTP2 Tunneling ini File Example

'For the SS7 MTP2 Tunneling ini file example, take into account the following notes:
This ini file acts as MTP2 tunneling central side (M2UA Media Gateway
Controller links).
There are 8 SS7 links - 4 links of type: MTP2 Media Gateway Controller, and 4
links of type MTP2. Each pair of links (1 MTP2 Media Gateway Controller and 1
MTP2) defines an MTP2 tunnel.
There is 1 interface that is used for the M2UA Media Gateway Controller <=>
M2UA SG connection.
There are 4 interface IDs defined: 1 per link (M2UA Media Gateway Controller
side).
To load the example of an SS7 MTP2 Tunneling ini file, take these
4 steps:
1.
Version 4.8
Load this ini file (as shown below, 'SS7 MTP2 Tunneling ini File Example Media Gateway Controller') on a Tunnel central gateway (MTP2 Media Gateway
Controller).
487
January 2006
Mediant 3000
2.
Load the ini file as shown in 'SS7 MTP2 Tunneling ini File Example - SG' on a
tennel remote gateway (MTP2 SG). The Media Gateway Controller gateway
connects (over IP) to the SG gateway. For more information on loading an ini file,
refer to the ''Software Upgrade Wizard'' on page 266.
3.
In the Media Gateway Controller gateway, change the parameter'SS7_DEST_IP'

to the actual IP address of the M2UA SG gateway.
4.
Change the value of the 'SyslogServerIP' parameter in the Media Gateway

Controller and SG gateways to your Syslog server IP address.
The following is an example of SS7 MTP2 Tunneling ini File

; 1=aLaw 3=ulaw
PCMLawSelect=
1
; EXT_BUS=5
TDMBusType=
H110=4
2
QSLAC=3
FRAMERS=2
SC_BUS=1
MVIP_BUS=0
; 0=2048kbps, 2=4096kbps, 3=8192kbps

TDMBusSpeed=
3
ProtocolType = 5
TraceLevel
= 0
CLOCKMASTER= 1
TerminationSide = 1
FramingMethod = 0
;acB8ZS = 0
LineCode = 0
2 for E1_CAS - FCD
Q931RELAYMODE = 0
[SS7]
SS7_MTP2_PARAM_TIMER_T4E_0=500
SS7_MTP2_PARAM_TIMER_T4N_0=8200
;
[syslog]
;SYSLOGSERVERIP = 168.100.0.1
ENABLESYSLOG = 1
User's Manual
488
User's Manual
WATCHDOGSTATUS = 0
[ SS7_LINK_TABLE ]
SS7_LINK_GROUP_ID, SS7_LINK_M2UA_IF_ID;
SS7_LINK_TABLE 1 = new_link_1, 0, 2, 2, 3, 4, 50;
[ \SS7_LINK_TABLE ]
[ SS7_LINK_TABLE ]
SS7_LINK_TRUNK_NUMBER,SS7_LINK_TIMESLOT_NUMBER,
SS7_LINK_LAYER2_VARIANT,SS7_LINK_MTP2_ATTRIBUTES,SS7_CONGESTION_LOW
_M ARK, SS7_CONGESTION_HIGH_MARK, SS7_LINK_TNL_MGC_LINK_NUMBER,
SS7_LINK_TNL_ALIGNMENT_MODE, SS7_LINK_TNL_CONGESTION_MODE,
SS7_LINK_TNL_WAIT_START_COMPLETE_TIMER,
SS7_LINK_TNL_OOS_START_DELAY_TIMER,
SS7_LINK_TNL_WAIT_OTHER_SIDE_INSV_TIMER;
SS7_LINK_TABLE 0 = new_link_0,
1, 0, 30000, 5000, 30000;
1, 0, 30000, 5000, 30000;
1, 0, 30000, 5000, 30000;
1, 0, 30000, 5000, 30000;
[ \SS7_LINK_TABLE ]
0, 2, 1, 3, 0, 15, 1, 0, 5, 50, 1,
0, 2, 1, 3, 3, 12, 1, 0, 5, 50, 3,
0, 2, 1, 3, 6,
7, 1, 0, 5, 50, 5,
0, 2, 1, 3, 7,
3, 1, 0, 5, 50, 7,
2904, 1,2904,168.100.0.2,3,3;
, 4, 2, 7, 0;
The following is an example of SS7 MTP2 Tunneling ini File Example - SG.
; 1=aLaw 3=ulaw
PCMLawSelect=
1
; EXT_BUS=5
TDMBusType=
Version 4.8
H110=4
2
QSLAC=3
489
FRAMERS=2
SC_BUS=1
MVIP_BUS=0
January 2006
Mediant 3000
; 0=2048kbps, 2=4096kbps, 3=8192kbps

TDMBusSpeed=
3
ProtocolType = 5
TraceLevel
= 0
CLOCKMASTER= 1
TerminationSide = 1
FramingMethod = 0
;acB8ZS = 0
LineCode = 0
2 for E1_CAS - FCD
Q931RELAYMODE = 0
; for ss7 configuration . 77 is for SS7 debug with TSL and 0 is
noth ing
; 7 is for M2ua DRAFT 7 ; 101 for UAL netbricks
PSTNRESERVED3= 101
[MEGACO]
[megaco conference support]
MGControlprotocoltype =2
ATMPHYTYPE=1
PHYCLKSOURCE=0
[syslog]
ENABLESYSLOG = 1
WATCHDOGSTATUS = 0
[ SS7_LINK_TABLE ]
SS7_LINK_TRUNK_NUMBER,SS7_LINK_TIMESLOT_NUMBER,SS7_LINK_M2UA_IF_ID;
SS7_LINK_TABLE
SS7_LINK_TABLE
SS7_LINK_TABLE
SS7_LINK_TABLE
0
1
2
3
=
=
=
=
new_link_0,
new_link_1,
new_link_2,
new_link_3,
0,
0,
0,
0,
2,
2,
2,
2,
1,1,
1,1,
1, 1,
1, 1,
1, 15,50;
2, 12, 12;
4, 7,18;
5, 3,1;
[\SS7_LINK_TABLE]
User's Manual
490
User's Manual

2904, 1;
, 4, 2, 3, 0;
21.3
SS7 Tunneling: Feature Description

The SS7 tunneling feature facilitates peer-to-peer transport of SS7 links between
gateways that support this unique MTP2 Tunneling application (M2TN) for transferring
SS7 MTP2 link data over IP. In this scenario, both sides of the link are pure TDM
switches and are unaware of the IP tandem that is utilized between them. Using
M2TN, the network operator can support SS7 connections over IP, carrying MTP level
3, as well as higher level SS7 layers (e.g., user parts and application protocols, such
as TUP, ISUP, SCCP, TCAP, etc.).
Version 4.8
491
January 2006
Mediant 3000
M2TN uses standard protocols, such as SigTran (RFC 2719 Architectural Framework
for Signaling Transport), SCTP (RFC 2960, Stream Control Transmission Protocol),
M2UA (RFC 3331), and MTP2 User Adaptation Layer, the latter being used for
transporting SS7-MTP2 signaling information over IP. M2UA architecture iand M2TN
architecture are shown in the figures below.
Figure 21-5: M2UA Architecture
Figure 21-6: M2TN Architecture
User's Manual
492
User's Manual
21.3.1
MTP2 Tunneling Technology

The SS7 Tunneling technology is based on a pairing of remote and central gateways,
as shown in the figure below. The remote gateways are configured to backhaul MTP
layer 2 signaling over the IP network using standard M2UA protocol (over SCTP
protocol). The function of the M2TN entity is to transmit traffic and handle all
management events between MTP2 on the TDM side and M2UA's Media Gateway
Controller entity on the IP side. Only the actual SS7 message (MSU) data is sent.
Management of the SS7 link is performed using M2UA without transporting the MTP2
LSSU and FISU messages over IP. These messages, in addition to MTP2 timing, are
terminated and supported, respectively, by the remote and central sides. Therefore,
the MTP2 connections are not affected by the fact that they are transported over IP.
Figure 21-7: Protocol Architecture for MTP2 Tunneling
21.3.2
IUA /DUA Behind NAT Support

To be able to support IUA SG functionality behind a NAT, SG needs to initiate SCTP
(by sending SCTP init to the MGC Side). After SCTP association establishment, SG
waits for ASP commands from MGC. This is done via new configuration of the
following line in SS7_SIG_IF_GROUP table. Note: This line is valid also for DUA.
9900, 1,9900,10.31.4.100,3,3;
Version 4.8
SS7_DEST_IP is MGCs IP.

493
January 2006
Mediant 3000
21.3.3
User's Manual
SS7_MGC_MX_IN_STREAM and SS7_MGC_NUM_OUT_STREAM values

need to be coordinated with the value that is configured in the MGC side.
SS7 Characteristics
Only standard protocols are used on external interfaces (MTP2 on PSTN side,
and M2UA over SCTP on IP side) - the M2TN application resides internally in the
AudioCodes gateway.
No extra signaling point codes are required; both endpoints are unaware that the
SS7 connection is via IP.
Several links from multiple SS7 nodes can be concentrated into a single board on
the "Central" side (using several SCTP associations per gateway).
AudioCodes' gateways can handle both SS7 MTP2 Tunneling and voice
concurrently (does not require additional gateway or other server).
Voice and signaling may be transferred on same E1/T1 trunk (F-Links).
IP traffic can be monitored via standard sniffing tools (e.g., protocol analyzers).
494
User's Manual
22
22. Appendix - Utilities
Appendix - Utilities
This section describes the functionality and operation of a list of utilities supplied with
the TrunkPack software package.
22.1
API Demonstration Utilities

LOCATION:
.\VoP_API_Library\VoPLib_Tcl_Extension\<OS>\<CPU>\apirunce
.\VoP_API_Library\VoPShell\Bin\voipsh.exe
DESCRIPTION:
These utilities are designed to serve both as a reference for using the VoPLib and as
demo applications, which the user can run immediately after installing the
board/module.
OPERATION:
The Apirunce Application - TCL-based demo program available for Linux,
Solaris and Windows OSs. With this application the user can build scripts online
or offline and execute them. All new APIs in this version are supported by Apirunce.
The VoPShell Application - Console-based demo program. (This tool only supports
up to version 4.2 based APIs, for new APIs refer to the Apirunce application).
22.2
TrunkPack Downloadable Conversion Utility

LOCATION:
.\Utilities\ Downloadables Construction Utility\DConvert.exe
Version 4.8
495
January 2006
Mediant 3000
Figure 22-1: TrunkPack Downloadable Conversion Utility R2.5.2
This utility is used to generate the following:
Process Call Progress Tones file(s)
Process Voice Prompts file(s)
Process CAS Tables (Even though this utility is listed in the main menu, it is
NOT applicable to IPmedia 3000, MP products, TPM-1100)
Process VXML file(s) (Even though this utility is listed in the main menu, it is
applicable to IPmedia 2000 and IPmedia 3000 only)
Process Prerecorded Tones file(s)
Process Encoded/Decoded ini file(s)
Process Coder Description file(s)
The files constructed using these utilities can be used when:
Configuring the board using the VoPLib function acOpenBoard().
Using an ini file during BootP/DHCP session
Using the Web Interface
Some files may have usage restrictions as described under their usage information.
User's Manual
496
User's Manual
22.2.1
Process Call Progress Tones file(s)
22.2.1.1
Converting a CPT ini File to a Binary dat File

To convert a CPT ini file to a binary dat file, take these 8 steps:
1.
Create a CPT ini file using the direction in ''Modifying the Call Progress Tones
File'' on page 415 or by editing a CPT ini file provided by AudioCodes.
2.
Execute DConvert.exe and click the Process Call Progress Tones file(s)
button. The Call Progress Tones dialog appears.
Figure 22-2: Call Progress Tones Screen
3.
Click the Select File . . . button and navigate to the location of the CPT ini file
that you want to convert.
4.
Select the desired file and click Open. The name and path of both the CPT ini file
and the dat file appear in the Using File field and Output File field respectively.
(The file names and paths are identical except for the file extension.)
5.
Fill in the Vendor, Version and Version Description fields.
6.
7.
Version 4.8
Vendor field - 256 characters maximum
Version feld - must be made up an integer, followed by a period '.', then

followed by another integer (e.g., 1.2, 23.4, 5.22)
Description field - 256 characters maximum
The default value of the CPT version drop-down list is Version 3. Do one of the
following:
If the software version release you are using is 4.4, in the CPT Version
drop-down list, select Version 2.
If the software device version release is prior to version 4.4, in the CPT
Version drop-down list, select Version 1 (to maintain backward
compatibility).
The Use dBm units for tone levels checkbox is not checked as the default. To
use -dBm units for setting the Call Progress Tone and User Defined Tone Levels,
click a checkmark into the Use dBm units for tone levels checkbox. This
checkbox should be checked to maintain backward compatibility.
497
January 2006
Mediant 3000
Note: The default value of the dBm units for tone levels checkbox is left
unchecked for backward compatibility with versions prior to version 4.4.
8.
22.2.2
Click the Make File button. The dat file is generated and placed in the same
directory as shown in the Output File field. A message box informing you that the
operation was successful indicates that the process is completed.
Process Voice Prompts file(s)

To generate a Voice Prompts file, take these 12 steps:
1.
Create raw Voice Prompt files according to the instructions in the section on
Relaying DTMF/MF Digits in the VoPLib Users Manual, Document #: LTRT844xx). From version 4.2, DConvert supports wav files as well.
2.
Execute DConvert.exe and click the Process Voice Prompts file(s) button. The
Voice Prompts window appears.
Figure 22-3: Voice Prompts Screen
3.
Select the raw Voice Prompt files (created in Step 1) step either by one of these
actions:
a.
Click the Add Files button in the upper right corner. The Add Files window
appears. (Refer to the figure, "Select Files Window" below.)
Navigate to the appropriate file.
User's Manual
498
User's Manual
Select it and click the Add>> button. To close the Add Files window, click
the
Exit button. (Press the Esc key to cancel changes.)

Figure 22-4: Select Files Window
Version 4.8
499
January 2006
Mediant 3000
Figure 22-5: Voice Prompts Window with wav Files
b.
4.
From any location on the PC, select the appropriate files and drag-drop them
into the Voice Prompts window.
Arrange the files as desired by dragging and dropping them from one location in
the list to another location.
Note: The sequence of files in the Add Files... window defines the Voice Prompt
ID.
5.
Use the Play button to preview the sound of the wav file. Use the Remove and
Remove all buttons to remove files in the list as needed.
6.
Select a coder for each file by first selecting the file (or files) and then doubleclicking or right-clicking on it. The File Data window appears.
Figure 22-6: File Data Window
User's Manual
7.
From the Coder drop-down list, select a coder type (to be used by the
acPlayVoicePrompt() function).
8.
In the Description field, enter a description (optional).

500
User's Manual
Note: For wav files, a coder is automatically selected from the wav file header.
9.
Close the File Data dialog by clicking on the

Exit button. (Press the Esc key
to cancel changes.). You are returned to the Voice Prompts window.
10. The default Output file name is voiceprompts.dat.You can modify it. Or,
Browse button to select a different Output file. Navigate to the
Use the
desired file and select it. The selected file name and its path appear in the
Output field.
11. Click the Make File(s) button to generate the Voice Prompts file. The Progress
bar at the bottom of the window is activated. The dat file is generated and placed
in the same directory as shown in the Output File field. A message box informing
you that the operation was successful indicates that the process is completed.
12. The generated file can be used only for downloading using the ini file facility or
using acOpenRemoteBoard() in full configuration operation mode. When using
the acAddVoicePrompt(), use the single raw voice prompt files.
22.2.3
Process CAS Tables

To produce a CAS table, take these 10 steps:
Version 4.8
1.
Construct the CAS protocol xxx.txt and xxx.h files according to the instructions in
the sections on Caller ID Support and CAS Protocol Table in the VoPLib
Users Manual, Document #: LTRT-844xx.
2.
Copy the files generated in the previous step (or at least the xxx.h file) to the
same directory in which DConvert.exe is located and make sure that the two
following files, CASSetup.h and CPP.exe, are also located in this same directory.
501
January 2006
Mediant 3000
3.
Execute DConvert.exe and click the Process CAS Tables button. The Call
Associated Signaling (CAS) Window appears.
Figure 22-7: Call Associated Signaling (CAS) Screen
4.
Click the Select File button. A Browse window appears.
5.
Navigate to the desired location and select the file to be converted. (This
automatically designates the output file as the same name and path, but with the
dat extension. The Table Name is also automatically designated.)
6.
Fill in the Vendor and Version fields.
Vendor Field - 32 characters maximum
Version Field - must be made up an integer, followed by a period ., then

followed by another integer (e.g., 1.2, 23.4, 5.22)
7.
Modify the Table Name if desired.
8.
For troubleshooting purposes, you can click a check into the Output state
names to file checkbox. This activates the file name field in which the default file
name, TableState Names.txt appears. You can modify the file name if desired.
The file is located in the same directory as the Using file and Output file
designated above.
9.
If the file to be converted uses the new table header, un-check the Force old
table header checkbox.
10. Click the Make File button. The dat file is generated and placed in the same
directory as shown in the Output File field. A message box informing you that the
operation was successful indicates that the process is completed.
On the bottom of the Call Assisted Signaling (CAS) Files(s) window, the Cas output
log box displays the log generated by the process. It can be copied as needed. The
information in it is NOT retained after the window is closed.
User's Manual
502
User's Manual
22.2.4
Process Prerecorded Tones File(s)

To generate a Prerecorded Tones file, take these 11 steps:
1.
Prior to the conversion process, the user should prepare the appropriate
prerecorded tones file(s).
2.
Execute DConvert.exe and press the Process Prerecorded Tones file(s)

button. The Prerecorded Tones file(s) window appears.
Figure 22-8: Prerecorded Tones File(s) Screen
3.
Select the raw Prerecorded Tones files (created in Step 1) utilizing one of these
actions:
a.
Click the Add Files button in the upper right corner. The Add Files window
appears. (Refer to the figure, Select Files Window.)
Navigate to the appropriate file.
Version 4.8
503
January 2006
Mediant 3000
Select it and click the Add>> button. (To close the Add Files window, click
the
Exit button. Press the Esc key to cancel changes.) You are returned
to the Prerecorded Tones file(s) window.
Figure 22-9: Prerecorded Tones File(s) Screen with wav Files
b.
4.
From any location on the PC, select the appropriate files and drag-drop them
into the Prerecorded Tones File(s) Screen.
To define a tone type, coder and default duration for each file, select the file (or
group of files to be set the same) and double click or right click on it. The File
Date window appears.
Figure 22-10: File Data Dialog Box
User's Manual
5.
From the Type drop-down list, select a Ring parameter type.
6.
From the Coder drop-down list, select a coder type (G.711 A-law_64, G.711 law, or Linear PCM).
7.
In the Description field, enter a description (optional).
8.
In the Default field, enter the duration in msec.
9.
Click the
Exit button. (Press the Esc key to cancel changes.) You are
returned to the Prerecorded Tones file(s) window.
504
User's Manual
10. The default Output file name is prerecordedtones.dat. You can modify it. Or,
Use the
Browse button to select a different Output file. Navigate to the
desired file and select it. The selected file name and its path appear in the
Output field.
11. Click Make File(s) button. The Progress bar at the bottom of the window is
activated. The dat file is generated and placed in the same directory as shown in
the Output File field. A message box informing you that the operation was
successful indicates that the process is completed.
22.2.5
Process Encoded/Decoded ini File(s)

The ini file can be both encoded and decoded using DConvert. Encoding usually
takes place before downloading an ini file to the board while decoding usually takes
place after uploading an ini file from the board.
To Encode an ini file, take these 4 steps:

1.
Prior to the encoding process, the user should prepare the appropriate ini file
either by uploading from the board or by constructing one (refer to ''Initialization
(ini) File'' on page 91).
Execute DConvert.exe and click the Process Encoded ini file(s) button. The
Encoded ini file(s) window appears.
Figure 22-11: Encoded ini File(s) Screen
2.
In the Encode ini File(s) area, click the Select File Button. A Browse window
appears.
3.
Navigate to the desired location and select the ini file to be encoded. (This
automatically designates the output file as the same name and path, but with the
aen extension.
Note: The Password field is to be implemented in a future version.
Version 4.8
505
January 2006
Mediant 3000
4.
Click the Encode File(s) button. The encoded file is generated and placed in the
same directory as shown in the Output File field. A message box informing you
that the operation was successful indicates that the process is completed.
The encoded ini file can be loaded using the regular ini file procedure. To upload a
file from a device, use the Web Interface (refer to ''Software Update'' on page 265).
To Decode an ini file, follow these 4 steps:

1.
Prior to the decoding process, the user should prepare the appropriate encoded
ini file either by uploading from the board or by using the encoding process on an
exiting ini file.
2.
Execute DConvert.exe and click the Process Encoded ini file(s) button.
3.
In the Decode ini File(s) area, click Select File(s) and select the aen file to be
decoded. (This automatically designates the output file as the same name and
path, but with the extension, _dl.ini.
4.
Click the Decode File(s) button. The decoded file is generated and placed in the
same directory as shown in the Output File field. A message box informing you
that the operation was successful indicates that the process is completed.
Note: The decoding process verifies the input file for validity. Any change made
to the encoded file causes an error and the decoding process is aborted.
22.3
PSTN Trace Utilities

LOCATION:
.\Utilities\PSTN Trace Utility
DESCRIPTION:
These utilities are designed to convert PSTN trace binary files to text format. The
binary PSTN trace files are generated when the user sets the PSTN interface to trace
mode.
OPERATION:
Generating a Trace/audit Text File for CAS Protocols
To generate a readable text file out of the binary trace file when
using CAS protocols, take these 3 steps:
1.
Rename the PSTN trace binary file to CASTrace0.dat.
2.
Copy it to the same directory in which the translation utility, CAS_Trace.exe, is

located.
3.
Run CAS_Trace.exe (no arguments are required). The text file, CASTrace0.txt, is
created.
Generating a Trace/audit Text File for ISDN/SS7/ATM Protocols
To generate a readable text file out of the binary trace file when
User's Manual
506
User's Manual
using ISDN/SS7/ATM protocols, take these 2 steps:

1.
Copy the PSTN trace binary file to the same directory in which the translation
utility CONVERT_TRACE.BAT is located. The following files should reside in the
same directory: Dumpview.exe, Dumpview.cfg and ReadMe.txt.
Read carefully the ReadMe.txt in order to understand the usage of the translation
utility.
2.
22.4
Run the CONVERT_TRACE.BAT. The text file is created.
Enabling PSTN Trace via the Web

This section contains direction on starting and collecting the PSTN trace via the Web.
(Refer to the figure below for a view of the Trunk Traces). Also, note if the PSTN trace
is of a ISDN/SS7/ATM or CAS collection based on the physical device involved in the
trace. This information is needed to properly parse the captured data.
To start and collect the PSTN trace via the Web, take these 12
steps:
1.
Run the UDP2File utility.
2.
Determine the trace file name.
3.
Determine the UDP port.
4.
Mark the PSTN Trace check box.
5.
Click the Run button. The UDP2File utility starts to collect the trace messages.
6.
Activate the Web page by entering <Mediant 3000 IP address>/TrunkTraces and

choose the Trunk Traces tab (e.g.,http://10.8.8.101/TrunkTraces).
7.
Use the user and password, which is the same for the unit.
8.
In the Web page, set the trace level of each trunk.
9.
Enable the trace via the Web.
10. Determine the UDP port (the same as in step 3).

11. Click the SUBMIT button. The board starts to send the trace messages.
Version 4.8
507
January 2006
Mediant 3000
12. In the UDP2File utility (Refer to the figure below) you should see the number in
the packets counter increasing.
Figure 22-12: Trunk Traces Screen
Figure 22-13: UDP2File Utility Dialog Box
User's Manual
508
User's Manual
23
23. Appendix - MGCP Compliance
Appendix - MGCP Compliance
The MGCP Compliance Matrix Table below summarizes the supported MGCP features respectively.
The Reference column in the table refers to IETF RFC 3435 from January 2003 (which replaced RFC
2705).
23.1
MGCP Compliance Matrix

Table 23-1: MGCP Compliance Matrix
AudioCodes
Comments
References
(to IETF RFC 3435)
Yes
IP address is used to
identify Call Agent
Pages 23, 96
Yes
12 Digit Maps
Such as:
R: [0 -9](D)
R: D/X(D)
D: xxxx | 88# | 7xx|xxxT
5x.T
2.1.5
Feature
Support
"*" Wild-carding
Yes
"$" Wild-carding
Yes
Domain name for

Call Agent
Digit Maps
Timer indication - T Yes
Interdigit timer Fixed Timer

of 4 sec is used
Digits and Letters

#
Yes
Yes
X.
Yes
Yes
[0-9]
Yes
A,B,C,D
Yes
Event names
Yes
Wildcard notations
(X, $, *,all)
Yes
Optional
connection ID
(G/rt@A3F58)
Yes
Version 4.8
X. - Arbitrary number of X
Occurrences
For digit maps
509
January 2006
Mediant 3000
Feature
Support
AudioCodes
Comments
References
(to IETF RFC 3435)
2.1.7
Signals
On/Off (OO)
Yes
Time out (TO)
Yes
Brief (BR)
Yes
Using "+", "-" to

turn on/off the
"OO" Signal
Yes
3.2.2.6
Connection
modes
Inactive
Yes
Send only
Yes
Receive only
Yes
Send/receive
Yes
Conference
Yes
Data
No
Loopback
Yes
Continuity test
Yes
Network loop back
Yes
Network continuity
(netwtest)
Yes
Endpoint
Configuration
command
Yes
2.3.2
2.3.3
Notification
Request
command
Endpoint ID
Yes
Notified Entity
Yes
RequestedEvents
(with associate
actions)
Yes
RequestIdentifier
Yes
DigitMap
Yes
If not specified, notifications

is send to command
originator
Defined explicitly
Yes
or through a
previous command
User's Manual
510
User's Manual
Feature
Support
SignalRequests
Yes
AudioCodes
Comments
References
(to IETF RFC 3435)
Quarantine
Handling
Discard
Yes
Process loop
Yes
Process
Yes
Loop
No
Process step by
step
Requested events
Yes
Digit map
Yes
DetectEvents
Yes
Encapsulated
Endpoint
Configuration
Yes
Event associated
actions
Notify event
immediately with
all accumulated
events
Yes
Swap audio
No
Accumulate event
in buffer, but do
not notify yet
Yes
Accumulate
according to digit
map
Yes
Keep signal active
Yes
Process
Embedded
Notification
Request
Yes
Ignore the event
Yes
Supporting two or
more actions,
hf(S,N)
Yes
Version 4.8
Combining up to 2 actions
511
January 2006
Mediant 3000
Feature
Support
AudioCodes
Comments
Persisted events
Yes
Configurable
Number of active
connection on an
endpoint
1 to 3
1 only when using

encryption; otherwise up to
3
Synchronization of
Signalrequest
action with
detected event
Yes
TO (Timeout) signals stop

when one of the requested
events is detected
References
(to IETF RFC 3435)
Example 1: Ringing stops if

off-hook event was detected
Example 2: Dial tone stops if
DTMF was detected
Notification request Yes

with empty signal
list for stopping
tone generation
Detection of events Yes
on Connections
2.3.4
Notifications
EndpointID
Yes
NotifiedEntity
Yes
RequestIDentifier
Yes
ObservedEvents
Yes
2.3.5
Create
Connection
command
CallID
Yes
Endpoint
Yes
NotifiedEntity
Yes
Multiple
connections per
endpoint
Yes
- Up to 3 connections
- Only one of them can be in
send/send receive mode
- 1 connection when using
encryption
LocalConnection
Options
Encoding method
Yes
One value
List of values not supported
User's Manual
512
User's Manual
AudioCodes
Comments
Feature
Support
Packetization
period
Yes
SDP "ptime" parameter

Supports only 20 msec
Bandwidth
Yes
Parsing only
Type of Service
(TOS)
Yes
2 Hex digits
Echo cancelation
Yes
Silence
suppression
Yes
Gain control
Yes
Reservation
service
No
RTP security
Yes
Type of network
(IN, Local, ATM)
Yes
Vendor specific
extensions
Yes
Mode
Yes
References
(to IETF RFC 3435)
-32 to +31 value
Providing Key as per RFC

2327
RemoteConnection Yes
Descriptor
SecondEndpointID
Yes
Encapsulated
Notification
Request
R:
Yes
S:
Yes
Encapsulated
Endpoint
Configuration
Yes
Create
Connection
return parameters
ConnectionID
Yes
SpecificEndpointID Yes
("Z")
LocalConnection
Descriptor
Version 4.8
Yes
513
January 2006
Mediant 3000
Feature
Support
SecondEndpointID
Yes
Secondconnection
ID
Yes
Second M line for

Fax t38
Yes
AudioCodes
Comments
References
(to IETF RFC 3435)
2.3.6
ModifyConnectio
n
CallID
Yes
Endpoint
Yes
Connection ID
Yes
NotifiedEntity
Yes
LocalConnection
Options
Yes
Mode
Yes
See CreateConnectionCmd
above
RemoteConnection Yes
Descriptor
Encapsulated
Notification
Request
R:
Yes
S:
Yes
Encapsulated
Endpoint
Configuration
No
Modify
Connection
Return
Parameters
LocalConnection
Descriptor
Yes
Returns if local connection

parameters were modified
2.3.7
Delete
Connection (from
Call Agent)
CallID
Yes
EndpointID
Yes
ConnectionID
Yes
Encapsulated
Notification
User's Manual
514
User's Manual
Feature
Support
AudioCodes
Comments
References
(to IETF RFC 3435)
Request
R:
Yes
S:
Yes
Encapsulated
Endpoint
Configuration
No
Delete
Connection
return
Parameters
Connection
Parameters
Number of packets
send
Yes
Number of octets
send
Yes
Number of packets
received
Yes
Number of octets
received
Yes
Number of packets
lost
Yes
Inter-packet arrival
jitter
Yes
Average
transmission
delay - latency
Yes
Delete
Connection
(from gateway)
Yes
CallID
Yes
EndPointID
Yes
ConnectionID
Yes
ReasonCode
Yes
Connection
Parameters
Yes
Version 4.8
2.3.8
515
January 2006
Mediant 3000
Feature
Support
AudioCodes
Comments
DeleteConnection Yes
(multiple
connections)
CallID
Yes
EndPointID
Yes
References
(to IETF RFC 3435)
2.3.9
Audit Endpoint
EndpointID
Yes
RequestedInfo
Yes
Wildcard
convention * ("all
of")
Yes
2.3.10
AuditEndpoint
Return
Parameters
Endpoint ID list,
"Z='
Yes
RequestedEvents
Yes
Including actions
Yes
associated with the
events
DigitMap
Yes
SignalRequests
Yes
TO signals
currently active
On/Off signals
currently ON
Pending Brief
signals
RequestIDentifier
Yes
NotifiedEntity
Yes
Connection
Identifiers
Yes
DetectEvents
Yes
ObservedEvents
Yes
EventStates
Yes
User's Manual
516
User's Manual
Feature
Support
Bearer
Information
No
RestartReason
Yes
RestartDelay
Yes
ReasonCode
No
AudioCodes
Comments
References
(to IETF RFC 3435)
Capabilities
List of supported
codecs
Yes
Packetization
Period
No
Bandwidth
No
Echo Cancelation
No
Silence
Suppression
No
Gain Control
No
Type of Service
No
Resource
Reservation
No
Encryption Key
No
Encryption Suites
Yes
Type of Network
Yes
Supported Event
Packages
Yes
Connection Modes
Yes
Audit Connection
Yes
ConnectionID
Yes
RequestedInfo
Yes
2.3.11
Audit Connection
Return
Parameters
CallID
Yes
Notified Entity
Yes
Local
Connection
Options
Yes
Version 4.8
517
January 2006
Mediant 3000
Feature
Support
Mode
Yes
Remote
Connection
Descriptor
Yes
LocalConnection
Descriptor
No
Connection
Parameters
Yes
AudioCodes
Comments
References
(to IETF RFC 3435)
2.3.12
Restart in
Progress (RSIP)
EndpointID
"All of" wildcard (*)
Yes
Restart Method
Yes
Graceful
Yes
Forced
Yes
Restart
Yes
Disconnected
Yes
Cancel-graceful
Yes
Restart Delay
Yes
ReasonCode
No
Restart in progress No
return parameters
(notified entity &
return code)
Return Codes
and Error Codes
Partially
100
Yes
2.4
The transaction is currently
being executed
An actual completion
message will follow later
200
Yes
The requested transaction

was executed normally
210-214
Yes
CALEA return codes
250
Yes
The connection was deleted
User's Manual
518
User's Manual
AudioCodes
Comments
Feature
Support
400
Yes
The transaction couldn't be

executed due to a transient
error
401
Yes
The phone is already off

hook
402
Yes
The phone is already on

hook
405
Yes
The transaction could not be

executed, because the
endpoint is "restarting".
500
Yes

executed because the
endpoint is unknown
501
Yes

endpoint is not ready
502
Yes

endpoint does not have
sufficient resources
503
No
"All of" wildcard not fully

supported
References
(to IETF RFC 3435)
The transaction contained

an "all of" wildcard, however
NotificationRequests nonempty
504
Yes
Unknown or unsupported
command.
505
Yes
Unsupported
RemotedConnectionDescrip
tor
506
Yes
Unable to satisfy both

LocalConnectionOptions
and RemoteConnection
Descriptor
507
Yes
Unsupported functionality
510
Yes

executed because a
protocol error was detected
511
Yes

executed because of the
command contained an
unrecognized extension
Version 4.8
519
January 2006
Mediant 3000
AudioCodes
Comments
Feature
Support
512
No

gateway is not equipped to
detect one of the requested
events
513
Yes

gateway is not equipped to
generate one of the
requested signals
514
Yes

gateway cannot send the
specified announcement
515
Yes
The transaction refers to an

incorrect connection ID
516
Yes
The Transaction refers to an

unknown call ID
517
Yes
Unsupported or invalid
mode
518
Yes
Unsupported or unknown
package
519
Yes
Gateway does not have a

digit map
520
Yes

GateWay is restarting
521
Yes
Endpoint redirected to
another Call Agent endpoint
is restarting
522
Yes
No such event or signal
523
Yes
Unknown action or illegal

combination of actions
524
Yes
Internal inconsistency in
localConnectionOptions
525
Yes
526
No
527
Yes
User's Manual
520
References
(to IETF RFC 3435)
User's Manual
AudioCodes
Comments
Feature
Support
528
Yes
529
No
530
No
531
Yes
532
Yes
Unsupported value in
LocalConnectionOptions
533
Yes
Response too big
534
Yes
Codec negotiation failure
535
Yes
Packetization period not

supported
536
No
RestartMethod
537
Yes
digit map extension
538
Yes
Event or SIgnal error
6xx
Yes
Basic and advanced audio

packages
Reason Codes
(900, 901, 902)
No
3.2
MGCP Command
Header
Endpoint identifier
Yes
Notified entity
Yes
In notified entity, If
port # is omitted,
using default
MGCP port (2427)
Yes
Response
Acknowledgement
Yes
(receive
side
only)
3.5
Encoding of
Session
Description - SDP
Version 4.8
References
(to IETF RFC 3435)
521
January 2006
Mediant 3000
Feature
Support
SDP parameters:
v,c,m,a
Yes
Using RTPMAP
attribute to define
encoding of
dynamic audio
formats
Yes
Optional Ptime
attribute to define
packet duration
Yes
IP address of
remote/local
gateways
Yes
AudioCodes
Comments
References
(to IETF RFC 3435)
3.5
Transmission
over UDP
Transaction
identifiers
Yes
Receiving
Duplicated
transaction IDs
Yes
Retransmission
timers
Yes
Piggy backing
Yes
Provisional
responses
Yes
MultipleCall Agents Yes

and Call Agent
Redundancy
States, failover and Yes
race conditions
4.1
Failover
Assumptions and
Highlights
Call Agents DNS
Yes
Notified Entity for

endpoint
Yes
Responses send to Yes

source address
Backup Call Agent
User's Manual
Yes
522
User's Manual
Feature
Support
AudioCodes
Comments
4.3
Retransmission,
Detection of Lost
Associations
Commands
retransmission
Yes
Disconnecting
endpoint/gateway
Yes
4.4
Race Conditions
Quarantine list
Yes
Explicit detection
Yes
Ordering of
commands
Yes
Restart avalanche
Yes
Disconnected
endpoints
Yes
5
Security
requirements
MGCP IP security
(RFC 1825)
Version 4.8
References
(to IETF RFC 3435)
No
523
January 2006
User's Manual
24
24. Appendix - MEGACO Compliance
Appendix - MEGACO Compliance

The MEGACO Compliance Matrix table below summarizes the supported MEGACO
features. The Reference column in the table refers to IETF RFC 3015 from September
2002.
24.1
MEGACO Compliance Matrix

Table 24-1: MEGACO Compliance Matrix
Reference
Item
(in RFC 3015)
7
Add
Yes
Modify
Yes
Subtract
Yes
Move
Yes
AuditValue
Yes
AuditCapabilities
Yes
Notify
Yes
ServiceChange
Yes
Descriptors
7.1.1
Specifying Parameters:
Version 4.8
Comments
Commands supported:
7.1
7.1.2
Support
Fully specified
Yes
Under specified
Yes
Over specified
Yes
Handling unspecified mandatory

parameters.
Yes
Wildcarded termination ID
Yes
Modem Descriptor:
V.18
No
V.22
No
V.22bis
No
V.32
No
525
January 2006
Mediant 3000

Reference
Item
(in RFC 3015)
7.1.3
7.1.4
7.1.5
Support
V.32bis
No
V.34
No
V.90
No
V.91
No
Synchronous ISDN
No
Comments
Multiplex Descriptor:
H.221
No
H.223
No
H.226
No
V.76
No
Media Descriptor:
Termination State Descriptor
Yes
Stream Descriptor
Yes
Local Control Descriptor
Yes
Local Descriptor
Yes
Remote Descriptor
Yes
Termination State Descriptor:

Service State:
7.1.6
Test
Yes
Out of service
Yes
In service
Yes
EventBufferControl:
Yes
Stream Descriptor:
Yes
7.1.7
Local Control Descriptor:

Mode:
User's Manual
Send-only
Yes
Receive-only
Yes
Send/receive
Yes
Inactive
Yes
526
User's Manual

Reference
Item
(in RFC 3015)
7.1.8
7.1.9
Support
Comments
Loop-back
Yes
ReserveGroup
No
This is treated as if the

default is 'yes'
ReserveValue
No
This is treated as if the

default is yes
Local & Remote Descriptors:

Unspecified Local Descriptor
Yes
Unspecified Remote Descriptor
Yes
Empty Local Descriptor
Yes
Empty Remote Descriptor
Yes
Multiple groups
No
Event Descriptor
EventBufferControl
7.1.10
Lockstep
Yes
Off
Yes
Event Buffer Descriptor

Yes
7.1.11
Signal Descriptor
Signal Types
7.1.12
Version 4.8
On/off
Yes
Timeout
Yes
Brief
Yes
Sequential signal list
Yes
Simultaneous signals
No
Keep active
Yes
Audit Descriptor
Modem
No
Mux
No
Events
Yes
Media
Yes
Signals
Yes
527
January 2006
Mediant 3000

Reference
Item
(in RFC 3015)
7.1.13
7.1.14
7.1.15
7.1.16
Support
Observed events
Yes
DigitMap
Yes
Statistics
Yes
Packages
Yes
EventBuffer
Yes
Empty descriptor
Yes
Comments
Service Change Descriptor

ServiceChangeMethod
Yes
ServiceChangeReason
Yes
ServiceChangeAddress
Yes
ServiceChangeDelay
Yes
ServiceChangeProfile
Yes
ServiceChangeVersion
Yes
ServiceChangeMGCId
Yes
TimeStamp
Yes
Digit Map Descriptor

Digit Map Names
Yes
StartTimer (T)
Yes
ShortTimer (S)
Yes
LongTimer (L)
Yes
DurationModifier (z)
Yes
Any digit 0-9 (x)
Yes
Zero or more repetitions (.)
Yes
Statistics Descriptor
Octets sent
Yes
Octets received
Yes
Empty AuditDescriptor in Sub
Yes
Package Descriptor
Yes
7.1.17
User's Manual
Observed Events Descriptor
528
User's Manual

Reference
Item
(in RFC 3015)
7.1.18
Support
Request Identifier
Yes
Event
Yes
Detection Time
Yes
Comments
Topology Descriptor
Isolate
Yes
Oneway
Yes
Bothway
Yes
CHOOSE wildcard
Yes
ALL wildcard
Yes
7.2
Command API
7.2.1
Add
Termination ID
Yes
MediaDescriptor
Yes
ModemDescriptor
No
MuxDescriptor
No
EventsDescriptor
Yes
SignalsDescriptor
Yes
Only one signal per channel

Up to 30 signals in a signal
list
7.2.2
Version 4.8
DigitMapDescriptor
Yes
AuditDescriptor
Yes
Modify
Termination ID
Yes
MediaDescriptor
Yes
ModemDescriptor
No
MuxDescriptor
No
EventsDescriptor
Yes
SignalsDescriptor
Yes
529

list
January 2006
Mediant 3000

Reference
Item
(in RFC 3015)
7.2.3
7.2.4
7.2.5
User's Manual
Support
DigitMapDescriptor
Yes
AuditDescriptor
Yes
Comments
Subtract
Termination ID
Yes
AuditDescriptor
Yes
Statistical Parameters return
Yes
Move
Termination ID
Yes
MediaDescriptor
Yes
ModemDescriptor
No
MuxDescriptor
No
EventsDescriptor
Yes
SignalsDescriptor
Yes
DigitMapDescriptor
Yes
AuditDescriptor
Yes

list
Audit Value
TerminationID
Yes
Wildcard
Yes
AuditDescriptor
Yes
Media
Yes
Modem
No
Mux
No
Event
Yes
Signal
Yes
DigitMap
Yes
ObservedEvents
Yes
EventBuffer
Yes
Statistics
Yes
Packages
Yes
530
User's Manual

Reference
Item
(in RFC 3015)
7.2.6
7.2.7
Support
Comments
Audit Capabilities
TerminationID
Yes
Wildcard
Yes
AuditDescriptor
Yes
Media
Yes
Modem
No
Mux
No
Event
Yes
Signal
Yes
DigitMap
Yes
ObservedEvents
Yes
EventBuffer
Yes
Statistics
Yes
Packages
Yes
Notify
Yes
7.2.8
Service Change
Termination ID
Yes
Wildcard
Yes
Root Termination
Yes
ServiceChangeMethod
Version 4.8
Graceful
Yes
Forced
Yes
Restart
Yes
Disconnected
Yes
Handoff
Yes
Failover
Yes
Extension
No
531
This method can be used

only for the whole gateway
(ROOT termination), and
only when sent from the
gateway to the MGC
January 2006
Mediant 3000

Reference
Item
(in RFC 3015)
Support
Comments
ServiceChangeReason
7.2.9
900 Service Restored
Yes
901 Cold Boot
Yes
902 Warm Boot
No
903 MGC Direct Change
Yes
904 Termination Malfunctioning
No
905 Term Taken out of Service
Yes
906 Loss of lower layer connectivity
Yes
907 Transmission Failure
Yes
908 MG Impending Failure
No
909 MGC Impending Failure
No
910 Media Capability Failure
No
911 Modem Capability Failure
No
912 Mux Capability Failure
No
913 Signal Capability Failure
No
914 Event Capability Failure
No
915 State Loss
No
ServiceChangeDelay
No
ServiceChangeAddress
Yes
ServiceChangeProfile
Yes
ServiceChangeVersion
Yes
ServiceChangeMgcId
Yes
TimeStamp
Yes
Manipulating and Auditing Context

Attributes
Yes
7.2.10
7.3
Generic Command Syntax

Text Encoding
Yes
Binary Encoding
Yes
Command Error
400 - Bad Request
User's Manual
Yes
532
User's Manual

Reference
Item
(in RFC 3015)
Version 4.8
Support
401 - Protocol Error
Yes
402 - Unauthorized
Yes
403 - Syntax Error in Transaction
Yes
404 - Syntax Error in TransactionReply
Yes
405 - Syntax Error in

TransactionPending
Yes
406 - Version not Supported
No
410 - Incorrect Identifier
Yes
411 - Unknown ContextId
Yes
412 - No ContextId Available
Yes
421 - Unknown Action
Yes
422 - Syntax Error In Action
Yes
430 - Unknown TerminationId
Yes
431 - No TerminationId Matched a

Wildcard
Yes
432 - Out of Termination Id / No

TerminationId Available
Yes
433 - TerminationId is already in a

context
Yes
440 - Unsupported or unknown

Package
Yes
441 - Missing RemoteDescriptor
Yes
442 - Syntax Error in Command
Yes

Command
Yes

Descriptor
Yes

Property
Yes

Parameter
Yes
447 - Descriptor not legal in this

command
Yes
448 - Descriptor appears twice in a

command
Yes
450 - No such property in this package
Yes
533
Comments
January 2006
Mediant 3000

Reference
Item
(in RFC 3015)
User's Manual
Support
451 - No such event in this package
Yes
452 - No such signal in this package
Yes
453 - No such statistic in this package
Yes
454 - No such parameter value in this

package
Yes
455 - Parameter illegal in this

Descriptor
Yes
456 - Parameter or Property appears

twice in this Descriptor
Yes
471 - Implied Add for Multiplex failure
Yes
500 - Internal Gateway Error
Yes
501 - Not Implemented
Yes
502 - Not ready
Yes
503 - Service Unavailable
Yes
504 - Command Received from

unauthorized entity
No
505 - Command Received before

Restart Response
Yes
510 - Insufficient resources
Yes
512 - Media Gateway unequipped to

detect requested Event
Yes
513 - Media Gateway unequipped to

generate requested Signals
Yes
514 - MG cannot send the specified

announcement
Yes
515 - Unsupported Media Type
Yes
517 - Unsupported or Invalid Mode
Yes
518 - Event Buffer Full
Yes
519 - Out Of Space To Store Digit Map
Yes
520 - Media Gateway does not have a

digit map
Yes
521 - Termination is Service

Changing
No
526 - Insufficient Bandwidth
No
529 - Internal Hardware Failure
No
534
Comments
User's Manual

Reference
Item
(in RFC 3015)
530 - Temporary Hardware Failure
No
531 - Permanent Network Failure
No
540 - Unexpected Initial hook state
Yes
581 - Does not Exist
Yes
8.
Transactions
8.1
Common Parameters
8.1.1
Transaction Identifiers
8.1.2
Support
TransactionID
Yes
Use of TransactionId 0
Yes
Context Identifiers
ContextID
Yes
CHOOSE Wildcard
Yes
All Wildcard
Yes
8.2
Transaction API
8.2.1
Transaction Request
Multiple actions per request
8.2.2
Yes
Transaction Reply
Multiple actions per reply
8.2.3
8.3
9.1
Comments
Yes
Transaction Pending
Transaction Pending Support
Yes
normalMGEcecutionTime
Yes
normalMGCEcecutionTime
Yes
Messages
Receive Messages
Yes
Send Messages
Yes
Transport
Transport over UDP
Yes
Transport over TCP
Yes
Ordering of Commands
Yes
Version 4.8
535
January 2006
Mediant 3000

Reference
Item
(in RFC 3015)
9.2
10
Support
Comments
Protection Against the Restart Avalanche

Use of default MWD per platform
No
Random restart delay
Yes
Random seed selection
Yes
Detection of local activity
No
Security Considerations
No
11
MG-MGC Control Interface
11.1
Multiple Virtual Gateways

No
11.2
11.3
Not supported, however,

receiving commands from
more than one MGC and
sending notification to the
MGC which requested it is
supported.
Cold Start
Primary Call Agent support
Yes
Secondary Call Agents support
Yes
Cyclic check for Call Agent
Yes
Negotiation of Protocol Version

No
11.4
Failure of an MG
No
11.5
Failure of an MGC
Yes
User's Manual
536
User's Manual
25
25. Advanced Announcement Packages - Compliance Tables (MEGACO & MGCP)
Advanced Announcement Packages Compliance Tables (MEGACO & MGCP)

There are two MEGACO related compliance tables relevant for the advanced
announcement packages.
H.248.9 Compliance Matrix - summarize the supported H.248.9 features

respectively refer to the table below.
H.248.9 Compliance Matrix - TD-51 - is an earlier draft (refer to ''H.248.9

Compliance Matrix'' on page 542)
One MGCP reltated compliance table relevant for the advanced announcement
packages.
PacketCable Audio Server Protocol Specification PKT-SP-ASP-I02-010620

ANN-2 Interface (refer to ''PacketCable Audio Server Protocol Specification'' on
page 547)
25.1
H.248.9 Compliance Matrix
25.1.1
Advanced Audio Server Base Package (aasb)

Table 25-1: Events (aasb)
Events
Event Name
Symbol
Supported
Audio operation failure
audfail
Yes
Table 25-2: Audio Operartion Failure Event Parameters (aasb)

Audio Operartion Failure Event Parameters
Parameter
Name
Supported
rc
Return Code
Yes
Version 4.8
537
January 2006
Mediant 3000
Table 25-3: Signals (aasb)

Signals
Signal Name
Symbol
Supported
Play
Play
Yes
Table 25-4: Play Announcement Signal Parameters (aasb)

Play Announcement Signal Parameters
Parameter
Name
Supported
an
Announcement
Yes
it
Iteration
Yes
iv
Interval
Yes
sp
Speed
No
vl
Volume
No
25.1.2
AAS Digit Collection Package (aasdc) Extends Aasb Package

Table 25-5: Events (aasdc)
Events
Event Name
Symbol
Supported
Play collect success
Pcolsucc
Yes
Table 25-6: Play Collect Success Event Parameters (aasdc)

Play Collect Success Event Parameters
Parameter
Name
Supported
dc
Digits collected
Yes
na
Number Of Attempts
Yes
ap
Amount played
No (Will be supported in later

release)
User's Manual
538
User's Manual
Table 25-7: Signals (aasdc)

Signals
Signal Name
Symbol
Supported
Play Collect
playcol
Yes
Table 25-8: Play Collect Signal Parameters (aasdc)

Play Collect Signal Parameters
Parameter
Name
Supported
ip
Initial Prompt
Yes
rp
Reprompt
Yes
nd
NoDigitsPrompt
Yes
sa
Success Announcement
Yes
fa
Failure Announcement
Yes
ni
Non Interruptible Play
Yes
kdg
Keep Digits
Yes
cb
Clear Didigt Buffer

release)
mxatt
Max Attempts
Yes
dm
Digit Map
Yes
sp
Speed
No
vl
Volume
No
off
Offset
No
rsk
Restart Key
Yes
rik
Reinput Key
Yes
rtk
Return Key
Yes
Version 4.8
539
January 2006
Mediant 3000
25.1.3
AAS Digit Collection Package (aasrec) Extends aasb Package

Table 25-9: Properties (aasrec)
Properties
Property Name
Symbol
Supported
Maximum temporary record life
Maxtrl
No
Table 25-10: Events (aasrec)

Events
Event Name
Symbol
Supported
Play record success
Precsucc
Yes
Table 25-11: Play Record Success Event Parameters (aasrec)

Play Record Success Event Parameters
Parameter
Name
Supported
ap
Amount played
Yes
na
Number Of Attempts
Yes
res
Recording result
No
ri
Recording Id
No
rdur
Recording duration
No
Table 25-12: Signals (aasrec)

Signals
Signal Name
Symbol
Supported
Play Record
playrec
Yes
Make persistent
makepers
No
User's Manual
540
User's Manual
Table 25-13: Play Record Signal Parameters (aasrec)

Play Record Signal Parameters
Parameter
Name
Supported
ip
Initial Prompt
Yes
ns
NoSpeechPrompt
Yes
sa
Yes
fa
Yes
mxatt
Max Attempts
Yes
prt
Pre Speech Timer
Yes
pst
Post Speech Timer
Yes
rlt
Record Length Timer
Yes
Rid
Record Identifier
Yes (Note that support for the use of

the $ wildcard for the rid parameter is
not provided, but support is provided for
specifying specific remote URLs.)
sp
Speed
No
vl
Volume
No
off
Offset
No
rsk
Restart Key
Yes
rik
Reinput Key
Yes
rtk
Return Key
Yes
25.1.4
Adanced Audio Server Segment Management Package

(aassm)
This package is not supported.
Version 4.8
541
January 2006
Mediant 3000
25.2
H.248.9 Compliance Matrix - TD-51 (Early Draft)
25.2.1
Advanced Audio Server Base Package (aasb) (Early Draft)

Table 25-14: Events (aasb) (Early Draft)
Events
Event Name
Symbol
Supported
Audio operation complete
audcomp
Yes
Audio operation failure
audfail
Yes
Table 25-15: Audio Operation Complete Event Parameters (aasb) (Early Draft)
Audio Operation Complete Event Parameters
Parameter
Name
Supported
ap
Amount played

release)
na
Number Of Attempts
Yes
dc
Digits collected
Yes
ri
Recording id
No
Table 25-16: Audio Operation Failure Event Parameters (aasb) (Early Draft)
Audio Operation Failure Event Parameters
Parameter
Name
Supported
rc
Return Code
Yes
na
Number Of Attempts
Yes
ap
Amount played
Yes (supported only with Play

Record signal)
ri
Recording id
No
User's Manual
542
User's Manual
Table 25-17: Signals (aasb) (Early Draft)

Signals
Signal Name
Symbol
Supported
Play
play
Yes
Play Collect
playcoll
Yes
Play Record
layrec
Yes
Make persistent
makepers
No
Delete persisten
delpers
No
Table 25-18: Play Announcement Signal Parameters (aasb) (Early Draft)

Play Announcement Signal Parameters
Parameter
Name
Supported
an
Announcement
Yes
ni
Yes
it
Iteration
Yes
iv
Interval
Yes
sp
Speed
No
vl
Volume
No
Table 25-19: Play Collect Signal Parameters (aasb) (Early Draft)

Parameter
Name
Supported
Ip
Initial Prompt
Yes
rp
Reprompt
Yes
nd
NoDigitsPrompt
Yes
sa
Yes
fa
Yes
ni
Yes
kdg
Keep Digits
Yes
cb
Clear Didigt Buffer

release)
Version 4.8
543
January 2006
Mediant 3000
Table 25-19: Play Collect Signal Parameters (aasb) (Early Draft)

mxatt
Max Attempts
Yes
dm
Digit Map
Yes
sp
Speed
No
vl
Volume
No
off
Offset
No
rsk
Restart Key
Yes
rik
Reinput Key
Yes
rtk
Return Key
Yes
Table 25-20: Play Record Signal Parameters (aasb) (Early Draft)

Play Record Signal Parameters
Parameter
Name
Supported
ip
Initial Prompt
Yes
rp
Reprompt
Yes
ns
NoSpeechPrompt
Yes
sa
Yes
fa
Yes
ni
No (behavue as ni=false)
cdb
Clear Digit Buffer
No
prt
Pre Speech Timer
Yes
pst
Post Speech Timer
Yes
rlt
Record Length Timer
Yes
rid
Record Identifier
Yes (Note that support for the use of

the $ wildcard for the rid parameter is
not provided, but support is provided for
specifying specific remote URLs.)
sp
Speed
No
vl
Volume
No
off
Offset
No
rsk
Restart Key
Yes
rik
Reinput Key
Yes
rtk
Return Key
Yes
User's Manual
544
User's Manual
25.2.2
Advanced Audio Server Set Package (aass)

This package is fully supported.
25.2.3
Advanced Audio Server Override Package (aas0)

This package is not supported.
25.2.4
Segment Description Matrix

Table 25-21: Supported Segment Descriptor Elements
Segment Descriptor Element
Supported
http:/localhost/ URI
Yes
http:/ URI
Yes
file:// URI
No
ftp:// URI
No
standalone variables
Yes
embedded variables
Yes
Table 25-22: Segment Descriptor Variables

Variables
Name(TD51/H.2489)
Subtype
Definition
Supported
dat/date
Note The dat variable

does not support subtypes
for date. However, if a
subtype is specified in the
play request it will be
gracefully ignored and will
instead produce a date
announcement according to
the rules of each supported
language.
Date
Yes
mdy
Month-Day-Year
No (see note above)
dym
Day-Year-Month
No (see note above)
Digits
Yes
gen
Generic
Yes
ndn
North American
Yes(Only in TD-51)
dig/digits
Version 4.8
545
January 2006
Mediant 3000
Table 25-22: Segment Descriptor Variables

Variables
DN
dur
none
Duration
Yes
mth/month
none
Month
Yes
mny/money
<ISO 4217 three letter

codes>
Money
Yes
Number
Yes
crd
Cardinal
Yes
ord
Ordinal
Yes
sil
none
Silence
Yes
str/chars
none
String
Yes
Time
Yes
t12
Twelve hour
format
Yes
t24
Twenty four hour Yes

format
none
Weekday
num/int
tme/tod
wkd/dow
Yes
Note: http://URI is to be implemented in the next applicable release.
User's Manual
546
User's Manual
25.3
PacketCable Audio Server Protocol

Specification PKT-SP-ASP-I02-010620 ANN-2
Interface
25.3.1
Base Audio Package

Table 25-23: Events
Event Name
Symbol
Supported
PlayAnnouncement
pa
Yes
PlayCollect
pc
Yes
PlayRecord
pr
Yes
ManageAudio
ma
No
OperationComplete
oc
Yes
OperationFailed
of
Yes
Table 25-24: PlayAnnouncement Parameters

Parameter
Name
Type
Supported
an
announcement
input
Yes
du
duration
input
No (to be supported in a next

applicable release)
it
iterations
input
Yes
iv
interval
input
Yes
off
offset
input
Yes
sp
speed
input
No
vl
volume
input
No
rc
return code
output
Yes
Table 25-25: PlayCollect Parameters

Parameter
Name
Type
Supported
cb
clear digit buffer
input
No (to be supported in a
future release)
dm
digit map
input
Yes
Version 4.8
547
January 2006
Mediant 3000
Table 25-25: PlayCollect Parameters

Parameter
Name
Type
Supported
edt
extra digit timer
input
Yes
fa
failure announcement
input
Yes
fdt
first digit timer
input
Yes
ict
inter digit critical timer
input
Yes
idt
inter digit timer
input
Yes
ip
initial prompt
input
Yes
na
number of attempts
input
Yes
nd
no digits reprompt
input
Yes
ni
non-interruptible play
input
Yes
off
offset
input
No
rik
reinput key
input
Yes
rp
reprompt
input
Yes
rsk
restart key
input
Yes
rtk
return key
input
Yes
sa
success announcement
input
Yes
sp
speed
input
No
vl
volume
input
No
ap
amount played
output;
No
mandatory if prompt
interrupted;
otherwise forbidden
dc
digits collected
output
Yes
na
number of attempts
output;
Yes
mandatory
rc
return code
output
Yes
Table 25-26: PlayRecord Parameters

Parameter
Name
Type
Supported
ap
append
input;
Yes
mandatory if prompt
interrupted;
otherwise forbidden
dm
User's Manual
digit map
input
548
No
User's Manual
Table 25-26: PlayRecord Parameters

Parameter
Name
Type
Supported
fa
failure announcement
input
Yes
ict
inter digit critical timer
input
Yes
idt
inter digit timer
input
Yes
ip
initial prompt
input
Yes
na
number of attempts
input
Yes
ni
non-interruptible play
input
Yes
ns
no speech reprompt
input
Yes
off
offset
input
No
prt
prespeech timer
input
Yes
pst
postspeech timer
input
Yes
rid
recording id
input;
Yes (Note that support for

the use of the '$' wildcard
for the rid parameter is not
provided, but support is
provided for specifying
specific URLs.)
mandatory
rik
reinput key
input
Yes
rlt
recording length timer
input;
Yes
mandatory
rp
reprompt
input
Yes
rsk
restart key
input
Yes
rtk
return key
input
Yes
sa
success announcement
input
Yes
sp
speed
input
No
vl
volume
input
No
ap
amount played
output;
Yes
mandatory if prompt
interrupted;
otherwise forbidden
dc
digits collected
output
Yes
na
number of attempts
output;
Yes
mandatory
rc
Version 4.8
return code
output
549
Yes
January 2006
Mediant 3000
Table 25-27: ManageAudio Parameters

Parameter
Name
Type
Supported
dpa
delete persistent audio
input
No (Signal is not supported)
rpa
record persistent audio
input
No (Signal not supported)
rc
return code
output
Table 25-28: Segment Descriptor Elements

Segment Descriptor Element
Supported
http:/localhost/ URI
Yes
http:/ URI
Yes
file:// URI
No
ftp:// URI
No
standalone variables
Yes
embedded variables
Yes
Table 25-29: Variables

Name/Type
Subtype
Definition
dat
Note - The 'dat' variable does

Date
not support subtypes for date.
However, if a subtype is
specified in the play request it
will be gracefully ignored and will
instead produce a date
announcement according to the
rules of each supported
language.
Supported
mdy
Month-Day-Year
No (see note above)
dym
Day-Year-Month
No (see note above)
dig
Digits
gen
Generic
Yes
ndn
North American DN
Yes
dur
none
Duration
Yes
mth
none
Month
Yes
mny
<ISO 4217 three letter codes>
Money
Yes
num
User's Manual
Number
550
User's Manual
Table 25-29: Variables

Name/Type
Subtype
Definition
Supported
crd
Cardinal
Yes
ord
Ordinal
Yes
sil
none
Silence
Yes
str
none
String
Yes
tme
wkd
25.3.2
Time
t12
Twelve hour format
Yes
t24
Twenty four hour

format
Yes
none
Weekday
Yes
Advanced Audio Package

Package Name: AAU
The Advanced Audio Package supports all the features of the Basic Audio Package,
as detailed above. In addition, it supports the following:
Table 25-30: Set Capability

Set Capability
Supported
Set capability fully supported
Yes
User defined selectors and values
Yes
Predefined language selector: "lang"
Yes
ISO 639-2 language codes for language selector values
Yes
Selector and value encoding in query part of URL
Yes
Set elements containing multiple variables. Variables must appear in

the same order for all elements.
Yes
Table 25-31: ManageAudio Parameters

Parameter
Name
Type
Supported
oa
override persistent audio
input
No (Signal is not supported)
ra
restore persistent audio
input
Version 4.8
551
January 2006
User's Manual
26
26. Appendix - Getting Started with VLANs and Multiple IPs
Appendix - Getting Started with VLANs

and Multiple IPs
By default the Mediant 3000 operates without VLANs and multiple IPs, using a single
IP address, subnet mask and default gateway IP address. This section provides an
example of the configuration required to integrate the Mediant 3000 into a VLAN and
multiple IPs network using the Embedded Web Server and ini file. The table below
shows an example configuration that is implemented in the following sections.
Table 26-1: Example of VLAN and Multiple IPs Configuration

Network
Type
IP Address
Subnet Mask
Default
Gateway IP
Address
VLAN ID
External
Routing Rule
OAM
10.31.174.50
255.255.0.0
0.0.0.0
83.4.87.X
Control
10.32.174.50
255.255.0.0
0.0.0.0
130.33.4.6
Media
10.33.174.50
255.255.0.0
10.33.0.1
--
Note that since a default gateway is available only for the Media network, for the
Mediant 3000 to be able to communicate with an external device / network on its OAM
and Control networks, IP routing rules must be used.
Note: The values provided are sample parameters only and are to be replaced
with actual values appropriate to your system.
26.1.1
Integrating Using the Embedded Web Server

To integrate the MediaPack into a VLAN and Multiple IPs network
using the Embedded Web Server, take these 7 steps:
1.
Access the Embedded Web Server (Refer to 'Embedded Web Server' on page
202).
2.
Use the Software Upgrade Wizard to load and burn the firmware version to the
MediaPack (VLANs and multiple IPs support is available only when the firmware
is burned to flash).
3.
Configure the VLAN parameters by completing the following steps:
Version 4.8
Open the VLAN Settings screen (Advanced Configuration menu > Network
Settings > VLAN Settings option); the VLAN Settings screen is displayed.
553
January 2006
Mediant 3000
Modify the VLAN parameters to correspond to the values shown in the figure
below.
Figure 26-1: VLAN Settings Screen Example
4.
Click the Submit button to save your changes.
Configure the multiple IP parameters by completing the following steps:
Open the IP Settings screen (Advanced Configuration menu > Network

Settings > IP Settings option); the IP Settings screen is displayed.
Modify the IP parameters to correspond to the values shown in Figure 1-3

below. Note that the OAM, Control and Media Network Settings parameters
appear only after you select the option Multiple IP Networks in the field IP
Networking Mode.
Note: Configure the OAM parameters only if the OAM networking parameters are
different from the networking parameters used in the Single IP Network
mode.
Figure 26-2: IP Settings Screen Example
User's Manual
554
User's Manual
5.
Configure the IP Routing table by completing the following steps (the IP Routing
table is required to define static routing rules for the OAM and Control networks
since a default gateway isnt supported for these networks):
Open the IP Routing Table screen (Advanced Configuration menu >

Network Settings > IP Routing Table option); the IP Routing Table screen is
displayed.
Figure 26-3: IP Routing table Screen Example
Use the Add a new table entry pane to add the routing rules shown in the
table below.
Table 26-2: Example of IP Routing Table Configuration

Destination IP
Address
Destination Mask
Gateway IP
Address
Hop Count
Network Type
130.33.4.6
255.255.255.255
10.32.0.1
20
Control
83.4.87.6
255.255.255.0
10.31.0.1
20
OAM
26.1.2
6.
Save your changes to flash so they are available after a power fail.
7.
Reset the gateway. Click the Reset button on the main menu bar; the Reset
screen is displayed. Click the button Reset.
Integrating Using the ini File

To integrate the MediaPack into a VLAN and multiple IPs network
using the ini file, take these 3 steps:
1.
Version 4.8
Prepare an ini file with parameters shown in the figure below (refer to the
following notes):
If the BootP/TFTP utility and the OAM interface are located in the same
network, the Native VLAN ID (VlanNativeVlanId) must be equal to the OAM
VLAN ID (VlanOamVlanId), which in turn must be equal to the PVID of the
switch port the gateway is connected to. Therefore, set the PVID of the
switch port to 4 (in this example).
Configure the OAM parameters (LocalOAMPAddress,

555
January 2006
Mediant 3000
LocalOAMSubnetMask and LocalOAMDefaultGW) only if the OAM
networking parameters are different from the networking parameters used in
the Single IP Network mode.
The IP Routing table is required to define static routing rules for the OAM
and Control networks since a default gateway isnt supported for these
networks
Example of VLAN and Multiple IPs ini File Parameters

; VLAN Configuration
VlanMode=1
VlanOamVlanId=4
VlanNativeVlanId=4
VlanControlVlanId=5
Vlanmediavlanid=6
; Multiple IPs Configuration
EnableMultipleIPs=1
LocalMediaIPAddress=10.33.174.50
LocalMediaSubnetMask=255.255.0.0
LocalMediaDefaultGW=10.33.0.1
LocalControlIPAddress=10.32.174.50
LocalControlSubnetMask=255.255.0.0
LocalControlDefaultGW=0.0.0.0
LocalOAMPAddress=10.31.174.50
LocalOAMSubnetMask=255.255.0.0
LocalOAMDefaultGW=0.0.0.0
; IP Routing table parameters
RoutingTableDestinationsColumn = 130.33.4.6, 83.4.87.6
RoutingTableDestinationMasksColumn = 255.255.255.255 ,
255.255.255.0
RoutingTableGatewaysColumn = 10.32.0.1 , 10.31.0.1
RoutingTableInterfacesColumn = 1 , 0
RoutingTableHopsCountColumn = 20,2
26.2
2.
Use the BootP/TFTP utility to load and burn (-fb option) the firmware version and
the ini file you prepared in the previous step to the MediaPack (VLANs and
multiple IPs support is available only when the firmware is burned to flash).
3.
Reset the MediaPack after disabling it on the BootP/TFTP utility.
Basic Setup
By default the Mediant 3000 works without VLANs and IP separation. To enable these
features, the enable parameter should be entered via the ini file, together with the set
of parameters that are needed for correct Mediant 3000 operation (i.e. set of IP
addresses, set of VLAN IDs, etc.) After the updated ini file is saved and loaded to the
non-volatile flash memory on the Mediant 3000, the Mediant 3000 must be reset. The
updated configuration, which includes the updated settings to enable VLANS and
multiple IP address is implemented.
26.3
Setup Example
The configuration directions in this appendix utilizes the sample parameters detailed in
this section.
Using default values, the Mediant 3000 currently works in single IP mode with
parameters acquiring from its BootP server. The following are sample parameters
acquired from the BootP server:
User's Manual
556
User's Manual
26.4
IP = 10.31.174.50
Subnet = 255.255.0.0
Default gateway = 10.31.10.1
Preparing the Mediant 3000 for VLANs and

Multiple IPs (MI)
To illustrate how to prepare for VLANS and Multiple IPs (MI), two examples are
detailed in this section.
Example 1 - The Mediant 3000 is to communicate with an external device whose IP
address is 130.33.4.6 via the internal Call-Control network
Example 2 - The Mediant 3000 is to communicate with an external network whose IP
address is 83.4.87.X via the internal OAM network.
In both of these examples the hop count routing parameter is 20. Since these internal
networks can not be configured with default gateways, static routes are needed.
To prepare the Mediant 3000 for Multiple IPs (MI) and VLANs, take
these 10 steps:
1.
Ascertain values for the following parameters:
Note: The values provided are sample parameters only and are to be replaced
with actual values appropriate to your system.
OAM network:
IP/Subnet/GW = 10.31.174.50 / 255.255.0.0 / 0.0.0.0
VLAN ID = 4
Call Control network:
IP/Subnet/GW = 10.32.174.50 / 255.255.0.0 / 0.0.0.0
VLAN ID = 5
Media network:
IP/Subnet/GW = 10.33.174.50 / 255.255.0.0 / 10.33.0.1
VLAN id = 6
Note: The board is configured only with one default gateway on the media
network. Additional routes can be configured statically by
WEB/SNMP/TPNCP and even via the ini file.
1.
In the ini file, set the VLAN parameters.

a.
Version 4.8
If the BootP/TFTP to be on the same network as the operational OAM

network, the Native VLAN parameter is equal to the OAM VLAN (both equal
to the PVID of the switch port the board to which it is connected). According
to the sample parameters in this example (see above), the OAM Network
557
January 2006
Mediant 3000
VLAN ID = 4. The following is an example of the VLAN parameters in the ini
file with values according to the sample parameters above:
vlanOamVlanId=4
vlanNativeVlanId=4
b.
In the switch port, configure the PVID = 4.
c.
Set the Call Control network VLAN ID and Media network VLAN ID.
According to the sample parameters in this example (see above), the Call
Control network VLAN ID = 5 and the Media network VLAN ID = 6 . The
following is an example of these parameters in the ini file with values
according to the sample parameters above:
vlanControlVlanId=5
vlanMediaVlanId=6
d.
Set the vlanMode parameter to 1. The following is an example of this

parameter in the ini file:
vlanMode=1
2.
In the ini file, set the Multiple IP parameters.
3.
In the ini file, configure the Local Media and Call-Control parameters. The
following is an example of these parameters in the ini file with values according
to the sample parameters above:
LocalMediaIPAddress=10.33.174.50
LocalMediaSubnetMask=255.255.0.0
LocalMediaDefaultGW=10.33.0.1
LocalControlIPAddress=10.32.174.50
LocalControlSubnetMask=255.255.0.0
LocalControlDefaultGW=0.0.0.0
Note: More than one interface can not be configured on the same network.
4.
Set the required static routes. The table below displays the Routing Table Rules
according to the sample parameters in the example 1 and 2 as mentioned above.
Table 26-3: Routing Table Rules

Destination
Subnet Mask
Gateway
Hops Count
Network
130.33.4.6
255.255.255.255
10.32.0.1
20
Call-Control
83.4.87.6
255.255.255.0
10.31.0.1
20
OAM
User's Manual
558
User's Manual
The interface networks are designated as follows:

0-OAM
1-Call Control
2-Media
According to the sample parameters shown in the table above, the Routing table in the
ini file appears like this:
The following is an example of the Routing Table parameters
(according to the sample parameters shown in the table above) in
the ini file:
RoutingTableDestinationsColumn = 130.33.4.6, 83.4.87.6
RoutingTableDestinationMasksColumn = 255.255.255.255 ,
255.255.255.0
RoutingTableGatewaysColumn = 10.32.0.1 , 10.31.0.1
RoutingTableInterfacesColumn = 1 , 0
RoutingTableHopsCountColumn = 20,20
Each row of these parameters in the ini file is a column in the table of Routing Table
Rules.
5.
Set the EnableMultipleIPs parameter to 1. The following is an example of this

parameter in the ini file:
EnableMultipleIPs=1
26.5
6.
Save the changes to the ini file.
7.
If your Mediant 3000 is using a software version earlier than 4.6, use BootP to
burn the updated cmp version to the non -volatile flash memory (-fb option in the
BootP application).
8.
Reset the Mediant 3000. The updated ini file is implemented. The board has all
the required information to enable the advanced VLAN and IP separation
features.
9.
To re-establish its network infrastructure, reset the Mediant 3000 again.
Verifying the VLANS and Multiple IP Settings

Using the Embedded Web Server
For details on using the Embedded Web Server, refer to ''Embedded Web Server'' on
page 202.
Version 4.8
559
January 2006
Mediant 3000
To verify the VLANS and Multiple IP settings using the Embedded

Web Server, take there 3 steps:
1.
In the Embedded Web Server, access the IP Setting screen (Advanced

Configuration->Network Settings->IP Settings).
Figure 26-4: IP Settings Screen Example
2.
Access the Routing Table screen (Advanced Configuration->Network Settings>Routing Table):

Figure 26-5: Routing Table Screen
3.
Access the VLAN Settings screen (Advanced Configuration->Network Settings>VLAN Settings):

Figure 26-6: VLAN Settings screen
User's Manual
560
User's Manual
26.6
OAM Parameters
If the your network architecture requires the OAM network settings be different than
the parameter values acquired in the BootP process, you must set the local OAM
configuration line in the ini file to the required parameters. The example below shows
the form of these parameter settings using the following sample parameter values:
OAM network:
IP/Subnet/GW = 10.34.174.50 / 255.255.0.0 / 0.0.0.0
VLAN ID = 7
To set the local OAM configuration, take these 4 steps:

1.
In the ini file, set the local OAM configuration line similar to the following:
LocalOAMIPAddress=10.34.174.50
LocalOAMSubnetMask=255.255.0.0
LocalOAMDefaultGW=0.0.0.0
2.
In the ini file, change the OAM VLAN tag line to:
vlanOamVlanId=7
26.7
3.
Save the changes to the ini file and load it to the Mediant 3000.
4.
Reset the Mediant 3000. The updated ini file is implemented. The board has all
the required information to enable the OAM parameters.
MI and VLAN Parameters

The following table lists the Multiple IP parameters.
Table 26-4: Multiple IP Parameters

Parameter Name
Default Value
Comments
EnableMultipleIPs
When burned in the flash, the board will try

to initialize multiple IPs feature in
subsequent boots.
LocalMediaIPAddress
0.0.0.0
The source address of the board in the

Media network
LocalMediaSubnetMask
0.0.0.0
The subnet applied to the board in the

Media network
LocalMediaDefaultGW
0.0.0.0
The default gateway in the Media network
LocalControlIPAddress
0.0.0.0
Version 4.8
561
January 2006
Mediant 3000
Table 26-4: Multiple IP Parameters

Parameter Name
Default Value
Comments
Control network
LocalControlSubnetMask
0.0.0.0

Control network
LocalControlDefaultGW
0.0.0.0
The default gateway in the Control network

(currently not in use)
LocalOAMIPAddress
0.0.0.0

OAM network
LocalOAMSubnetMask
0.0.0.0

OAM network
LocalOAMDefaultGW
0.0.0.0
The default gateway in the OAM network

(currently not in use)
The following table lists the VLAN parameters.
Table 26-5: VLAN Parameters

Parameter Name
Default Value
Comments
vlanMode
When burned in the flash, the board will try

to initialize VLANs feature in subsequent
boots.
vlanNativeVlanId
The PVID of the switch port which the

board connected to.
vlanOamVlanId
The VLAN Identifier of the OAM.
vlanControlVlanId
The VLAN Identifier of the Control.
vlanMediaVlanId
The VLAN Identifier of the Media.
vlanSendNonTaggedOnNative
Specifies whether to send non-tagged

packets on the native vlan
vlanNetworkServiceClassPriority
Sets the priority for the Network service

class content
vlanPremiumServiceClassMediaPri
ority
Sets the priority for the Premium service

class content and media traffic
vlanPremiumServiceClassControlP
riority
Sets the priority for the Premium service

class content and control traffic
vlanGoldServiceClassPriority
Sets the priority for the Gold service class

content
vlanBronzeServiceClassPriority
Sets the priority for the Bronze service

class content
NetworkServiceClassDiffServ
48
Sets the DiffServ for the Network service
User's Manual
562
User's Manual
Table 26-5: VLAN Parameters

Parameter Name
Default Value
Comments
class content
PremiumServiceClassMediaDiffSer
v
46
Sets the DiffServ for the Premium service

class content and media traffic
PremiumServiceClassControlDiffS
erv
46
Sets the DiffServ for the Premium service

class content and control traffic
GoldServiceClassDiffServ
26
Sets the DiffServ for the Gold service class

content
BronzeServiceClassDiffServ
10
Sets the DiffServ for the Bronze service

class content
The following parameters are used for both the VLAN and MI features.
Table 26-6: Shared VLAN and MI Parameters

Parameter Name
EnableDNSasOAM
Default
Value
1
Range
Enable = 1
Disable = 0
Comments
For MI: If enabled, the DNS services
are on the OAM network. If disabled,
they are on the Control network
For VLANS: If enabled, the DNS
services are on the OAM VLAN. If
disabled, they are on the Control VLAN
EnableNTPasOAM
Enable = 1
Disable = 0
For MI: If enabled, NTP services are on

the OAM network. If disabled, they are
on the Control network
For VLANS: If enabled NTP services
are on the OAM VLAN. If disabled, they
are on the Control VLAN
EnableSCTPasControl
Enable = 1
Disable = 0
For MI: If enabled, SCTP services are

on the Control network. If disabled,
they are on the OAM network
For VLANS: If enabled, SCTP services
are on the Control VLAN. If disabled,
they are on the OAM VLAN.
EnableTPNCPasOAM
Enable = 1
Disable = 0
For MI: If enabled, TPNCP services are

on the OAM network. If disabled, they
are the Control network
For VLAN: If enabled, TPNCP services
are on the OAM VLAN. If disabled, they
Version 4.8
563
January 2006
Mediant 3000
Table 26-6: Shared VLAN and MI Parameters

Parameter Name
Default
Value
Range
Comments
are on the Control VLAN.
User's Manual
564
User's Manual
27. VoATM Related SDP Exchange Samples & Call Flows
27
VoATM Related SDP Exchange Samples

& Call Flows
27.1
Sample SDP Exchanges
27.2
for VoATM
The following SDP exchanges are provided as a reference for understanding the steps
necessary to establish a bearer path connection between the VoATM media server
(Node 1) and the remote gateway (Node 2).
27.2.1
AAL1
STEP 1: MGC sends the following SDP lines to node 1:
v=0
c=ATM NSAP $
m=audio - AAL1/ATMF 0
STEP 1A: returned from node 1:
v=0
o=- 1085487653 0 ATM NSAP
39.3456.7890.1234.5678.9012.3a7a.0090.8f04.aaae.00
s=c=ATM NSAP 39.3456.7890.1234.5678.9012.3a7a.0090.8f04.aaae.00
a=ptime:5
a=aalType:AAL1
a=eecid:02f00000
STEP 2: MGC sends the following SDP lines to node 2: (local + remote)
:
Local SDP
v=0
c=ATM NSAP $
Remote SDP
v=0
o=- 1085487653 0 ATM NSAP
39.3456.7890.1234.5678.9012.3a7a.0090.8f04.aaae.00
s=c=ATM NSAP 39.3456.7890.1234.5678.9012.3a7a.0090.8f04.aaae.00
a=eecid:02f00000
a=ptime:5
a=aalType:AAL1
STEP 2A: MGC receives the following SDP lines from node 2
Version 4.8
565
January 2006
Mediant 3000
:
v=0
o=- 1085502830 0 ATM - s=c=ATM NSAP 39.3456.7890.1234.5678.9012.3a7a.000e.2dc8.2118.01
a=ptime:5
a=aalType:AAL1
The following lines occur in parallel with STEP 2A and cosist of UNI Signalling
between Node 1 and Node 2:
Node 2 to Node 1:
UNI SETUP MESSAGE:
Includes information element called Generic Identifier Transport
Information Element (GIT IE)
The following lines may be before, in parallel with, or after STEP 3 depending upon
control messaging timing
:
Node 1 to Node 2:
UNI CONNECT MESSAGE:
The following lines may occur before, in parallel with, or after step 3.:
Node 2 to Node 1:
UNI CONNECT ACK MESSAGE:
:
STEP 3: MGC sends the followng SDP lines to node 1 (remote SDP)
v=0
o=- 1085502830 0 ATM - s=c=ATM NSAP 39.3456.7890.1234.5678.9012.3a7a.000e.2dc8.2118.01
a=ptime:5
a=aalType:AAL1
27.2.2
AAL2
The MGC sends SDP lines to the originating gateway (add). Note that no SDP is sent
down to the originating gateway.
MGC receives the following SDP lines from the originating gateway.
:
v=0
c=ATM NSAP 39.3456.7890.1234.5678.9012.3a7a.0020.480d.50b0.00
m=audio $/$ AAL2/ITU 2 1 AAL2/custom 200 100
User's Manual
566
User's Manual
MGC sends SDP lines to the VoATM media server.

:
Local SDP:
v=0
c=ATM NSAP $
m=audio $/$ AAL2/ITU 2 1 AAL2/custom 200
a=vsel:PCMU - Remote SDP:
v=0
c=ATM NSAP 39.3456.7890.1234.5678.9012.3a7a.0020.480d.50b0.00
m=audio $/$ AAL2/ITU 2 1 AAL2/custom 200 100
a=vsel:PCMU - -
Either here or just after the SDP is acknowledged, the VoATM media server sends a
UNI SETUP message to the originating gateway. The originating gateway blindly
accepts the SETUP and caches the data awaiting the control message, which
contains the VCCI info (contained in the SDP in the message below).
Once the VCCI is matched up (refer to the last message below) with the incoming VC
from the UNI SETUP, the voice path is cut through. Note that the most significant bit
of the most significant byte of the VCCI is flipped in both the UNI setup message and
also in the local SDP information. This indicates ownership in terms of which side (the
originating gatweay or the VoATM media server) established the VC.
A UNI CONNECT is sent back from the originating to the VoATM media server.
A UNI CONNECT ACK is sent from the VoATM media server to the originating
gateway.
SDP lines are returned from VoATM media server.
:
Local SDP returned:
v=0
c=ATM NSAP 39.3456.7890.1234.5678.9012.3a7a.0090.8f04.aaae.00
m=audio 15940/255 AAL2/ITU 2
a=vsel:PCMU - -
SDP lines are sent to originating gateway as part of the modify command (VCCI is
matched up):
v=0
c=ATM NSAP 39.3456.7890.1234.5678.9012.3a7a.0090.8f04.aaae.00
m=audio 15940/255 AAL2/ITU 2
a=vsel:PCMU - -
27.3
Call Flows
Call Flow scenarios are provided as a reference for understanding the overall
implementation.
Version 4.8
567
January 2006
Mediant 3000
27.3.1
Simple Announcement Call Over AAL1 SVC

In the following call flow, the MGC establishes an announcement from the TP-6310 to
the Remote Gateway over an AAL1 SVC.
27.3.1.1
Mediant 3000 as Master to the ATM Connection

In this scenario the Mediant 3000 is the Master of the AAL1 connection.
Figure 27-1: Remote Gateway H.248 AAL1 SVC Call Flow - 6310 Master
Remote Gateway
MGC
6310 Board
ADD()
ACK(AESA-1,eecid=B3D58E32)
ADD(AESA-1,eecid=B3D58E32)
ACK
UNI4.0 SETUP(eecid=B3D58E32)
UNI4.0 CONNECT
COAV(event)
COAV(event)
PLAY
User's Manual
568
User's Manual
27.3.1.2
Mediant 3000 as Slave to the ATM Connection

In this scenario the Mediant 3000 is the slave of the AAL1 connection.
Figure 27-2: Remote Gateway H.248 AAL1 SVC Call Flow - 6310 Slave
6310 Board
MGC
Remote Gateway
ADD()
ACK(AESA-1,eecid=B3D58E32)
ADD(AESA-1,eecid=B3D58E32)
ACK
UNI4.0 SETUP(eecid=B3D58E32)
UNI4.0 CONNECT
COAV(event)
COAV(event)
PLAY
Version 4.8
569
January 2006
Mediant 3000
27.3.2

In the following call flow, the MGC establishes an announcement from the Mediant
3000 to the Remote Gateway over an AAL2 SVC.
Figure 27-3: Remote Gateway H.248 AAL2 SVC Call Flow
MGC (6310
Board)
Remote
Gateway
6310 Board
MGC (Remote
Gateway)
CRCX
ACK (Partially Qualified SDP)

ADD (Audio Endpoint)
Return (Audio Endpoint)
ADD (Partially Qualified SDP)
Return (Fully Qualified SDP +
Ephemeral)
UNI4.0 SETUP(AESA, vcci)
UNI4.0 CONNECT
Modify (Play annc)
ACK (Modify annc Endpoint)
Modify (Fully Qualified
SDP,vcci)
ACK
Modify (Announcement
complete)
ACK
Delete (Endpoint)
ACK
Modify (No signals)
ACK
Subtract (Ephemerals/Audio
Endpoints)
ACK
User's Manual
570
User's Manual
28
28. Appendix - SNMP Traps
Appendix - SNMP Traps

This section provides information regarding proprietary traps currently supported in the
Mediant 3000. Note that traps whose purposes are alarms are different from traps
whose purposes are not alarms, e.g., logs.
Currently, all traps have the same structure, which is made up of the same 11
varbinds. An example is: 1.3.6.1.4.1.5003.9.10.1.21.1
The source varbind is made up of a string that details the component from which the
trap is being sent, forwarded by the hierarchy in which it resides. For example, an
alarm from an SS7 link has the following string in its source varbind:
acBoard#1/SS7#0/SS7Link#6
In this example, the SS7 link number is specified as 6 and is part of the only SS7
module in the device that is placed in slot number 1 (in a chassis) and is the module to
which this trap is related. For devices where there are no chassis options the slot
number of the board is always 1.
28.1
Alarm Traps
The following provides information relating to those alarms that are raised as the result
of a generated SNMP trap. The component name described within each of the
following section headings refers to the string that is provided in the
acBoardTrapGlobalsSource trap varbind. In all the following discussions, to clear a
generated alarm the same notification type is sent but with the severity set to cleared.
28.1.1
Component: Board#<n>
The source varbind text for all the alarms under the component below is System#0.
<n> is the slot number when the TP-6310 resides in a chassis.
1 = the slot number when the TP-6310 resides in a chassis.
Table 28-1: acBoardFatalError Alarm Trap

Alarm:
acBoardFatalError
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.1
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
underlyingResourceUnavailable (56)
Alarm Text:
Board Fatal Error: <text>
Status Changes:
Condition:
Any fatal error
Alarm status:
Critical
Version 4.8
571
January 2006
Mediant 3000
Table 28-1: acBoardFatalError Alarm Trap

Alarm:
acBoardFatalError
<text> value:
A run-time specific string describing the fatal error
Condition:
After fatal error
Alarm status:
Status stays critical until reboot. A clear trap is not sent.
Corrective Action:
Capture the alarm information and the syslog close, if active. Contact your
first-level support group. The support group will likely want to collect
additional data from the device and then perform a reset.
Table 28-2: acBoardConfigurationError Alarm Trap

Alarm:
acBoardConfigurationError
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.2
Default Severity
critical
Event Type:
equipmentAlarm
Probable Cause:
Alarm Text:
Board Config Error: <text>
Status Changes:
Condition:
A configuration error was detected
Alarm status:
critical
<text> value:
A run-time specific string describing the configuration error.
Condition:
After configuration error
Alarm status:
Corrective Action:
Inspect the run-time specific string to determine the nature of the

configuration error. Fix the configuration error using the appropriate tool:
web interface, EMS, or ini file. Save the configuration and if necessary
reset the device.
Note: The acBoardTemperatureAlarm alarm trap below does not apply to the High
Availability Mode.
User's Manual
572
User's Manual
Table 28-3: acBoardTemperatureAlarm Alarm Trap

Alarm:
acBoardTemperatureAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.3
Default Severity
critical
Event Type:
equipmentAlarm
Probable Cause:
temperatureUnacceptable (50)
Alarm Text:
Board temperature too high
Status Changes:
Condition:
Temperature is above 60 degrees C (140 degrees F)
Alarm status:
critical
Condition:
After raise, temperature falls below 55 degrees C (131 degrees F)
Alarm status:
cleared
Corrective Action:
Inspect the system. Determine if all fans in the system are properly
operating.
Table 28-4: acBoardEvResettingBoard Alarm Trap

Alarm:
acBoardEvResettingBoard
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.5
Default Severity
critical
Event Type:
equipmentAlarm
Probable Cause:
outOfService (71)
Alarm Text:
User resetting board
Status Changes:
Condition:
When a soft reset is triggered via either web interface or SNMP.
Alarm status:
critical
Condition:
After raise
Alarm status:
Corrective Action:
A network administrator has taken action to reset the device. No

corrective action is needed.
Version 4.8
573
January 2006
Mediant 3000
Table 28-5: acFeatureKeyError Alarm Trap

Alarm:
acFeatureKeyError
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.6
Default Severity
critical
Event Type:
processingErrorAlarm
Probable Cause:
configurationOrCustomizationError (7)
Alarm Text:
Feature key error
Status Changes:
This alarm's support is pending
Condition:
Alarm status:
Note:
28.1.2
This alarms support is pending
Component: Board#<n>
The source varbind text for all the alarms under the component below is System#0.
Table 28-6: acgwAdminStateChange Alarm Trap

Alarm:
acgwAdminStateChange
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.7
Default Severity
Major
Event Type:
Probable Cause:
outOfService (71)
Alarm Text:
Network element admin state change alarm Gateway is <text>
Status Changes:
Condition:
Admin state changed to shutting down
Alarm status:
Major
<text> value:
shutting down. No time limit.
Condition:
Admin state changed to locked
Alarm status:
Major
<text> value:
locked
User's Manual
574
User's Manual
Table 28-6: acgwAdminStateChange Alarm Trap

Alarm:
acgwAdminStateChange
Condition:
Admin state changed to unlocked
Alarm status:
cleared
Corrective Action:
A network administrator has taken an action to lock the device. No

corrective action is required.
Table 28-7: acOperationalStateChange Alarm Trap

Alarm:
acOperationalStateChange
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.15
Default Severity
Major
Event Type:
Probable Cause:
outOfService (71)
Alarm Text:
Network element operational state change alarm. Operational state is

disabled.
Note:
This alarm is raised if the operational state of the node goes to

disabled. The alarm is cleared when the operational state of the node
goes to enabled.
Status Changes:
Condition:
Operational state changed to disabled
Alarm status:
Major
Condition:
Operational state changed to enabled
Alarm status:
cleared
Note:
In both ATM and IP systems, the operational state of the node is

disabled if the device fails to properly initialize. In ATM systems, the
operational state of the node is also disabled if there are no ATM
ports available for use. An ATM port is available for use if it is
unlocked and enabled.
Corrective Action:
In ATM and IP systems, check for initialization errors. Look for other
alarms and syslogs that might provide additional information about the
error. In an ATM system, also check for ATM port status and alarms. If
any ATM ports are disabled, then attempt to bring them back into service.
The source varbind text for all the alarms under the component below is
System#0/AlarmManager#0.
Version 4.8
575
January 2006
Mediant 3000
Table 28-8: acActiveAlarmTableOverflow Alarm Trap

Alarm:
acActiveAlarmTableOverflow
OID:
1.3.6.1.4.15003.9.10.1.21.2.0.12
Default Severity
Major
Event Type:
Probable Cause:
resourceAtOrNearingCapacity (43)
Alarm Text:
Active alarm table overflow
Status Changes:
Condition:
Too many alarms to fit in the active alarm table
Alarm status:
Major
Condition:
After raise
Alarm status:
Status stays major until reboot. A clear trap is not sent.
Note:
The status stays major until reboot as it denotes a possible loss of

information until the next reboot. If an alarm was raised when the table
was full, it is possible that the alarm is active, but does not appear in the
active alarm table.
Corrective Action:
Some alarm information may have been lost, but the ability of the device to
perform its basic operations has not been impacted. A reboot is the only
way to completely clear a problem with the active alarm table. Contact
your first-level group.
Note: The acBoardTemperatureAlarm alarm trap below does not apply to the High
Availability Mode.
Board#<n>/AtmPort#<m> where n is the slot number, and m is the ATM port number.
Table 28-9: acAtmPortAlarm Alarm Trap

Alarm:
acAtmPortAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.13
Default Severity
Critical
User's Manual
576
User's Manual

Alarm:
acAtmPortAlarm
Event Type:
equipmentAlarm
Probable Cause:
adapterError (1)
Alarm Text:
ATM Port Alarm: port <number>, <text>
Status Changes:
Condition:
LOS condition is present
Alarm status:
critical
<text> value:
LOS
Note:
The alarmStatus field in the AtmPortTable will have a value of los(1).
Condition:
AIS condition is present (LOS condition is not present)
Alarm status:
Major
<text> value:
AIS
Note:
The alarmStatus field in the AtmPortTable will have a value of ais(2).
Condition:
RDI condition is present (LOS and AIS conditions are not present)
Alarm status:
Major
<text> value:
RDI
Note:
The alarmStatus field in the AtmPortTable will have a value of rdi(4).
Condition:
LOS, AIS, and RDI conditions are not present
Alarm status:
cleared
Note:
Alarm conditions (taken from the Sonet/SDH standards documents) are:

2 LOS Loss of Signal
2 AIS Alarm Indication Signal
2 RDI Remote Defect Indication
Version 4.8
577
January 2006
Mediant 3000

Alarm:
acAtmPortAlarm
Corrective Action:
Ensure that the fiber is plugged into appropriate port on the IPM-6310
Rear Transition Module (RTM) board of the system. Check to see if the
fiber has been damaged. Ensure that the network side of the fiber is
enabled and is on-line.
28.1.3
Component: SS7#0
System#0/SS7#0/SS7Link#<m> where m is the link number.
Table 28-10: acSS7LinkStateChangeAlarm Trap

Alarm:
acSS7LinkStateChangeAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.19
Default Severity
Major
Event Type:
communicationsAlarm
Probable Cause:
other
Alarm Text:
*** SS7 *** Link %i is %s $s
Status Changes:
Condition:
Operational state of the SS7 link becomes BUSY.
Alarm status:
Major
<text> value:
%i - <Link number>
%s - <state name>: { "OFFLINE", "BUSY", "INSERVICE"}
%s IF link has MTP3 layer, then this string equals:
(SP %i linkset %i slc %i)
Where:
%i - <SP number>
%i - <Link-Set number>
%i - <SLC number>
Otherwise there is NO additional text.
Additional Info1
varbid
BUSY
Condition:
Operational state of the link becomes IN-SERVICE or OFFLINE.
Alarm status:
cleared
User's Manual
578
User's Manual
Table 28-10: acSS7LinkStateChangeAlarm Trap

Alarm:
acSS7LinkStateChangeAlarm
Corrective Action:
For full details see the SS7 section and SS7 MTP2 and MTP3 relevant
standards.
Table 28-11: acSS7LinkInhibitStateChangeAlarm Trap

Alarm:
acSS7LinkInhibitStateChangeAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.20
Default Severity
Major
Event Type:
communicationsAlarm
Probable Cause:
other
Alarm Text:
*** SS7 *** Link %i (SP %i linkset %i slc %i) is %s
Status Changes:
Condition:
SS7 link becomes inhibited (local or remote).
Alarm status:
Major
<text> value:
%i - <Link number>
%i - <SP number>
%i - <SLC number>
%s - <congestion state>: { "UNINHIBITED", "INHIBITED" }
Additional Info1
varbind
INHIBITED
Condition:
Link becomes uninhibited - local AND remote
Alarm status:
cleared
Corrective Action:
Make sure the link is uninhibited on both local and remote sides
Note:
This alarm is raised for any change in the remote or local inhibition
status.
Version 4.8
579
January 2006
Mediant 3000
Table 28-12: acSS7LinkBlockStateChangeAlarm

Alarm:
acSS7LinkBlockStateChangeAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.21
No
Major
Event Type:
communicationsAlarm
Probable Cause:
other
Note:
Support pending
Table 28-13: acSS7LinkCongestionStateChangeAlarmTrap

Alarm:
acSS7LinkCongestionStateChangeAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.22
Default Severity
Major
Event Type:
communicationsAlarm
Probable Cause:
other
Alarm Text:
*** SS7 *** Link %i is %s %s
Status Changes:
Condition:
SS7 link becomes congested (local or remote).
Alarm status:
Major
<text> value:
%i - <Link number>
%s IF link has MTP3 layer, then this string equals:
(SP %i linkset %i slc %i)
Where:
%i - <SP number>
%i - <SLC number>
Otherwise there is NO additional text.
%s - <congestion state>: { "UNCONGESTED", "CONGESTED" }
Additional Info1
varbind
CONGESTED
Condition:
Link becomes un-congested - local AND remote.
Alarm status:
cleared
User's Manual
580
User's Manual
Table 28-13: acSS7LinkCongestionStateChangeAlarmTrap

Alarm:
acSS7LinkCongestionStateChangeAlarm
Corrective Action:
Reduce SS7 traffic on that link.
Note :
This alarm is raised for any change in the remote or local congestion
status.
System#0/SS7#0/ SS7LinkSet#<m> where m is the link set number.
Table 28-14: acSS7LinkSetStateChangeAlarm Trap

Alarm:
acSS7LinkSetStateChangeAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.23
Default Severity
Major
Event Type:
communicationsAlarm
Probable Cause:
other
Alarm Text:
*** SS7 *** Linkset %i on SP %i is %s
Status Changes:
Condition:
Operational state of the SS7 link-set becomes BUSY.
Alarm status:
Major
<text> value:
%i - <SP number>
%s - <state name: { "OFFLINE", "BUSY", "INSERVICE"}
Additional Info1
varbind
BUSY
Condition:
Operational state of the link-set becomes IN-SERVICE or OFFLINE
Alarm status:
cleared
Corrective Action:
For full details see the SS7 section and SS7 MTP3 relevant standards
System#0/SS7#0/ SS7RouteSet#<m> where m is the route set number.
Version 4.8
581
January 2006
Mediant 3000
Table 28-15: acSS7RouteSetStateChangeAlarm Trap

Alarm:
acSS7RouteSetStateChangeAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.24
Default Severity
Major
Event Type:
communicationsAlarm
Probable Cause:
other
Alarm Text:
*** SS7 *** Routeset %i on SP %i is %s
Status Changes:
Condition:
Operational state of the SS7 route-set becomes BUSY
Alarm status:
Major
<text> value:
%i - <Route-Set number>
%i - <SP number>
Additional Info:
BUSY
Condition:
Operational state of the route-set becomes IN-SERVICE or OFFLINE
Alarm status:
cleared
Corrective Action:
System#0/SS7#0/ SS7SN#<m> where m is the (signaling node) number.
Table 28-16: acSS7SNSetStateChangeAlarmTrap

Alarm:
acSS7SNSetStateChangeAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.25
Default Severity
Major
Event Type:
communicationsAlarm
Probable Cause:
other
Alarm Text:
*** SS7 *** SP %i is %s
Status Changes:
Condition:
Operational state of the SS7 node becomes BUSY
Alarm status:
Major
User's Manual
582
User's Manual
Table 28-16: acSS7SNSetStateChangeAlarmTrap

Alarm:
acSS7SNSetStateChangeAlarm
<text> value:
%i - <SP number>
Additional Info1
varbind
BUSY
Condition:
Cleared when the operational state of the node becomes IN-SERVICE or

OFFLINE
Alarm status:
cleared
Corrective Action:
Signaling Node must complete its MTP3 restart procedure and become unisolated
System#0/SS7#0/SS7Redundancy#0.
Table 28-17: acSS7RedundancyAlarm

Alarm:
acSS7RedundancyAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.26
No
Major
Event Type:
communicationsAlarm
Probable Cause:
other
Note:
Support pending
28.1.4
Component: Chassis#0
The source varbind
Chassis#0/FanTray#0
text
for
the
alarm
under
the
component
below
is
Table 28-18: acFanTrayAlarm Alarm Trap

Alarm:
acFanTrayAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.29
Default Severity
Critical
Event Type:
equipmentAlarm
Version 4.8
583
January 2006
Mediant 3000
Table 28-18: acFanTrayAlarm Alarm Trap

Alarm:
acFanTrayAlarm
Probable Cause:
heatingVentCoolingSystemProblem
Alarm Text:
Fan-Tray Alarm.
Status Changes:
Condition:
Fan-Tray is missing
Alarm status:
Critical
<text> value:
Fan-Tray Alarm. Fan-Tray is missing.
Condition:
One or more fans in the Fan-Tray are faulty.
Alarm status:
Major
<text> value:
Fan is faulty.
Condition:
Fan tray is in place and fans are working.
Alarm status:
Cleared
The source varbind text for the alarm under this component
Chassis#0/PowerSupply#<m> where m is the power supplys slot number.
is
Table 28-19: acPowerSupplyAlarm Alarm Trap

Alarm:
acPowerSupplyAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.30
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
powerProblem
Alarm Text:
Power-Supply Alarm. Power-Supply is missing.
Status Changes:
Condition:
The HA (High Availability) feature is active and one of the power supply
units is faulty or missing.
Alarm status:
Major
Condition:
PS unit is placed and working.
Alarm status:
Cleared
User's Manual
584
User's Manual
Table 28-19: acPowerSupplyAlarm Alarm Trap

acPowerSupplyAlarm
Alarm:
The source varbind text for the alarm under this component
Chassis#0/PemCard#<m> where m is the power entry modules slot number.
is
Table 28-20: acPEMAlarm Alarm Trap

Alarm:
acPEMAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.31
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
underlyingResourceUnavailable
Alarm Text:
PEM Module Alarm. <text>
Status Changes:
Condition:
The HA (High Availability) feature is active and one of the PEM units is
missing (PEM Power Entry Module)
Alarm status:
Critical
<text> value:
PEM card is missing.
Condition:
PEM card is placed and both DC wires are in.
Alarm status:
Cleared
The source varbind text for the alarm under this component is Chassis#0/SA#<m>
where m is the shelf Alarm modules slot number.
Table 28-21: acSAMissingAlarm Alarm Trap

Alarm:
acSAMissingAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.32
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
underlyingResourceUnavailable
Alarm Text:
SA Module Alarm. SA-Module from slot #n is missing.
Version 4.8
585
January 2006
Mediant 3000
Table 28-21: acSAMissingAlarm Alarm Trap

acSAMissingAlarm
Alarm:
Status Changes:
Condition:
SA module removed or missing
Alarm status:
Critical
Condition:
SA module is in slot 2 or 4 and working.
Alarm status:
Cleared
The source varbind text for the alarm under this component is Chassis#0.
Table 28-22: acUserInputAlarm Alarm Trap

Alarm:
acUserInputAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.36
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
inputDeviceError
Alarm Text:
User input Alarm. User's Input-Alarm turn on.
Status Changes:
Condition:
Input dry contact is short circuited.
Alarm status:
Critical
Condition:
Input dry contact circuit is reopened.
Alarm status:
Cleared
28.1.5
Component: System#0/Module#<m>
Note: The alarm traps discussed in this section applies to the Mediant 3000 in
High Availability Mode ONLY.
User's Manual
586
User's Manual
The source varbind text for the alarms under the component below is
System#0/Module#<m> where m is the 6310 modules slot number.
Table 28-23: acHASystemFaultAlarm Alarm Trap

Alarm:
acHASystemFaultAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.33
Default Severity
critical
Event Type:
qualityOfServiceAlarm
Probable Cause:
outOfService
Alarm Text:
No HA! <text>
Status Changes:
Condition:
HA feature is active but the system is NOT working in HA mode.
Alarm status:
Critical
<text> value:
there are many possible values for the text:

Fatal exception error
TCPIP exception error
Network processor exception error
SW WD exception error
HW WD exception error
SAT device is missing
SAT device error
DSP error
BIT tests error
PSTN stack error
Keep Alive error
Software upgrade
Manual switch over
Manual reset
Board removal
Can't read slot number
TER misplaced
HW fault. TER in slot 2 or 3 is missing
HW fault. TER has old version or is not functional
HW fault. invalid TER Type
HW fault. invalid TER active/redundant state
HW fault. Error reading GbE state
Redundant module is missing
Version 4.8
587
January 2006
Mediant 3000
Table 28-23: acHASystemFaultAlarm Alarm Trap

acHASystemFaultAlarm
Alarm:
Unable to sync SW versions

Redundant is not connecting
Redundant is not reconnecting after deliberate restart
No Ethernet Link in redundant module
SA module faulty or missing
Condition:
HA feature is active and the redundant module is in start up mode and

hasnt connected yet.
Alarm status:
Minor
<text> value:
Waiting for redundant to connect
Condition:
HA system is active.
Alarm status:
Cleared
Table 28-24: acHASystemConfigMismatchAlarm Alarm Trap

Alarm:
acHASystemConfigMismatchAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.34
Default Severity
major
Event Type:
Probable Cause:
configurationOrCustomizationError
Alarm Text:
Configuration mismatch in the system.
Status Changes:
Condition:
HA feature is active. The active module was unable to pass on to the

redundant module the License Key.
Alarm status:
Major
<text> value:
Fail to update the redundant with feature key
Condition:
Successful License Key update.
Alarm status:
Cleared
<text> value:
The feature key was successfully updated in the redundant module
User's Manual
588
User's Manual
Table 28-24: acHASystemConfigMismatchAlarm Alarm Trap

Alarm:
acHASystemConfigMismatchAlarm
Table 28-25: acHASystemSwitchOverAlarm Alarm Trap

Alarm:
acHASystemSwitchOverAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.35
Default Severity
Critical
Event Type:
qualityOfServiceAlarm
Probable Cause:
outOfService
Alarm Text:
Switch-over:
Status Changes:
Condition:
Switch over has taken place.
Alarm status:
Critical
<text> value:
see the acHASystemFaultAlarm table above.
Condition:
10 seconds have passed since the switch over.
Alarm status:
cleared

Alarm:
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.3
Default Severity
critical
Event Type:
equipmentAlarm
Probable Cause:
temperatureUnacceptable (50)
Alarm Text:
Board temperature too high
Status Changes:
Condition:
Temperature in the active module or redundant is above 67 degrees C

(140 degrees F)
Alarm status:
critical
Version 4.8
589
January 2006
Mediant 3000

Alarm:
Condition:
After raise, temperature falls below 55 degrees C (131 degrees F)
Alarm status:
cleared
Corrective Action:
Inspect the system. Determine if all fans in the system are properly
operating.
The source varbind text for the alarm under this component is:
If the lost link is from the Active module - Chassis#0/Module#<m>/EthernetLink#0
where m is the 6310 modules slot number.
If the lost link is from the Redundant module - Chassis#0/Module#<m> where m is the
6310 modules slot number.
Table 28-27: acBoardEthernetLinkAlarm Alarm Trap

Alarm:
acBoardEthernetLinkAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.10
Default Severity
Critical
Event Type:
equipmentAlarm
Probable Cause:
Alarm Text:
Ethernet link alarm: <text>
Status Changes:
Condition:
Fault on single interface of the Active module.
Alarm status:
Major
<text> value:
Redundant link (physical link n) is down
Condition:
Fault on both interfaces
Alarm status:
critical
<text> value:
No Ethernet link
Condition:
Fault on single interface of the Redundant module.
Alarm status:
Major
<text> value:
Redundant link in the redundant module (physical link n) is down
Condition:
Both interfaces are operational
User's Manual
590
User's Manual
Table 28-27: acBoardEthernetLinkAlarm Alarm Trap

Alarm:
acBoardEthernetLinkAlarm
Alarm status:
cleared
Corrective Action:
Ensure that both Ethernet cables are plugged into the back of the system.
Inspect the systems Ethernet link lights to determine which interface is
failing. Reconnect the cable or fix the network problem
Note:
The alarm behaves differently when coming from the redundant or the
active modules of an HA system. The alarm form the redundant will be
raised when there is an operational HA configuration in the system. There
is no critical severity for the redundant module losing both its Ethernet
Links as that is conveyed in the noHA alarm that follows such a case.
28.1.6
Component: Interfaces#0/Sonet#<m>
The source varbind text for the alarms under the component below is
Interfaces#0/Sonet#<m> where m is the Sonet IF number.
Table 28-28: AcSonetSectionLOFAlarm Alarm Trap

Alarm:
acSonetSectionLOFAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.38
Default Severity
critical
Event Type:
communicationsAlarm
Probable Cause:
lossOfFrame
Alarm Text:
SONET-Section LOF.
Status Changes:
Condition:
LOF condition is present on SONET no.n
Alarm status:
Critical
<text> value:
LOF
Note:
The sonetSectionCurrentStatus field in the sonetSectionCurrentTable will

have a value sonetSectionLOF (4).
Condition:
LOF condition is not present.
Alarm status:
cleared
Version 4.8
591
January 2006
Mediant 3000
Table 28-29: AcSonetSectionLOSAlarm Alarm Trap

Alarm:
acSonetSectionLOSAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.39
Default Severity
critical
Event Type:
communicationsAlarm
Probable Cause:
lossOfSignal
Alarm Text:
SONET-Section LOS.
Status Changes:
Condition:
LOS condition is present on SONET no #n
Alarm status:
Critical
<text> value:
LOS
Note:
The sonetSectionCurrentStatus field in the sonetSectionCurrentTable will

have a value sonetSectionLOS (2).
Condition:
AIS condition is present (LOS condition is not present)
Alarm status:
Critical
<text> value:
Note:
Condition:
LOS condition is not present.
Alarm status:
cleared
Table 28-30: AcSonetLineAISAlarm Alarm Trap

Alarm:
acSonetLineAISAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.40
Default Severity
critical
Event Type:
communicationsAlarm
Probable Cause:
receiveFailure
Alarm Text:
SONET-Line AIS.
Status Changes:
User's Manual
592
User's Manual
Table 28-30: AcSonetLineAISAlarm Alarm Trap

Alarm:
acSonetLineAISAlarm
Condition:
AIS condition is present on SONET-Line #n.
Alarm status:
critical
<text> value:
AIS
Note:
The sonetLineCurrentStatus field in the sonetLineCurrentTable will have a

value sonetLineAIS (2).
Condition:
AIS condition is not present.
Alarm status:
cleared
Table 28-31: AcSonetLineRDIAlarm Alarm Trap

Alarm:
acSonetLineRDIAlarm
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.41
Default Severity
critical
Event Type:
communicationsAlarm
Probable Cause:
transmitFailure
Alarm Text:
SONET-Line RDI.
Status Changes:
Condition:
RDI condition is present on SONET-Line #n.
Alarm status:
Critical
<text> value:
RDI
Note:
The sonetLineCurrentStatus field in the sonetLineCurrentTable will have a

value sonetLineRDI (4).
Condition:
RDI condition is not present.
Alarm status:
cleared
Version 4.8
593
January 2006
Mediant 3000
28.2
Log Traps (Notifications)

This section details traps that are not alarms. These traps are sent out with the
severity varbind value of indeterminate. These traps do not clear, they do not appear
in the alarm history or active tables. One log trap that does send out clear is
acPerformanceMonitoringThresholdCrossing.
Table 28-32: acKeepAlive Log Trap

Trap
acKeepAlive
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.16
Default Severity
Indeterminate
Event Type:
other (0)
Probable Cause:
other (0)
Trap Text:
Keep alive trap
Status Changes:
The STUN client in the board is enabled and has either identified a NAT or is
not finding the STUN server
Condition:
The ini file contains the following line: SendKeepAliveTrap=1

Trap status:
Trap is sent
Note:
Keep-alive is sent out every x second.x =0. 9 of the time defined in the
NatBindingDefaultTimeout parameter
Table 28-33: acPerformanceMonitoringThresholdCrossing Log Trap

Trap
acPerformanceMonitoringThresholdCrossing
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.27
Default Severity
Indeterminate
Event Type:
other (0)
Probable Cause:
other (0)
Trap Text:
"Performance: Threshold alarm was set ", with source = name of

performance counter which caused the trap
Status Changes:
Condition:
A performance counter has crossed the high threshold
Trap status:
Indeterminate
Condition:
A performance counter has crossed the low threshold
Trap status:
Cleared
User's Manual
594
User's Manual
Table 28-34: acHTTPDownloadResult Log Trap

Trap:
acHTTPDownloadResult
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.28
Default Severity
Indeterminate
Event Type:
processingErrorAlarm (3) for failures and other (0) for success.
Probable Cause:
other (0)
Status Changes:
Condition:
Successful HTTP download.
Trap text:
HTTP Download successful
Condition:
Failed download.
Trap text:
HTTP download failed, a network error occurred.
NOTE:
There are other possible textual messages describing NFS failures or

success, FTP failure or success.
28.3
Other Traps
The following are provided as SNMP traps and are not alarms.
Table 28-35: coldStart Trap

Trap Name:
coldStart
OID:
1.3.6.1.6.3.1.1.5.1
MIB
SNMPv2-MIB
Note:
This is a trap from the standard SNMP MIB.
Table 28-36: authenticationFailure Trap

Trap Name:
authenticationFailure
OID:
1.3.6.1.6.3.1.1.5.5
MIB
SNMPv2-MIB
Version 4.8
595
January 2006
Mediant 3000
Table 28-37: acBoardEvBoardStarted Trap

Trap Name:
acBoardEvBoardStarted
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.4
MIB
AcBoard
Severity
cleared
Event Type:
equipmentAlarm
Probable Cause:
Other(0)
Alarm Text:
Initialization Ended
Note:
This is the AudioCodes Enterprise application cold start trap.
Table 28-38: AcDChannelStatus Trap

Trap Name:
acDChannelStatus
OID:
1.3.6.1.4.1.5003.9.10.1.21.2.0.37
MIB
AcBoard
Severity
minor
Event Type:
communicationsAlarm
Probable Cause:
communicationsProtocolError
Alarm Text:
D-Channel Trap.
Trunk no.<m> where m is the trunk number (from 0 up).
Source:
Status Changes:
Condition:
D-Channel un-established.
Trap status:
Trap is sent with the severity of Minor.
Condition:
D-Channel established.
Trap status:
Trap is sent with the severity of Cleared.
28.4
Trap Varbinds
Every AudioCodes Enterprise trap described above provides the following fields
(known as varbinds). Refer to the AcBoard MIB for additional details on these
varbinds.
User's Manual
596
User's Manual
acBoardTrapGlobalsName
acBoardTrapGlobalsTextualDescription
acBoardTrapGlobalsSource
acBoardTrapGlobalsSeverity
acBoardTrapGlobalsUniqID
acBoardTrapGlobalsType
acBoardTrapGlobalsProbableCause
acBoardTrapGlobalsAdditionalInfo1
Note that acBoardTrapGlobalsName is actually a number. The value of this varbind is

X minus 1, where X is the last number in the trap OID. For example, the name of
acBoardEthernetLinkAlarm is 9.
The OID for acBoardEthernetLinkAlarm is
1.3.6.1.4.1.5003. 9.10.1.21.2.0.10.
Version 4.8
597
January 2006
User's Manual
29
29. Appendix - Customizing the Web Interface
Appendix - Customizing the Web

Interface
OEM customers incorporating AudioCodes' devices into their portfolios can customize
the device's Web interface to suit their specific corporate logo and product naming
conventions.
OEM customers can customize the Web interface's title bar (AudioCodes' title bar is
shown in the figure, "Web Interface Title Bar", below and an example of a customized
title bar is shown in the figure, "Customized Web Interface Title Bar" below.)
Note: The product name appears according to the AudioCodes product utilized
together with the AudioCodes Web Interface.
Figure 29-1: Web Interface Title Bar
Corporation logo can be

OEM-customized
Background image can be

OEM-customized
Product name can be

OEM-customized
Figure 29-2: Customized Web Interface Title Bar
29.1
Company & Product Bar Components

The Title bar is composed of 3 components:
Version 4.8
Replacing the main corporation logo - refer to ''Replacing the Main Corporate
Logo'' on page 600
Replacing the title bar's background image file - refer to ''Replacing the Title Bar's
Background Image File'' on page 602
Customizing the product's name - Refer to ''Customizing the Product's Name'' on

page 603
599
January 2006
Mediant 3000
29.2
Replacing the Main Corporate Logo

The main corporate logo can be replaced either with a different logo image file (refer
to "Replacing the Main Corporate Logo with an Image File" below) or with a text' string
(refer to Replacing the Main Corporate Logo wi'th a Text String.)
Note: When the main corporate logo is replaced, the AudioCodes logo in the main
menu bar on the left (refer to ''About the Web Interface Screen'' on page
208) and the AudioCodes logo in the Software Upgrade Wizard (refer to
''Software Upgrade Wizard'' on page 266) disappear.
29.2.1
Replacing the Main Corporate Logo with an Image File

Note: Use a gif, jpg or jpeg file for the logo image. It is important that the image file
has a fixed height of 59 pixels (the width can be configured). The size limit
for the logo image file is 64 k bytes.
To replace AudioCodes' default logo with your own corporate logo

via the Web interface, take these 8 steps:
1.
Access the Embedded Web Server (refer to ''Accessing the Embedded Web
2.
In the browser's URL field, enter the IP address of the location of the
AudioCodes' Web Interface Application, followed by /AdminPage.
3.
If you have not accessed this page for a while, you are prompted for your user
name and Password. Enter them and press OK.
4.
On the Main-menu bar to the left, click the Logo Image Download option. The
Image Download screen appears.
Figure 29-3: Logo Image Download Screen
User's Manual
600
User's Manual
5.
Click the Browse button in the Send Logo Image File from your computer to
the device box. Navigate to the folder that contains the logo image file you want
to download.
6.
Click the Send File button. The file is sent to the device. When the download is
complete, the screen is automatically refreshed and the new logo image is
displayed.
7.
Check the appearance of the logo to verify that it appears as desired. If you want
to modify the width of the logo (the default width is 339 pixels), in the Logo Width
field, enter the new width (in pixels) and press the Set Logo Width button.
8.
Save the image to flash memory by clicking the Save Configuration button on the
Save Configuration screen. The new logo appears on all Web interface screens.
Note: If you encounter any problem during the loading of the files, or you want to
restore the default images, click the Restore Default Images button.
To replace AudioCodes' default logo with your own corporate logo

image via the ini file, take these 2 steps:
1.
Place your corporate logo image file in the same folder in which the device's ini
file is located (i.e. the same location defined in the BootP/TFTP server). For
detailed information on the BootP/TFTP server, refer to the Appendix,
''BootP/TFTP Server'' on page 307 .
2.
Add/modify the two ini file parameters in the table below according to the
procedure described in ''Software Upgrade Wizard'' on page 266.
Note: Loading the device's ini file via the Configuration File screen in the Web
interface does not load the corporate logo image file as well.
Table 29-1: Customizable Logo ini File Parameters for the Image File
Parameter
Description
LogoFileName
The name of the image file containing your corporate logo.

Use a gif, jpg or jpeg image file.
The default is AudioCodes' logo file.
Note: The length of the name of the image file is limited to 47 characters.
LogoWidth
Width (in pixels) of the logo image.

Note: The optimal setting depends on the resolution settings.
The default value is 339, which is the width of AudioCodes' displayed logo.
Version 4.8
601
January 2006
Mediant 3000
29.2.2
Replacing the Main Corporate Logo with a Text String

The main corporate logo can be replaced with a text string. To replace AudioCodes'
default logo with a text string via the Web interface, modify the two ini file parameters
in the table below according to the procedure described in''Modifying ' on page 604ini
'File Parameters via the Web Interface's AdminPage'' on page 604.
Table 29-2: Customizable Logo ini File Parameters for the String Text
Parameter
Description
UseWebLogo
0 = Logo image is used (default value).

1 = Text string is used instead of a logo image.
WebLogoText
Text string that replaces the logo image.

The string can be up to 15 characters.
29.3
Replacing the Background Image File

The background image file is repeated across the width of the screen. The number of
times the image is repeated depends on the width of the background image and
screen resolution. When choosing your background image, keep this in mind.
Note: Use a gif, jpg or jpeg file for the background image. It is important that the
background image file has a fixed height of 59 pixels. The size limit for the
background image file is 64k bytes.
To replace the background image via the Web interface, take these
7 steps:
User's Manual
1.
Access the Embedded Web Server (refer to ''Accessing the Embedded Web
2.
In the browser's URL field, enter the IP address of the location of the Web
Interface Application, followed by /AdminPage.
3.
4.
On the Main-menu bar to the left, click the Image Download option. The Image
Download screen appears.(shown in the figure, 'Image Download Screen'
above).
5.
Click the Browse button in the Send Background Image File from your
computer to the device box. Navigate to the folder that contains the background
image file you want to download.
6.
Click the Send File button. The file is sent to the device. When the download is
complete, the screen is automatically refreshed and the new background image
is displayed.
602
User's Manual
7.
Save the image to the flash memory by clicking the Save Configuration button
on the Save Configuration screen. The new background appears on all Web
interface screens.
Note: If you encounter any problem during the loading of the files, or you want to
restore the default images, click the Restore Default Images button.
To replace the background image via the ini file, take these 2
steps:
1.
Place your background image file in the same folder in which the device's ini file
is located (i.e. the same location defined in the BootP/TFTP server). For detailed
information on the BootP/TFTP server, refer to the Appendix, 'BootP/TFTP
Server'' on page 307.
2.
Add/modify the ini file parameters in the table below according to the procedure
described ''Software Upgrade Wizard'' on page 266.
Note: Loading the device's ini file via the Configuration File screen in the Web
interface does not load the background image file as well.
Table 29-3: Customizable Background ini File Parameters

Parameter
Description
BkgImageFileName
The name of the file containing the new background.

Use a gif, jpg or jpeg image file.
The default is AudioCodes background file.
Note: The length of the name of the image file is limited to 47 characters.
29.4
Customizing the Product Name

The Product Name text string can be modified according to OEMs specific
requirements.
Version 4.8
To replace the default product name with a text string via the Web interface,
modify the two ini file parameters in the table below according to the procedure
described' in 'Modifyi' on page 604ng ini 'File Parameters via the Web Interface's
AdminPage'' on page 604.
To replace the default product name with a text string via the ini file, add/modify
the two ini file parameters in the table below according to the procedure
described in' 'Software Upgrade Wizard'' on page 266.
603
January 2006
Mediant 3000
Table 29-4: Customizable Product Name ini File Parameters

Parameter
Description
UseProductName
0 = Don't change the product name (default).

1 = Enable product name change.
UserProductName
Text string that replaces the product name.

The default is "Mediant 3000".
The string can be up to 29 characters.
29.4.1
Customizing the Web Browser Title Bar

Figure 29-4: Default Web Browser Title Bar
Upon customizing the logo section of the screen as described in ''Replacing the Main
Corporate Logo'' on page 600, the AudioCodes string on the Web browser's title bar
changes to the text string held in the WebLogoText parameter. If this parameter holds
an empty string, the browser's title bar contains only its own name.
29.5
Modifying ini File Parameters via the AdminPage

To modify ini file parameters via the AdminPage, take these 7
steps:
User's Manual
1.
Open AudioCodes' Web Interface Application, using the directions in the Device
Management section of the accompanying AudioCodes product user's manual.
2.
In the browser's URL field, enter the IP address of the location of the
AudioCodes' Web Interface Application, followed by /AdminPage.
3.
604
User's Manual
4.
Click the INI Parameters option, the ini Parameters screen is displayed.
Figure 29-5: ini Parameters Screen
5.
In the Parameter Name dropdown list, select the required ini file parameter.
6.
In the Enter Value text box to the right, enter the parameter's new value.
7.
Click the Apply new value button to the right. The ini Parameters screen is
refreshed, the parameter name with the new value appears in the fields at the top
of the screen and the Output Window displays a log displaying information on the
operation.
Note: You cannot load the image files (e.g., logo/background image files) or any
other auxiliary file to the device by choosing a file name parameter in this
screen.
Version 4.8
605
January 2006
User's Manual
30
30. Appendix - Regulatory Information
Appendix - Regulatory Information

Declaration of Conformity
73/23/EEC (including amendments),
Application of Council Directives:
89/336/EEC (including amendments)

Standards to which Conformity is Declared:
EN55022: 1998, Class A

EN300 386 V1.3.1: 2001
EN60950-1: 2001
Manufacturer's Name:
AudioCodes Ltd.
Manufacturer's Address:
1 Hayarden Street, Airport City, Lod 70151, Israel.
Type of Equipment:
Digital VoIP System. DC powered
Model Numbers:
Mediant 3000, Stretto 3000, IPmedia 3000
I, the undersigned, hereby declare that the equipment specified above conforms to the above
Directives and Standards.
Signature
11th February, 2005
Airport City, Lod, Israel
Date (Day/Month/Year)
Location
I. Zusmanovich, Compliance Engineering Manager
Czech
[AudioCodes Ltd] tmto prohlauje, e tento [3000 Series] je ve shod se zkladnmi

poadavky a dalmi pslunmi ustanovenmi smrnice 73/23/EEC 89/336/EEC
Danish
Undertegnede [AudioCodes Ltd] erklrer herved, at flgende udstyr [3000 Series]

overholder de vsentlige krav og vrige relevante krav i direktiv 73/23/EEC
89/336/EEC
Dutch
Hierbij verklaart [AudioCodes Ltd] dat het toestel [3000 Series] in overeenstemming is
met de essentile eisen en de andere relevante bepalingen van richtlijn 73/23/EEC
89/336/EEC
English
Hereby, [AudioCodes Ltd], declares that this [3000 Series] is in compliance with the
essential requirements and other relevant provisions of Directive 73/23/EEC
89/336/EEC
Estonian
Kesolevaga kinnitab [AudioCodes Ltd] seadme [3000 Series] vastavust direktiivi

73/23/EEC 89/336/EEC phinuetele ja nimetatud direktiivist tulenevatele teistele
asjakohastele stetele.
Finnish
[AudioCodes Ltd] vakuuttaa tten ett [3000 Series] tyyppinen laite on direktiivin
73/23/EEC 89/336/EEC oleellisten vaatimusten ja sit koskevien direktiivin muiden
ehtojen mukainen.
French
Par la prsente [AudioCodes Ltd] dclare que l'appareil [3000 Series] est conforme aux
exigences essentielles et aux autres dispositions pertinentes de la directive 73/23/EEC
Version 4.8
607
January 2006
Mediant 3000
Czech
[AudioCodes Ltd] tmto prohlauje, e tento [3000 Series] je ve shod se zkladnmi

poadavky a dalmi pslunmi ustanovenmi smrnice 73/23/EEC 89/336/EEC
Danish
Undertegnede [AudioCodes Ltd] erklrer herved, at flgende udstyr [3000 Series]

overholder de vsentlige krav og vrige relevante krav i direktiv 73/23/EEC
89/336/EEC
89/336/EEC
German
Hiermit erklrt [AudioCodes Ltd], dass sich dieser/diese/dieses [3000 Series] in

bereinstimmung mit den grundlegenden Anforderungen und den anderen relevanten
Vorschriften der Richtlinie 73/23/EEC 89/336/EEC befindet". (BMWi)
Greek
Hungarian
Alulrott, [AudioCodes Ltd] nyilatkozom, hogy a [3000 Series] megfelel a vonatkoz

alapvet kvetelmnyeknek s az 73/23/EEC 89/336/EEC irnyelv egyb elrsainak
Icelandic
ki etta er samrmi vi tilskipun Evrpusambandsins 73/23/EEC 89/336/EEC
Italian
Con la presente [AudioCodes Ltd] dichiara che questo (3000 Series) conforme ai
requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla direttiva 73/23/EEC
89/336/EEC
Latvian
Ar o [AudioCodes Ltd] deklar, ka [3000 Series] atbilst Direktvas 73/23/EEC

89/336/EEC btiskajm prasbm un citiem ar to saisttajiem noteikumiem.
Lithuanian
[AudioCodes Ltd] deklaruoja, kad irenginys [3000 Series] tenkina 73/23/EEC

89/336/EEC Direktyvos esminius reikalavimus ir kitas sios direktyvos nuostatas
Maltese
Hawnhekk, [AudioCodes Ltd], jiddikjara li dan [3000 Series] jikkonforma mal-tiijiet

essenzjali u ma provvedimenti orajn relevanti li hemm fid-Dirrettiva 73/23/EEC
89/336/EEC
Norwegian Dette produktet er i samhrighet med det Europeiske Direktiv 73/23/EEC 89/336/EEC
Polish
[AudioCodes Ltd], deklarujemy z pelna odpowiedzialnoscia, ze wyrb [3000 Series]

spelnia podstawowe wymagania i odpowiada warunkom zawartym w dyrektywie
73/23/EEC 89/336/EEC
Portugues
e
[AudioCodes Ltd] declara que este [3000 Series] est conforme com os requisitos
essenciais e outras disposies da Directiva 73/23/EEC 89/336/EEC.
Slovak
[AudioCodes Ltd] tmto vyhlasuje, e [3000 Series] spa zkladn poiadavky a vetky
prslun ustanovenia Smernice 73/23/EEC 89/336/EEC
Slovene
iuo [AudioCodes Ltd] deklaruoja, kad is [3000 Series] atitinka esminius reikalavimus
ir kitas 73/23/EEC 89/336/EEC Direktyvos nuostatas.
Spanish
Por medio de la presente [AudioCodes Ltd] declara que el (3000 Series) cumple con
los requisitos esenciales y cualesquiera otras disposiciones aplicables o exigibles de la
Directiva 73/23/EEC 89/336/EEC
Swedish
Hrmed intygar [AudioCodes Ltd] att denna [3000 Series] str I verensstmmelse med
de vsentliga egenskapskrav och vriga relevanta bestmmelser som framgr av
direktiv 73/23/EEC 89/336/EEC
User's Manual
608
User's Manual
30. Appendix - Regulatory Information
Safety Notices
Installation and service of this gateway must only be performed by authorized, qualified
service personnel.
The protective earth terminal on the back of the 3000 must be permanently connected to
protective earth.
Caution Laser
The SB-1610 board may contain a Class I Laser/LED emitting device, as defined by 21CFR
1040 and IEC825.
Do NOT stare directly into the beam or fiber optic terminations as this can damage your
eyesight.
NEBS Information
The Ethernet port cable must be shielded and earthed at both ends to comply with GR 1089.
Telecommunication Safety
The safety status of each port is declared and detailed in the table below:
Ports
Safety Status
DC Input Power Port
SELV
GbE (Gigabit Ethernet)
SELV
SELV: Safety extra low voltage circuit.
FCC Statement
This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses and can radiate radio frequency energy and, if not installed and used in
accordance with the instruction manual, may cause harmful interference to radio communications.
Operation of this equipment in a residential area is likely to cause harmful interference in which case
the user will be required to correct the interference at his own expense.
WARNING
This is a Class A product. In a domestic environment this product may cause radio
interference in which case the user may be required to take adequate measures.
Version 4.8
609
January 2006
Mediant 3000
User's Manual
610
User's Manual
31
31. List of Abbreviations
List of Abbreviations
Table 31-1: List of Abbreviations
Abbreviation
Meaning
AAL1
ATM Adaptation Layer 1 Used in North America for voice traffic. It

provides support for constant bit rate (voice) traffic
AAL2
ATM Adaptation Layer 2 Used to transmit standard and compressed voice

transmissions including silence suppression. It can support both constant
and variable bit rates.
ADPCM
Adaptive Differential PCM - voice compression
AIS
ASN.1
Abstract Syntax Notation
ATM
Asynchronous Transmission Mode A connection based transport

mechanism that is based on 53 byte cells
A-law
European Compander Functionality Rule (see -law)
bps
Bits per second
BLES
Broadband Loop Emulation Service by the DSL Forum
BRI
Basic Rate Interface in ISDN
CAS
Channel Associated Signaling
cPCI
Compact PCI (Industry Standard)
COLP
Connected Line Identity Presentation
COLR
Connected Line Identity Restriction
DHCP
Dynamic Host Control Protocol
DID
Direct Inward Dial
DS1
1.544 Mbps USA Digital Transmission System (see E1 and T1)
DS3
44.736 Mbps USA Digital Transmission System, Encapsulates 28 T1

streams, Also called T3
DSL
Digital Subscriber Line
DSP
Digital Signal Processor (or Processing)
DTMF
Dual Tone Multiple Frequency (Touch Tone)
E1
2.048 Mbps European Digital Transmission System (see T1)
E-ADPCM
Enhanced ADPCM
Version 4.8
611
January 2006
Mediant 3000

Abbreviation
Meaning
ETSI
European Telecommunications Standards Institute
FR
Frame Relay
GK
Gatekeeper
GW
Gateway
G.xxx
An ITU Standard - see References section for details
H.323
A range of protocol standards for IP-based networks
H.323 Entity
Any H.323 Component
IE
Information Element (ISDN layer 3 protocol, basic building block)
IETF
Internet Engineering Task Force
IP
Internet Protocol
IPmedia
AudioCodes series of VoIP Media Processing Boards
IPM-260/UNI
AudioCodes IPmedia PCI VoIP Media Processing Board, to 240 ports
IPM-1610
AudioCodes IPmedia cPCI VoIP Media Processing Board, to 240 ports
IPM-6310
AudioCodes IPmedia VoIP Media Processing Board, to 2016 voice/fax/data

independent multiple LBR channels
ISDN
Integrated Services Digital Network
ISO
International Standards Organization
ITU
International Telecommunications Union
ITU-T
Telecommunications section of the ITU
IVR
Interactive Voice Response
Jitter
Variation of interpacket timing interval
kbps
Thousand bits per second
LAPD
Line Access Protocol for the D-channel
LFA
LOF
Loss of Frame
Mbps
Million bits per second
MCU
Multipoint Control Unit (H.323)
Mediant
AudioCodes series of Voice over Packet Media Gateways
Mediant for
Broadband
AudioCodes series of Broadband Access Gateways, including Cable and

V5.2 Access Gateways
User's Manual
612
User's Manual

Abbreviation
Meaning
MEGACO
Media Gateway Control (Protocol, H.248)
MGC
Media Gateway Controller
MGCP
Media Gateway Control Protocol
MIB
Management Information Base
MP-102
AudioCodes 2-port Analog MediaPack Media Gateway
MP-104
MP-108
MP-124
ms or msec
Millisecond; a thousandth part of a second
MVIP
Multi Vendor Integration Protocol
NetCoder
AudioCodes Proprietary High Quality, Speech Coder
NIC
Network Interface Card
OSI
Open Systems Interconnection (Industry Standard)
PCI
Personal Computer Interface (Industry Standard)
PCM
Pulse Code Modulation
PDU
Protocol Data Unit
POTS
Plain Old Telephone System or Service
PRI
Primary Rate Interface in ISDN
PSTN
Public Switched Telephone Network
QoS
Quality of Service
RAI
Remote Alarm Indication
RAS
Registration, Admission, and Status (control within H.323).
RDK
Reference Design Kit.
RFC
Request for Comment issued by IETF.
RTCP
Real Time Control Protocol.
RTP
Real Time Protocol.
SB-1610
AudioCodes TrunkPack VoIP/ 1610 cPCI media streaming board, to 480

ports for Wireless systems
ScBus
Signal Computing Bus - part of SCSA
SCSA
Signal Computing System Architecture
Version 4.8
613
January 2006
Mediant 3000

Abbreviation
Meaning
SDK
Software Development Kit
SNMP
Simple Network Management Protocol
Stretto
AudioCodes series of Voice over Wireless Media Gateways
TCP
Transmission Control Protocol.
TCP/IP
Transmission Control Protocol/Internet Protocol.
TFTP
Trivial File Transfer Protocol.
TGCP
Trunking Gateway Control Protocol
TPNCP
AudioCodes TrunkPack Network Control Protocol.
TP-260/UNI
AudioCodes TrunkPack VoIP/260 Voice over IP PCI media streaming

board, up to 240 ports
TP-2810
AudioCodes TrunkPack VoIP/2810 cPCI T3 media streaming board, to 672

ports
TP-1610
AudioCodes TrunkPack VoIP cPCI media streaming board, to 480 ports
TP-6310
AudioCodes TrunkPack VoIP Media Processing Board, to 2016

voice/fax/data independent multiple LBR channels
TPM-1100
AudioCodes TrunkPack Module
TrunkPack
AudioCodes series of voice compression boards
T1
1.544 Mbps USA Digital Transmission System (see E1 and DS1)
T3
44.736 Mbps USA Digital Transmission System, Encapsulates 28 T1

streams, also called DS3
UDP
User Datagram Protocol
VCC
Virtual Channel Connection
VoAAL2
Voice over AAL2 (see above)
VoATM
Voice over Asynchronous Transfer Mode
VoDSL
Voice over Digital Subscriber Line
VoFR
Voice over Frame Relay
VoIP
Voice over Internet Protocol
VoP
Voice over Packet(s)
VoPN
Voice over Packet Networks
VPN
Virtual Private Network
-law
American Compander Functionality Rule, (see A-law)
User's Manual
614
User's Manual

Abbreviation
Meaning
s or sec
microsecond; a millionth part of a second
Version 4.8
615
January 2006
User's Manual
32
32. Index
Appendix - MGCP Compliance................... 513
Appendix - Regulatory Information ............. 611
Appendix - RTP/RTCP Payload Types117, 423
Appendix - Security............. 195, 207, 208, 453
Appendix - SNMP Traps ....... 26, 192, 203, 575
Appendix - SS7 Configuration Guide.......... 477
Appendix - Table Parameters ...... 94, 237, 238,
239, 240, 242, 243, 389, 477
Appendix - Utilities97, 195, 244, 246, 411, 413,
418, 421, 499
Application Settings ............................ 221, 224
Assigning an IP Address Using BootP ... 81, 82
Assigning an IP Address Using HTTP.......... 81
Assigning the IP Addresses for High
Availability Mode ....................................... 82
Assigning the Mediant 3000 IP Address81, 101
ATM AAL1................................................... 178
ATM AAL2................................................... 179
ATM AAL2 PVC Table ........................ 401, 405
ATM Port Loopback Table .................. 401, 402
ATM Port Table................................... 401, 402
ATM Port Table PARAMS .................. 389, 401
ATM Remote Gateway Table ............. 401, 404
ATM SVC Profile Table....................... 402, 406
Automatic Update Facility ............................. 98
Auxiliary Files................................................ 97
Auxiliary Files Download..... 267, 274, 418, 421
Index
6
6310/RTM ......................................................42
A
AAL1 ............................................................569
AAL2 ............................................................571
AAS Digit Collection Package (aasdc) Extends
Aasb Package..........................................542
AAS Digit Collection Package (aasrec)
Extends aasb Package ............................544
Abort Procedure ..........................................278
About the Web Interface Screen .........210, 604
Accessing the Embedded Web Server.......208,
211, 276, 285, 604, 606
Action/Event ................................................434
Actions .........................................................431
Actions upon Detecting Board Failure.........102
Adanced Audio Server Segment Management
Package (aassm) .....................................545
Administrative State Control ........................203
Advanced Announcement Packages Compliance Tables (MEGACO & MGCP)541
.................................................................541
(Early Draft)..............................................546
Advanced Audio Server Override Package
(aas0) .......................................................549
Advanced Audio Server Set Package (aass)
.................................................................549
Advanced Configuration ..............................220
Advanced Configuration Screen..........220, 463
Air Filter Replacement ...................................75
Alarm Indicators.............................................54
Alarm Traps .................................................575
API Demonstration Utilities..................431, 499
Appendix - Auxiliary Files ......................83, 411
Appendix - BootP/TFTP Server82, 86, 91, 100,
208, 278, 285, 309, 418, 419, 421, 605, 607
Appendix - CAS Protocol Table...................431
Appendix - CAS to Analog Mapping Protocol
.................................................................443
Appendix - Customizing the Web Interface .603
Appendix - DTMF, Fax & Modem Transport
Modes ......................................................427
Appendix - Getting Started with VLANs and
Multiple IPs.......................................190, 557
Appendix - Individual ini File Parameters .....91,
94, 215, 218, 219, 220, 223, 224, 228, 229,
230, 244, 317
Appendix - MEGACO Compliance ..............529
Version 4.8
B
Backing up the Current Software Upgrade Key
......................................................... 275, 278
Backup Copies of ini and Auxiliary Files72, 100
Basic Configuration..................................... 214
Basic Setup................................................. 560
Bearer Path Selection................................. 179
Board Hot-Swap Support.............................. 50
Board Replacement ...................................... 70
Boot Firmware & Operational Firmware ....... 83
BootP/TFTP Server Installation .................. 310
C
Cabling the Mediant 3000............... 57, 61, 100
Call Flows ................................................... 572
Call Progress Tone and User-Defined Tone
Auxiliary Files .......................................... 411
Carrier-Grade Alarm System ...................... 187
CAS Packages............................................ 127
CAS/R2 Support in MEGACO .................... 139
Certificates .......................................... 223, 252
Changing the Network Parameters via CLI 285
Changing the Script File ............................. 439
Channel Configuration ................................ 218
Channel Status ........................................... 262
Client Certificates........................................ 466
Client Configuration Screen........................ 314
Coder Table File ......................... 118, 132, 420
Cold Start Trap............................................ 188
Company & Product Bar Components........ 603
617
January 2006
Mediant 3000
Component
Board#<n>......................................575, 578
Chassis#0...............................................587
Interfaces#0/Sonet#<m> ........................595
SS7#0.....................................................582
System#0/Module#<m> .........................590
Component Replacement and Maintenance .69
Compression Coders...................................132
Configuration and Update of the Endpoint's
Notified Entity...........................................104
Configuration Extensions:............................479
Configuration File ........................222, 244, 280
Configuration Parameters and Files..83, 88, 91
Configuring and Unlocking the Mediant 300072
Configuring Fax Relay Mode .......................427
Configuring Fax/Modem ByPass Mode.......428
Configuring Fax/Modem Bypass NSE mode
.................................................................428
Configuring IPSec and IKE..........................455
Configuring RADIUS Support......................468
Connecting the Earth.....................................62
Connecting the PSTN and ATM Interfaces ..57,
62
Connection the DC Power .............................68
Constructing a CAS Protocol Table.............431
Control Protocol Reports .............................287
Converting a Modified CoderTable ini File to a
dat File Using DConvert Utility .................421
Converting a Modified CPT ini File to a dat File
with the Download Conversion Utility ......418
Cooling System .............................................53
Correlating PC / Mediant 3000 IP Address &
Subnet Mask ....................................208, 212
Customizing the Product Name...........603, 607
Customizing the Web Browser Title Bar......608
F
Fan Tray Unit Replacement.............. 73, 75, 76
Fax T.38 and Voice Band Data Support
(Bypass Mode) ........................ 143, 149, 171
Fax Transport Type Setting with Local
Connection Options......................... 106, 109
Fax/Modem Settings ................................... 427
Fax/Modem/CID Settings.................... 222, 228
Firewall Settings.......................... 223, 250, 473
for VoATM................................................... 569
Function ...................................................... 437
Functional Block Diagram............................. 27
Functional Specifications ............................ 303
Functions .................................................... 432
G
General ....................................................... 439
General Features .......................................... 24
General Media Settings ...................... 222, 230
General Parameters.................................... 216
General Security Settings ................... 223, 253
Getting Acquainted with the Web Interface 210
Getting Started........................................ 77, 81
Graceful Shutdown ............................... 70, 204
H
H.248.9 Compliance Matrix ........................ 541
H.248.9 Compliance Matrix - TD-51 (Early
Draft) ............................................... 541, 546
Hairpinning of ATM Connections ................ 182
High Availability....................................... 23, 25
High Availability Systems............................ 203
IKE .............................................................. 454

IKE Configuration................................ 454, 455
IKE Table ............................................ 223, 256
Individual ini File Parameters...................... 317
Infrastructure Parameters ........... 227, 317, 324
ini File Table Parameters............................ 389
INIT variables.............................................. 431
Initialization (ini) File ..................... 91, 411, 509
Initializing the Mediant 3000 System in High
Availability Mode ..................................... 100
Inserting Boards............................................ 71
Installing/Unzipping When Using a Windows
Operating System...................................... 77
Internal Firewal ........................................... 471
Internal Firewall........................................... 471
Introduction ................................................. 309
Introductory Notes......................................... 21
IP Settings........................................... 221, 223
IPmedia Settings................................. 222, 229
IPSec .......................................................... 455
IPSec and IKE............................................. 453
IPSec and IKE Configuration Tables
Confidentiality.......................................... 462
Default Coder Table (Tbl) ini file..................421

Default Dynamic Payload Types Which are Not
Voice Coders ...........................................425
Default RTP/RTCP/T.38 Port Allocation......425
Device Information.......................262, 266, 276
Diagnostics & Troubleshooting....................283
Digits Collection Support .............................145
Downloading Auxiliary Files via TFTP During
the Board Startup.................................91, 97
DTMF/MF Relay Settings ............................427
E
Electronic Surveillance (CALEA).................110
Embedded Web Server ..... 72, 81, 83, 91, 185,
204, 275, 284, 458, 461, 468, 557, 564
Embedded Web Server Protection & Security
Mechanisms .............................................205
Enabling PSTN Trace via the Web..............511
Encoding Mechanism ............................97, 456
Ethernet Ports................................................66
Examples of SS7 ini Files............................480
User's Manual
618
User's Manual
32. Index
MGCP/MEGACO Error Conditions ............. 287
MGCP-Specific Parameters................ 317, 373
MI and VLAN Parameters........................... 565
Microsoft DHCP/BootP Server .................. 90
Modifying ini File Parameters via the
AdminPage...................... 469, 606, 607, 608
Modifying the Call Progress Tones File ..... 246,
417, 501
Mounting the Mediant 3000 Chassis ...... 57, 58
MTP2 Tunneling Technology...................... 496
IPSec Configuration.............................454, 459

IPSec Table .........................................223, 254
IUA /DUA Behind NAT Support...................496
K
Key Features ...............................................309
L
Legal Notice.................................................476
Limiting the Embedded Web Server to ReadOnly Mode................................................206
List of Abbreviations ....................................615
Loading the Software Upgrade Key ....276, 278
Loading the Software Upgrade Key Using
BootP/TFTP .....................................276, 277
Loading the Software Upgrade Key Using the
Embedded Web Server............................276
Locking the Mediant 3000 Prior to Shutdown70
Log Traps (Notifications) .............................598
Logging Screen ...........................................312
N
Network Port Usage.................................... 473
Next State ................................................... 439
NFS Servers Table ............................. 389, 407
Node Maintenance................................ 70, 203
O
OAM Parameters ........................................ 565
Operating the Syslog Server....................... 284
Operation .................................................... 135
Other dependencies in ini File: ................... 479
Other Traps................................................. 599
Overview of the Mediant 3000 ...................... 23
M
Management Settings..........................223, 258
Mapping Payload Numbers to Coders ........158
Media Encryption (SRTP) using RFC 3711.152
Media Processing Parameters ............317, 337
Media Security.............................................474
Mediant 3000 Chassis ...........................30, 101
Mediant 3000 Hardware Equipment........29, 57
Mediant 3000 Hardware Installation..............57
Mediant 3000 High Availability Mode ..........280
Mediant 3000 Initialization & Configuration
Files......................................................81, 83
Mediant 3000 Management.........................185
Mediant 3000 Selected Specifications ........303
Mediant 3000 Startup ....................................83
Mediant 3000 System Initilization Process..101
Mediation .....................................................138
MEGACO (Media Gateway Control) Protocol
.................................................................134
MEGACO Compliance Matrix......................529
MEGACO Overview.....................................134
MEGACO Profiling.......................................171
MEGACO Termination Naming ...................171
MEGACO-Specific Parameters ...........317, 377
Message Log ...............................262, 265, 285
MFC R2 protocol .........................................440
MGCP Call Agent Configuration..................104
MGCP Coder Negotiation............................117
MGCP Compliance Matrix ...........................513
MGCP Control Protocol ...............................103
MGCP Endpoint Map...................................131
MGCP Fax...................................................106
MGCP KeepAlive Mechanism .....................105
MGCP Operation .........................................103
MGCP Overview..........................................103
MGCP Piggy-Back Feature .........................105
MGCP Profiling....................................106, 109
Version 4.8
P
Package Contents......................................... 58
PacketCable Audio Server Protocol
Specification PKT-SP-ASP-I02-010620
ANN-2 Interface............................... 541, 551
Parameter Value Structure ........................... 92
Parameters ................................................. 437
Parameters Common to All Control Protocols
......................................................... 317, 366
Payload Types Defined in RFC 3551 ......... 423
Payload Types Not Defined in RFC 3551... 424
PEM/DC/3K Connections ............................. 66
PEM/DC/3K Replacement ............................ 72
Performance Measurements ...................... 188
Playing the Prerecorded Tones (PRT) Auxiliary
File........................................................... 418
Possible Common Problems ...................... 288
Possible Voice Problems ............................ 289
Power............................................................ 50
Preferences Screen .................... 312, 313, 315
Preparing the Mediant 3000 for VLANs and
Multiple IPs (MI) ...................................... 561
Process Call Progress Tones file(s) ........... 501
Process CAS Tables................................... 505
Process Encoded/Decoded ini File(s)......... 509
Process Prerecorded Tones File(s) ............ 507
Process Voice Prompts file(s)..................... 502
Protocol Management................................. 213
Protocol Selection ....................................... 214
PS/DC/3K Module Replacement .................. 72
PS/DC/3K Power Supply Modules................ 53
PSTN Parameters............................... 317, 349
PSTN Settings ............................................ 231
619
January 2006
Mediant 3000
SNMP NAT Traversal ................................. 202
SNMP Parameters .............................. 317, 384
SNMP Standards and Objects.................... 185
SNMP Traps ............................................... 287
Software Directory Contents & Structure 77, 78
Software Package................................... 57, 77
Software Update ................................. 267, 510
Software Upgrade Key................ 101, 268, 275
Software Upgrade Wizard.. 100, 205, 268, 419,
491, 604, 605, 607
Solutions to Possible Problems .................. 288
Special Mediant 3000 System Specific
Behavior .................................................. 101
Specifications.............................................. 309
SS7 Characteristics .................................... 497
SS7 Configuration....................................... 236
SS7 ini File Table Parameters .................... 389
SS7 Link Set Timers ........................... 222, 238
SS7 Links............................................ 222, 238
................................................................. 478
SS7 M2UA - Media Gateway Controller Side
ini File Example ....................................... 481
SS7 M2UA - SG Side ................................. 477
SS7 M2UA - SG Side ini File Example ....... 480
SS7 MTP2 Attributes .......................... 222, 236
SS7 MTP2 Tunneling.................................. 479
SS7 MTP2 Tunneling ini File Example ....... 490
SS7 MTP3 Node ......................................... 478
SS7 MTP3 Node ini File Example .............. 486
SS7 Network Elements............................... 477
SS7 Parameters.......................... 237, 317, 364
SS7 RouteSet-Routes Table Parameters.. 389,
399
SS7 RouteSets Table Parameters...... 389, 399
SS7 Signaling LinkSet Timers Table
Parameters.............................. 238, 389, 393
SS7 Signaling LinkSets Table Parameters 389,
397
SS7 Signaling Node Timers................ 222, 237
SS7 Signaling Node Timers Table Parameters
................................................................. 391
SS7 Signaling Nodes.......................... 222, 239
SS7 Signaling Nodes Table Parameters ... 237,
240, 389
SS7 SigTran Group IDs ...................... 222, 242
SS7 SigTran Interface IDs .................. 222, 242
SS7 Tunneling
Feature Description ............................... 494
SSL/TLS...................................................... 463
Standard Control Protocols......................... 103
States Line Structure ................................. 434
States.......................................................... 432
Status and Diagnostic Menu............... 205, 262
STUN - Simple Traversal of User Datagram
Protocol ................................................... 134
Support of DiffServ Capabilities.................. 137
Support of RFC 3264.................................. 150
Supported MEGACO Packages ................. 160
PSTN Trace Utilities ....................................510

PVC Access.........................................180, 181
Q
Quick Setup ...........................................81, 211
R
RADIUS Support .........................205, 249, 466
Recommended Practices ............................476
Regional Settings ................................223, 245
Related Standards.......................................177
Removing Boards ..........................................70
Replacing the Background Image File 603, 606
Replacing the Main Corporate Logo...603, 604,
608
Replacing the Main Corporate Logo with a
Text String........................................604, 606
Replacing the Main Corporate Logo with an
Image File ................................................604
Reporting Fax Events ..................................145
Reserved Words..........................................434
Reset Button....... 214, 236, 244, 267, 275, 279
Restoring and Backing Up the Device
Configuration....................................244, 280
Restoring ini Files and Other Configuration
Files............................................................72
RFC 2833 Support.......................................142
RFC 3407 Support Simple Capabilities....147
Routing Table ......................................221, 226
RTP Media Encryption RFC 3711 Secured
RTP ..........................................................111
RTP Settings ...............................................229
S
SA/M3K Synchronization and Alarm Board...46
Sample SDP Exchanges .............................569
Save Configuration ......................204, 244, 278
Saving Changes ..........................................211
SCTP Parameters ...............................317, 386
SDP Support in MEGACO...................145, 171
SDP Support in MGCP ................................105
SDP Support Profiling..................................146
Secure Telnet ..............................................464
Secured Configuration File Download...........96
Security Settings..........................................247
Segment Description Matrix ........................549
Selecting a Coder or Ptime Using an UnderSpecified Local Descriptor .......................146
Server Certificate Replacement ..................464
Setting Up a RADIUS Server ......................467
Setup Example ............................................560
Signal List Package - SL .............................131
Silence Suppression Support ......................142
.................................................................572
.................................................................574
SNMP Interface Details ...............................195
User's Manual
620
User's Manual
32. Index
Verifying the VLANS and Multiple IP Settings
Using the Embedded Web Server........... 564
VLAN Settings..................................... 221, 227
VoATM Media Server Support.................... 177
VoATM Parameters ............................ 317, 388
VoATM Related SDP Exchange Samples &
Call Flows.......................................... 24, 569
Voice Profile Selection................................ 179
Voice Settings ..................................... 221, 227
Voice Streaming Parameters...................... 385
Supported MGCP Packages .......................120

Supporting V.34 Faxes ................................429
SVC Access (ATM AAL1)............................178
SVC Access (ATM AAL2)....................181, 192
Syslog ................................. 265, 278, 283, 285
System Parameters .......................99, 317, 318
Systems .......................................................202
T
T3 Configuration Table Parameters ....389, 408
T3 Settings ..................................................231
Table Elements............................................431
Tables of Parameter Value Structure .....92, 94,
477
TDM Bus Settings........................222, 235, 243
Template Screen .........................................316
TGCP Compatibility .....................................110
The Embedded Web Server's 'Message Log'
(Integral Syslog).......................................285
The Mediant 3000 Boards .............................31
The Mediant 3000 Chassis............................29
The Power Entry Module (PEM/DC/3K) ..51, 60
The TP-6310 Board and RTM .......................32
TP-6310 Board Panel LED Indicators ....32, 36,
101
TP-6310 Self-Test .......................................286
TPNCP Error Report....................................287
Trap Varbinds ..............................................600
Troubleshooting an Unsuccessful Loading of a
License Key .............................................278
Trunk Settings .............................212, 222, 232
TrunkPack Downloadable Conversion Utility
.................................................................499
TrunkPack-VoP Series Supported MIBs .....189
W
Web & Telnet Access List................... 223, 249
Web Interface Parameters.......... 224, 317, 381
Web Server Configuration .......................... 463
Web User Accounts .................... 206, 223, 247
U
Unpacking......................................................58
Unzipping the Software Package ..................77
Unzipping When Using a Linux/Solaris
Operating System ......................................78
Upgrading Mediant 3000 Software..91, 97, 100
User Error Messages...................................290
Using BootP/DHCP .............. 81, 82, 83, 86, 91
Using Bypass Mechanism for V.34 Fax
Transmission............................................429
Using Events Only Mechanism for V.34 Fax
Transmission............................................429
Using Internet Explorer to Access the
Embedded Web Server............................209
Using Relay Mode for Various Fax Machines
(T.30 and V.34) ........................................430
Using SNMP ..................................26, 185, 287
Using the Secure Web Server .....................464
V
Verifying that the Key was Successfully
Loaded .....................................................278
Version 4.8
621
January 2006
TrunkPack Series
Mediant 3000
TrunkPack: VoIP cPCI & PCI Boards

Mediant Media Gateways
User's Manual
www.audiocodes.com
User's Manual
622

Mediant 3000 User&#39;s Manual Ver 4.8

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Mediant 3000 User&#39;s Manual Ver 4.8

Transféré par

Droits d'auteur :

Formats disponibles

TrunkPack Series

TrunkPack: VoIP cPCI & PCI Boards

Users Manual version 4.8

Overview of the Mediant 3000 ..........................................................................23

General Features .....................................................................................24

Mediant 3000 Hardware Equipment .................................................................29

The Mediant 3000 Chassis ......................................................................29

The Mediant 3000 Boards .......................................................................31

Mediant 3000 Hardware Installation.................................................................57

Package Contents ................................................................................... 58

Mounting the Mediant 3000 Chassis......................................................58

Connecting the Earth ............................................................................... 62

Component Replacement and Maintenance .........................................69

Power Consumption ................................................................................ 51

Cooling System .......................................................................................53

The TP-6310 Board and RTM ................................................................. 32

Mediant 3000 Chassis ............................................................................. 30

Board Replacement ................................................................................. 70

Unzipping the Software Package ...........................................................77

Installing/Unzipping When Using a Windows Operating System ......... 77

Software Directory Contents & Structure..............................................78

Getting Started ..................................................................................................81

Assigning the Mediant 3000 IP Address................................................81

Assigning an IP Address Using HTTP ..................................................... 81

Assigning the IP Addresses for High Availability Mode ......................82

Mediant 3000 Initialization & Configuration Files ...........................................83

Boot Firmware & Operational Firmware ................................................83

Configuration Parameters and Files ......................................................91

BootP/DHCP Server Parameters............................................................. 86

Backup Copies of ini and Auxiliary Files.............................................100

Rebooting the Redundant TP-6310 Board ............................................ 101

6.10 Actions upon Detecting Board Failure ................................................101

Standard Control Protocols ...........................................................................103

MGCP Control Protocol ........................................................................103

MGCP Overview .................................................................................... 103

MEGACO Overview............................................................................... 134

VoATM Media Server Support ........................................................................175

Related Standards .................................................................................175

SVC Access (ATM AAL1) ...................................................................... 176

ATM AAL2 ..............................................................................................177

MGCP Coder Negotiation ...................................................................... 117

MEGACO (Media Gateway Control) Protocol ......................................134

Bearer Path Selection............................................................................ 177

Hairpinning of ATM Connections.........................................................180

Mediant 3000 Management.............................................................................183

Using SNMP ...........................................................................................183

Embedded Web Server .........................................................................202

SNMP Standards and Objects............................................................... 183

9.2.15 Restoring and Backing Up the Device Configuration............................. 278

10 Diagnostics & Troubleshooting .....................................................................281

10.4 TP-6310 Self-Test...................................................................................284

10.6 Solutions to Possible Problems...........................................................286

Key Features ......................................................................................... 307

13 Appendix - Individual ini File Parameters .....................................................315

14 Appendix - Table Parameters.........................................................................387

SS7 ini File Table Parameters ............................................................... 387

15 Appendix - Auxiliary Files ..............................................................................409

15.2 Playing the Prerecorded Tones (PRT) Auxiliary File ..........................416

16 Appendix - RTP/RTCP Payload Types...........................................................421

Payload Types Defined in RFC 3551....................................................421

17 Appendix - DTMF, Fax & Modem Transport Modes......................................425

DTMF/MF Relay Settings.......................................................................425

18 Appendix - CAS Protocol Table .....................................................................429

INIT variables......................................................................................... 429

Mediant 3000 User's Manual Ver 4.8

Mediant 3000 User's Manual Ver 4.8