AudioCodes MediaPack MP-1, MediaPack MP-124, MediaPack MP-108, MediaPack MP-104, MediaPack MP-102 User Manual
Page 1
MediaPack™ MP-1xx
Media Gateway User’s Manual
for MP-124, MP-108, MP-104 and MP-102
Version 4.0
Document #: LTRT-00714
US: AudioCodes Inc, 2890 Zanker Road, Suite # 200, San Jose, CA 95134.
Tel: 408-577-0488 - Fax: 408-577-0492
International: AudioCodes Ltd, 4 HaHoresh Street, PO Box 14, Yehud 56470, Israel.
Tel: +972-3-539 4000 - Fax: +972-3-539 4040
China: AudioCodes Ltd, Room 209 Tower A, Grand Pacific Building,
8A Guanghua Road, Chaoyang District, Beijing 100026, P.R.China
Tel: 86-10-6581-6622 - Fax: 86-10-6581-5599
Technical Support: support@audiocodes.com
Page 2
The following AudioCodes manuals should be used for additional
information:
"Software Utilities Manual", Document #: LTRT-00702.
“MP-Series Release Notes”, Document #: LTRT-00616
“VoPLib Reference Library User's Manual”, Document #: LTRT-00744.
Page 3
MP-1xx User’s Manual General
Structure of this Manual
This MP-1xx User’s Manual has the following sections:
FCC Compliance, Notices, Conformity and Warranty
3
Contents, Figures and Tables 7
1. Overview and Features 15
2. MP-10x Hardware Installation 21
3. MP-124 Hardware Installation 31
4. Software Installation 41
5. Operation & Configuration 65
6. Management 99
7. Provisioning 111
8. GUI Demo Application 127
9. Diagnostics 129
10. Specifications 147
Appendix A - BootP Server Config. Tool Demo 155
Appendix B - DHCP Server Configuration 155
Appendix C - BootP Server Installation & Configuration 155
Appendix D - TFTP Server Installation & Configuration 156
Appendix E - MGCP Compliance Matrix 156
Appendix F - RTP/RTCP Payload Types 156
Appendix G - DTMF, Fax & Modem Modes 156
Abbreviations and Terminology
Each abbreviation, unless widely used, is spelled out in full when first used,
and only Industry standard terms are used throughout this manual. The $
symbol indicates hexadecimal notation.
Trademarks
AC, AudioCoded, AudioCodes, AudioCodes logo, IPmedia, Mediant,
MediaPack, NetCoder, Stretto, TrunkPack and VoicePacketizer, are
trademarks or registered trademarks of AudioCodes Limited.
All other products or trademarks are property of their respective owners.
Version 4.0 3 October 2002
Page 4
MP-1xx
Notice
This MP-1xx User’s Manual describes the AudioCodes MediaPack MP-124 24-
port, MP-108 8-port, MP-104 4-port and MP-102 2-port Media Gateways, referred
to collectively as the MP-1xx enabling Users to send voice fax and data over the
same IP network.
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.
For Technical Support please contact:
e-mail: support@audiocodes.com
In the US, fax 408-577-0492
In other countries, fax +972-3-539-4040
© Copyright 2002 AudioCodes Ltd. All rights reserved
This document is subject to change without notice.
Date Published: Oct-21-2002 Date Printed: Oct-31-2002
Regulatory Information
General
This regulatory information document is provided in accordance with standards UL 1950, EN
60950 and 47 CFR, part 15, for the Analog Media Gateway product family.
The safety status of each port on the gateway is declared and detailed in the table below:
Ports Safety Status
Ethernet (100 Base-T)
FXS (ODP P/N’s)
FXS
TNV-3: Circuit whose normal operating voltages exceeds the limits for an SELV circuit under
normal operating conditions and on which over voltages from Telecommunication Networks are
possible
TNV-2: Circuit whose normal operating voltages exceeds the limits for an SELV circuit under
normal operating conditions and is not subjected to over voltages from Telecommunication
Networks
SELV: Safety extra low voltage circuit.
SELV
TNV-3
TNV-2
MP-1xx User’s Manual 4 Document #: LTRT-00714
Page 5
MP-1xx User’s Manual General
FCC Notice to Users
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to
part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful
interference in a residential installation. This equipment generates, uses and can radiate radio frequency
energy and, if not installed and used in accordance with the instructions, may cause harmful interference to
radio communications. However, there is no guarantee that interference will not occur in a particular
installation. If this equipment does cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the User is encouraged to try to correct the interference by
one or more of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation between the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help.
Declaration of Conformity
We AudioCodes Ltd
Declare under our sole responsibility that the products:
MP-1xx/FXS
(where xx can represent 02, 04,08 or 24)
To which this declaration relates, is in conformity with the following standards: EN 55022 1998, EN 50024
1998, EN 60950 1992 + Amendments 1, 2, 3 & 4
As described in the European Directives: 89/336 (EMC),
73/23 (Safety),
93/68 (Safety).
Yehud, Israel, September 4, 2002
Israel Zusmanovich
Compliance Eng.
Este producto està en conformidad con la directiva Europea 89/336, 73/23, 93/68
Dette produkt er i overensstemmelse med Europæiske Direktiver 89/336, 73/23, 93/68
Dieses Produkt ist konform mit der europäischen Richtlinie 89/336, 73/23, 93/68
Ce produit est conforme aux exigences de la Directive européenne 89/336, 73/23, 93/68
Questo prodotto è conforme con la normativa europea 89/336, 73/23, 93/68
Este producto està em conformidade com as Diretrizes Européia 89/336, 73/23, 93/68
Tuote on eurooppalaisen säännöstön mukainen 89/336, 73/23, 93/68
Denna product följer europeiska direktiv 89/336, 73/23, 93/68
Το προιόν, είναι σύµφωνο µε τους κανονισµούς της Ευρωπαικής Κοινώτητας 89/336, 73/23, 93/68
Tæki þetta er í samræmi við tilskipun Evrópusambandsins 89/336, 73/23, 93/68
Dette produktet er i samhørighet med det Europeiske Direktiv 89/336, 73/23, 93/68
Version 4.0 5 October 2002
Page 6
MP-1xx
Safety Notice
Installation and service of AudioCodes’ Media Gateways must be performed by
authorized, qualified service personnel only.
General Warranty
AudioCodes Ltd. (hereinafter "AudioCodes") warrants that its Products (hereinafter
"Products") shall conform to AudioCodes’ published specifications for a period of one (1)
year. The foregoing warranty does not apply to any Products which have been subject to
misuse, neglect, accident, or modification or which have been altered and are not capable of
being tested by AudioCodes under its normal test conditions. AudioCodes’ sole obligation to
the Purchaser (hereinafter "Buyer") hereunder for Products failing to meet the aforesaid
warranty shall be, at AudioCodes' discretion, to replace the non-conforming Products or
issue the Buyer credit for the purchase price of the non-conforming Products, where within
the warranty period: 1) AudioCodes has received written notice of any nonconformity; and 2)
After AudioCodes' written authorization to do so the Buyer has returned the non-conforming
Products to AudioCodes, freight prepaid; and 3) AudioCodes has determined that the
Products are non-conforming and that such nonconformity is not a result of the Buyer’s
conduct. No Products may be used in a life support application. AudioCodes warrants
that the Products sold hereunder shall at the time of shipment be free and clear of liens and
encumbrances. This warranty extends to the Buyer only and may be invoked by the Buyer
for its customers. AudioCodes shall not accept warranty returns directly from the Buyer’s
customers or users of the Buyer’s products or devices. This warranty is in lieu of all other
warranties whether express, implied or statutory including implied warranties of
merchantability or fitness for particular purpose. AudioCodes shall not be liable for damages
due to delays in deliveries or use. In no event shall AudioCodes be liable for any incidental
or consequential damages due to breach of this warranty or for any infringement action
initiated by a third party. The Buyer’s sole remedy for any breach shall be limited to the
remedies set forth herein and shall not exceed the sale price for the Products.
MP-1xx User’s Manual 6 Document #: LTRT-00714
Page 7
MP-1xx User’s Manual Contents
Table of Contents
FCC Compliance, Notices, Conformity and Warranty ...........................4
1....Overview ...........................................................................................15
1.1 Introduction ........................................................................................................ 17
1.2 Gateway Description.......................................................................................... 17
1.3 MP-1xx Key Features ........................................................................................ 20
2
M
P
-
1
0
x
H
a
r
d
w
a
r
e
I
n
s
t
a
l
l
a
t
i
o
2
M
P
-
1
0
x
H
a
r
d
w
a
r
e
I
n
s
t
2
M
P
-
1
0
x
H
a
r
d
w
a
r
e
2.1 MP-10x Hardware Installation Procedure .......................................................... 23
2.1.1 Unpacking................................................................................................ 23
2.1.2 MP-10x Rack Mounting ........................................................................... 24
2.1.3 MP-10x Desktop Mounting ...................................................................... 25
2.1.4 Cable Connections .................................................................................. 26
2.2 Front Panel LED Indicators................................................................................ 27
2.3 Rear Panel LED Indicators and Connectors...................................................... 29
2.4 Installation of the Life Line on FXS only ............................................................ 30
a
I
n
s
t
a
3 MP-124 Hardware Installation..........................................................31
n
l
l
a
t
i
o
n
l
l
a
t
i
o
n
..........................................................21
3.1 MP-124 Hardware Installation Procedure.......................................................... 33
3.1.1 Unpacking................................................................................................ 33
3.1.2 MDF Adaptor ........................................................................................... 33
3.1.3 MP-124 Cable Connections..................................................................... 35
3.1.4 MP-124 19-inch Rack Mounting .............................................................. 36
3.2 MP-124 Front Panel LED Indicators .................................................................. 38
3.3 MP-124 Rear LED Indicators/Connectors ......................................................... 39
4 Software Installation.........................................................................41
4.1 Software Installation Procedure ......................................................................... 43
4.1.1 MP-1xx Initialization (BootP, TFTP) ........................................................ 43
4.1.2 MP-1xx Initialization................................................................................. 45
4.1.2.1 Command Line Switches ...................................................................... 45
4.1.3 MP-1xx Software Upgrade Procedure..................................................... 46
4.1.4 AudioCodes’ BootP/TFTP Server Configuration Tool ............................. 46
4.1.5 Microsoft™ DHCP/BootP Server .............................................................. 47
4.1.6 Third Party TFTP & BootP Servers ......................................................... 47
4.2 The ini File Structure.......................................................................................... 48
4.2.1 The ini File Structure Rules ..................................................................... 48
4.2.2 The ini File Example ................................................................................ 49
4.3 Call Progress Tones & Distinctive Ringing ........................................................ 50
4.3.1 Format of the Call Progress Tones Section ............................................ 50
Version 4.0 7 October 2002
Page 8
MP-1xx
Table of Contents (continued)
4.3.2 Format of the Distinctive Ringing Section ............................................... 52
4.3.3 Default Template for Call Progress Tones .............................................. 54
4.3.4 Default Template for Distinctive Ringing Patterns .................................. 58
4.3.5 Call Progress Tone Generation and Download Procedure ..................... 62
4.4 The coeff.dat Configuration File ........................................................................ 64
5 Operation & Configuration .............................................................. 65
5.1 General .............................................................................................................. 67
5.2 MGCP Control Protocol ..................................................................................... 68
5.2.1 MGCP Overview...................................................................................... 68
5.2.2 Operation................................................................................................. 68
5.2.3 MGCP Call Agent IP Address ................................................................. 68
5.2.4 MP-1xx Compression Codecs................................................................. 69
5.2.5 Supported MGCP Packages ................................................................... 70
5.2.5.1 DTMF Package - D ............................................................................... 70
5.2.5.2 Generic Media Package - G ................................................................. 71
5.2.5.3 Line Package - L ................................................................................... 71
5.2.5.4 PacketCable (NCS) Line Package - L .................................................. 72
5.2.5.5 Announcement Package - L ................................................................. 73
5.3 MEGACO Protocol............................................................................................. 74
5.3.1 MEGACO Overview ................................................................................ 74
5.3.2 MEGACO Operation................................................................................ 74
5.3.2.1 Executing MEGACO Commands.......................................................... 74
5.3.2.2 Setting MEGACO Call Agent IP Address and Port............................... 75
5.3.2.3 Handling Events.................................................................................... 75
5.3.2.4 Playing Signals ..................................................................................... 76
5.3.2.5 SDP Support in MEGACO .................................................................... 77
5.3.2.6 Mapping of payload numbers to coders ............................................... 78
5.3.3 Supported MEGACO Packages .............................................................. 81
5.3.3.1 Generic Media Package: G................................................................... 81
5.3.3.2 Base Root Package: ROOT.................................................................. 82
5.3.3.3 Tone Generator Package: ToneGen .................................................... 82
5.3.3.4 Tone Detection Package: ToneDet ...................................................... 82
5.3.3.5 DTMF Generator Package: DG (Extends ToneGen)............................ 83
5.3.3.6 DTMF Detection Package: DD (Extends ToneDet) .............................. 84
5.3.3.7 Call Progress Tone Generator Package- CG (Extends ToneGen) ......85
5.3.3.8 Call Progress Tones Detection Package- CD (Extends ToneDet) ....... 85
5.3.3.9 Analog Line Supervision Package - AL ................................................ 86
5.3.3.10 Network Package- NT .................................................................... 86
5.3.3.11 RTP Package- RTP (Extends: NT) ................................................ 86
5.3.3.12 TDM Circuit Package – TDMC (Extends - NT) .............................. 87
MP-1xx User’s Manual 8 Document #: LTRT-00714
Page 9
MP-1xx User’s Manual Contents
Table of Contents (continued)
5.3.3.13 Generic Announcement Package - AN .......................................... 87
5.3.3.14 Expanded Call Progress Tones Generator Package - XCG (Extends
- ToneGen) ........................................................................................................ 87
5.3.3.15 Basic Service Tones Generation Package - SRVTN (Extends -
ToneGen) ........................................................................................................ 88
5.3.3.16 Expanded Services Tones Generation Package - XSRVTN
(Extends - ToneGen) ......................................................................................... 88
5.3.3.17 Enhanced Alerting Package - ALERT ............................................ 88
5.3.3.18 Analog Display Signaling Package – ANDISP (Extends: ALERT). 89
5.3.3.19 Extended Analog Line Supervision Package – XAL (Extends: AL) 89
5.3.3.20 FXO Package - FXO....................................................................... 89
5.3.4 MEGACO Terminations Naming ............................................................. 90
5.4 TPNCP Profile.................................................................................................... 91
5.4.1 TPNCP Overview .................................................................................... 91
5.4.2 VoP Library Functions ............................................................................. 91
5.4.2.1 Library Initialization/Cleanup Functions ................................................ 91
5.4.2.2 Board Configuration Functions ............................................................. 91
5.4.2.3 Channel Configuration Functions ......................................................... 92
5.4.2.4 IVR-Supporting Functions ..................................................................... 93
5.4.2.5 RTP/RTCP-Related Functions .............................................................. 93
5.4.2.6 Event Handling Functions ..................................................................... 94
5.4.2.7 Analog Interface Control Functions ...................................................... 94
5.4.2.8 TFTP Server Related Functions ........................................................... 95
5.4.2.9 Auxiliary Functions ................................................................................ 95
5.4.2.10 Callback Functions ......................................................................... 95
5.4.2.11 Operating System Wrapper Functions ........................................... 96
5.4.3 IP-Media Library ...................................................................................... 97
5.4.4 VoATM Library......................................................................................... 97
5.4.5 PSTN Library Functions .......................................................................... 97
6 Management......................................................................................99
6.1 SNMP Management ........................................................................................ 101
6.1.1 SNMP Overview .................................................................................... 101
6.1.2 SNMP Message Standard ..................................................................... 101
6.1.3 SNMP MIB Objects................................................................................ 102
6.1.4 SNMP Extensibility Feature................................................................... 103
6.1.5 MP-1xx Supported MIBs........................................................................ 104
6.2 Embedded Web Server ................................................................................... 105
6.2.1 Overview................................................................................................ 105
6.2.2 Password Control .................................................................................. 105
6.2.2.1 The Embedded Web Server Username-Password............................. 105
Version 4.0 9 October 2002
Page 10
MP-1xx
Table of Contents (continued)
6.2.2.2 Authentication Method ........................................................................ 106
6.2.3 Web Configuration................................................................................. 106
6.2.3.1 Read-only Mode.................................................................................. 106
6.2.3.2 Disable/Enable Embedded Web Server ............................................. 106
6.2.4 Using the Embedded Web Server......................................................... 107
6.2.4.1 Set up Device Configuration Parameters ........................................... 108
6.2.5 Channel Information Menu .................................................................... 109
7 MP-1xx Provisioning...................................................................... 111
7.1 MP-1xx Provisioning for Operation of Control Protocols ................................. 113
7.2 MP-1xx Provisioning for MGCP & MEGACO Operation ................................. 115
7.3 MP-1xx Default Settings .................................................................................. 118
7.3.1 Default MGCP/MEGACO Channel Parameters .................................... 118
7.3.2 Default RTP/RTCP/T.38 Port Allocation ............................................... 123
7.4 MP-1xx Provisioning for TPNCP Operation .................................................... 124
7.5 Loading Configuration Files ............................................................................. 125
8 GUI Demo Application ................................................................... 127
9 Diagnostics..................................................................................... 129
9.1 Diagnostics Overview ...................................................................................... 131
9.2 Troubleshooting MP-1xx Devices with HyperTerminal.................................... 132
9.2.1 Connecting the MP-1xx to a HyperTerminal ......................................... 132
9.2.2 Configuring HyperTerminal ................................................................... 132
9.2.3 Assessing MP-1xx Software Using HyperTerminal............................... 133
9.2.4 Determining MP-1xx Initialization Problems.......................................... 134
9.2.5 Reinitializing the MP-1xx ....................................................................... 135
9.3 Alarms.............................................................................................................. 139
9.3.1 Visual Front Panel LED Indicators ........................................................ 139
9.3.2 Rear Panel LED Indicators.................................................................... 139
9.4 MP-1xx Self-Testing ........................................................................................ 141
9.5 Control Protocol Reports ................................................................................. 142
9.5.1 Error Indications through the Network Interface.................................... 142
9.5.2 TPNCP Error Report ............................................................................. 142
9.5.3 MGCP/MEGACO Error Conditions ....................................................... 142
9.5.4 SNMP Traps .......................................................................................... 142
9.6 SysLog Support ............................................................................................... 143
9.6.1 SysLog Overview .................................................................................. 143
9.6.2 SysLog Operation.................................................................................. 143
9.6.2.1 Sending SysLog Messages ................................................................ 143
9.6.2.2 Setting the SysLog Server IP Address ............................................... 144
MP-1xx User’s Manual 10 Document #: LTRT-00714
Page 11
MP-1xx User’s Manual Contents
Table of Contents (continued)
9.6.2.3 Controlling the Activation of the SysLog Client ................................... 144
9.6.2.4 The ini File Example for SysLog ......................................................... 144
9.7 Solutions to Possible Problems ....................................................................... 145
9.7.1 Solutions to Voice Problems ................................................................. 146
10 Specifications .................................................................................147
10.1 MP-1xx Specifications and Functionality ......................................................... 149
Appendices ...........................................................................................153
Appendix A..- BootP/TFTP Configuration Utility ...............................155
Appendix B..- Windows™ DHCP Server Configuration ....................155
Appendix C..- BootP Server Configuration ........................................155
Appendix D..- TFTP Server Configuration..........................................156
Appendix E..- MGCP Compliance Matrix............................................156
Appendix F ..- RTP/RTCP Payload Types ...........................................156
Appendix G..- DTMF, Fax & Modem Modes........................................156
Version 4.0 11 October 2002
Page 12
MP-1xx User’s Manual Contents
List of Figures
Figure 1-1: MP-108 Front View........................................................................................................ 18
Figure 1-2: MP-104 Front View........................................................................................................ 18
Figure 1-3: MP-102 Front View........................................................................................................ 18
Figure 1-4: MP-124 VoIP Gateway.................................................................................................. 18
Figure 1-5: Typical MP-1xx VoIP Application................................................................................... 19
Figure 2-1: MP-1xx Rack Mounting ................................................................................................. 24
Figure 2-2: MP-10x Desktop or Shelf .............................................................................................. 25
Figure 2-3: RJ-45 and RJ-11 Connectors and Pinouts.................................................................... 26
Figure 2-4: MP-1xx Front Panel LED Indicators .............................................................................. 27
Figure 2-5: Rear Panel LED Indicators and Connectors.................................................................. 29
Figure 2-6: RJ-11 Connector and Life Line Pinout for MP-10x/FXS ................................................ 30
Figure 3-1: MP-124 in a 19-inch Rack with MDF Adaptor ............................................................... 34
Figure 3-2: 50-pin Telco Connector................................................................................................. 35
Figure 3-3: RJ-45 and RJ-11 Connectors and Pinouts.................................................................... 36
Figure 3-4: MP-124 with 19-inch Rack Mounting Ears ....................................................................36
Figure 3-5: Front Panel LED Indicators ........................................................................................... 38
Figure 3-6: MP-124 Rear Panel LED Indicators and Connectors .................................................... 39
Figure 4-1: MP-1xx Initialization Procedure..................................................................................... 44
Figure 4-2: ini File Structure ............................................................................................................ 48
Figure 4-3: ini File Example............................................................................................................. 49
Figure 4-4: Download Selection Screen .......................................................................................... 62
Figure 4-5: File Selection Screen .................................................................................................... 63
Figure 6-1: Embedded Web Server – Home Page ........................................................................ 107
Figure 6-2: Embedded Web-Server - Device Parameters ............................................................. 108
Figure 6-3: Embedded Web Server - Channel Information............................................................ 109
Figure 6-4: Embedded Web Server - Channel Status ................................................................... 110
Figure 9-1: RS-232 Cable Wiring................................................................................................... 132
Figure 9-2: HyperTerminal Main Screen........................................................................................ 134
Figure 9-3: AudioCodes BootP/TFTP Server Main Screen............................................................ 136
Figure 9-4: Client Configuration..................................................................................................... 136
Figure 9-5: Preferences Screen..................................................................................................... 137
Figure 9-6: AudioCodes BootP/TFTP Server - Client Found ......................................................... 138
Figure 9-7: The ini File Example for SysLog.................................................................................. 144
MP-1xx User’s Manual 12 Document #: LTRT-00714
Page 13
MP-1xx User’s Manual Contents
List of Tables
Table 2-1: Front Panel Network LED Indicators & Restart............................................................... 27
Table 2-2: MP-108 Channel LEDs ...................................................................................................28
Table 2-3: MP-104 Channel LEDs ...................................................................................................28
Table 2-4: MP-102 Channel LEDs ...................................................................................................28
Table 2-5: Meaning of Rear Panel LED Indicators...........................................................................29
Table 2-6: Explanation of Rear Panel Connectors/Switches............................................................29
Table 3-1: Pin Allocation in 50-pin Telco Connector ........................................................................35
Table 3-2: Function of Front Panel LED Indicators.......................................................................... 38
Table 3-3: Function of Rear Panel LED Indicators...........................................................................39
Table 3-4: Function of Rear Panel Connectors/Switches.................................................................40
Table 4-1: Output Tone Levels ........................................................................................................ 52
Table 4-2: Call Progress Tones (continues on pages 54 to 57)....................................................... 54
Table 4-3: Number Of Distinctive Ringing Patterns (continues on pages 58 to 61) .........................58
Table 5-1: MP-1xx Compression Codecs ........................................................................................69
Table 5-2: DTMF Package - D.........................................................................................................70
Table 5-3: Generic Media Package - G............................................................................................ 71
Table 5-4: Line Package - L.............................................................................................................71
Table 5-5: PacketCable (NCS) Line Package - L.............................................................................72
Table 5-6: Announcement Package - L............................................................................................73
Table 5-7: MGCP/MEGACO Mapping of Payload Numbers to Coders ........................................... 78
Table 5-8: Generic Media Package: G............................................................................................. 81
Table 5-9: Base Root Package: ROOT............................................................................................ 82
Table 5-10: Tone Generator Package: ToneGen.............................................................................82
Table 5-11: Tone Detection Package: ToneDet............................................................................... 82
Table 5-12: DTMF Generator Package: DG ....................................................................................83
Table 5-13: DTMF Detection Package: DD......................................................................................84
Table 5-14: Call Progress Tones Generator Package- CG..............................................................85
Table 5-15: Call Progress Tones Detection Package- CD............................................................... 85
Table 5-16: Analog Line Supervision Package- AL..........................................................................86
Table 5-17: Network Package- NT................................................................................................... 86
Table 5-18: RTP Package- RTP ...................................................................................................... 86
Table 5-19: TDM Circuit Package - TDMC ......................................................................................87
Table 5-20: Generic Announcement Package .................................................................................87
Table 5-21: Expanded Call Progress Tones Generator Package - XCG .........................................87
Table 5-22: Basic Service Tones Generation Package - SRVTN .................................................... 88
Table 5-23: Expanded Services Tones Generation Package - XSRVTN......................................... 88
Table 5-24: Enhanced Alerting Package - ALERT...........................................................................88
Table 5-25: Analog Display Signaling Package - ANDISP...............................................................89
Table 5-26: Extended Analog Line Supervision Package- XAL ....................................................... 89
Table 5-27: FXO Package – FXO .................................................................................................... 89
Table 5-28: Library Initialization/Cleanup Functions ........................................................................ 91
Table 5-29: Board Configuration Functions ..................................................................................... 91
Table 5-30: Channel Configuration Functions..................................................................................92
Table 5-31: IVR-Supporting Functions............................................................................................. 93
Table 5-32: RTP/RTCP-Related Functions......................................................................................93
MP-1xx User’s Manual 13 Document #: LTRT-00714
Page 14
MP-1xx
Table 5-33: Event Handling Functions............................................................................................. 94
Table 5-34: Analog Interface Control Functions .............................................................................. 94
Table 5-35: TFTP Server Related Functions ................................................................................... 95
Table 5-36: Auxiliary Functions ....................................................................................................... 95
Table 5-37: Callback Functions ....................................................................................................... 95
Table 5-38: Operating System Wrapper Functions.......................................................................... 96
Table 7-1: MP-1xx Basic Configuration Parameters...................................................................... 114
Table 7-2 MGCP Specific Parameters (continues on pages 115 to 116) ......................................115
Table 7-3: MEGACO-Specific Parameters .................................................................................... 117
Table 7-4: MGCP/MEGACO Default Channel Parameters (on pages 119 to 123)........................ 119
Table 7-5: Default RTP/RTCP/T.38 Port Allocation....................................................................... 123
Table 9-1: Possible Initialization Problems.................................................................................... 134
Table 9-2: Meaning of Front Panel LED Indicators........................................................................ 139
Table 9-3: Meaning of Rear Panel LED Indicators (continues on pages 139 to 140) .................... 139
Table 9-4: Solutions to Problems (continues on pages 145 to 146) .............................................. 145
Table 9-5: Solutions to Possible Voice Problems .......................................................................... 146
Table 10-1: MP-1xx Specifications (continues on pages 149 to 151)............................................ 149
MP-1xx User’s Manual 14 Document #: LTRT-00714
Page 15
MP-1xx User’s Manual 1. Overview
1
1
1
O
O
O
v
v
v
e
e
e
r
r
r
v
v
v
i
i
i
e
e
e
w
w
w
Version 4.0 15 October 2002
Page 16
MP-1xx
Note 1: The MP-124 24-port, MP-108 8-port, MP-104 4-port and MP-102 2-port
Media Gateways have similar functionality except for the number of channels
(the MP-124 and MP-102 support only FXS), and all versions are referred to
collectively in these release notes as the MP-1xx.
Note 2: MP-10x refers to MP-108 8-port, MP-104 4-port and MP-102 2-port
gateways.
Note 3: MP-1xx/FXS refers only to the MP-124/FXS, MP-108/FXS, MP-104/FXS and
MP-102/FXS gateways.
Note 4: MP-10x/FXO refers only to MP-108/FXO and MP-104/FXO gateways.
This section describes the features and functionality of the
MP-124, MP-108, MP-104 and MP-102 telephony Media
Gateways
The section has the following subsections:
1.1 Introduction ........................................................................................................ 17
1.2 Gateway Description ......................................................................................... 17
1.3 MP-1xx Key Features ........................................................................................ 20
MP-1xx User’s Manual 16 Document #: LTRT-00714
Page 17
MP-1xx User’s Manual 1. Overview
1.1 Introduction
This User’s Manual provides you with information on installation,
configuration, and operation of the MP-124 24-port, MP-108 8-port, MP-104 4port and MP-102 2-port Media Gateways. As these units have similar
functionality (except for the number of channels and some minor features),
they are referred to collectively as the MP-1xx. It is expected that Readers are
familiar with regular telephony and data networking concepts.
1.2 Gateway Description
AudioCodes’ MP-1xx telephony Media Gateway provides excellent voice
quality and optimized packet voice streaming over IP networks, enabling
voice, fax, and data traffic to be sent over the same IP network.
Based on AudioCodes’ award-winning, field-proven TrunkPack design, the
MP-1xx uses AudioCodes’ well-established DSP voice compression
technology.
The MP-1xx incorporates up to 24 analog ports for connection, either directly
to an enterprise PBX (MP-10x/FXO), and to phones or fax (MP-1xx/FXS),
supporting up to 24 simultaneous VoIP calls. Additionally, the MP-1xx is
equipped with a 10/100 Base-T Ethernet port for connection to the LAN.
MP-1xx Gateways are best suited for small to medium-sized enterprises,
branch offices or for residential Media Gateway solutions.
MP-1xx Gateways enable Users to make free local or international
telephone/fax calls between distributed company offices, using their existing
telephones/fax. These calls are routed over the existing IP Internet or Intranet
corporate data networks ensuring that voice traffic takes the minimum of
space on the data network.
MP-1xx Gateways are compact devices, designed to be installed either as a
desk-top unit (shown in Figure 1-1 to Figure 1-4 on page 18) or installed in a
19-inch rack (see Figure 2-1).
The MP-1xx supports MGCP (Media Gateway Control Protocol) and
MEGACO (Me
enabling the use of "voice over packet" solutions in environments where each
enterprise or residential location is provided with a simple Media Gateway.
This provides the enterprise with a telephone connection (e.g., RJ-11), and
the ability to transmit voice and telephony signals over a packet network. The
Media Gateways are controlled by a Media Gateway Controller MGC (or Call
Agent) that performs the routing of the calls.
Additionally, for emergency use, the MP-10x/FXS provides a Life Line, connected to
the unused pins on port #4, (MP-102/FXS uses port #2) with a relay to an analog line,
even if the
The layout in Figure 1-5 on page 19 illustrates an MP-1xx VoIP application.
dia Gateway Control) Protocol (ITU H.248 and RFC 3015),
MP-10x is powered off.
Version 4.0 17 October 2002
Page 18
MP-1xx
Figure 1-1: MP-108 Front View
Figure 1-2: MP-104 Front View
Figure 1-3: MP-102 Front View
Figure 1-4: MP-124 VoIP Gateway
MP-1xx User’s Manual 18 Document #: LTRT-00714
Page 19
MP-1xx User’s Manual 1. Overview
Figure 1-5: Typical MP-1xx VoIP Application
Version 4.0 19 October 2002
Page 20
MP-1xx
1.3 MP-1xx Key Features
• High quality Voice, Data and Fax over IP networks.
• MP-124 supports up to 24 analog telephone loop start FXS ports as
shown in Figure 1-4 on page 18.
• MP-108 supports up to 8 analog telephone loop start FXS or FXO ports
as shown in Figure 1-1 on page 18.
• MP-104 supports up to 4 analog telephone loop start FXS or FXO ports
as shown in Figure 1-2 on page 18.
• MP-102 supports up to 2 analog telephone loop start FXS ports as shown
in Figure 1-3 on page 18.
• Connected to the IP network via a 10/100 Base-T Ethernet interface.
• Coders include: G.711, G.723.1, G.726, G.727, G.729A, and NetCoder at
6.4 to 9.6 kbps, selectable per channel.
• T.38 Fax with superior performance (round trip delay up to 9 sec).
• Compliant with MGCP (RFC 2705), MEGACO (H.248) and PacketCable
NCS protocols.
• The FXO version can be controlled remotely using the AudioCodes
proprietary TPNCP (TrunkPack Network Control Protocol) API library.
• The FXS version can be controlled remotely using either MGCP,
MEGACO (ITU H.248 and RFC 3015), or the AudioCodes proprietary
TPNCP (TrunkPack Network Control Protocol) API library.
• Life Line, connected to the unused pins on port #4, (MP-102 uses port
#2) with a relay to an analog line, even if the MP-10x/FXS is powered off.
• LEDs on the front and rear panels provide information on the operating
Media Gateway status and of the network interface.
• Restart button on the Front panel restarts the MP-1xx.
• MP-10x has a compact, rugged enclosure providing up to 8 analog RJ-11
ports within a compact housing of only one-half of a 19-inch rack unit, 1 U
high (1.75" or 44.5 mm).
• Mounting option of installing two MP-10x Gateways in a single 19-inch
rack shelf, 1 U high (1.75" or 44.5 mm).
• MP-124 19-inch, 1 U rugged enclosure provides up to 24 analog FXS
ports, using single 50-pin Telco connector.
MP-1xx User’s Manual 20 Document #: LTRT-00714
Page 21
MP-1xx User’s Manual 3. Software Installation
2
2
2
M
M
M
P
P
P
-
-
-
1
1
1
0
0
0
x
x
x
H
H
H
I
I
I
a
n
n
n
a
a
s
s
s
r
r
r
t
t
t
d
d
d
a
a
a
w
w
w
l
l
a
l
l
l
l
a
a
a
a
a
r
t
t
t
r
r
i
i
i
e
e
e
o
o
o
n
n
n
Version 4.0 21 October 2002
Page 22
MP-1xx
This section is the installation of the MP-108, MP-104 and
MP-102.
The MP-124 installation is described in Section 3
Note 1: The MP-124 24-port, MP-108 8-port, MP-104 4-port and MP-102 2-port
Media Gateways have similar functionality except for the number of channels
(the MP-124 and MP-102 support only FXS), and all versions are referred to
collectively in these release notes as the MP-1xx.
Note 2: MP-10x refers to MP-108 8-port, MP-104 4-port and MP-102 2-port
gateways.
Note 3: MP-1xx/FXS refers only to the MP-124/FXS, MP-108/FXS, MP-104/FXS and
MP-102/FXS gateways.
Note 4: MP-10x/FXO refers only to MP-108/FXO and MP-104/FXO gateways.
This section has the following subsections:
Hardware Installation Procedure ................................. 23
Front Panel LED Indicators .......................................... 27
Rear Panel LED Indicators and Connectors ................29
Installation of the Life Line ...........................................30
MP-1xx User’s Manual 22 Document #: LTRT-00714
Page 23
MP-1xx User’s Manual 3. Software Installation
2.1 MP-10x Hardware Installation Procedure
2.1.1 Unpacking
To unpack the MP-10x:
• Open the carton and remove packing materials
• Remove the MP-10x from the carton
• Check that there is no equipment damage
• Check, retain and process any documents
• Notify AudioCodes of any damage or discrepancies
• Retain any diskettes or CDs
Safety Notice
Installation and service of this device must only be performed by authorized, qualified
service personnel.
Version 4.0 23 October 2002
Page 24
MP-1xx
2.1.2 MP-10x Rack Mounting
Figure 2-1: MP-1xx Rack Mounting
The MP-10x is installed into a standard 19-inch rack by the addition of the 2
brackets supplied (shown above).
To install the MP-10x, take the following steps:
1. Fasten the short bracket to the right-hand side of the MP-10x using
the 2 screws provided, as shown in Figure 2-1, and carefully
positioning the peg into a convenient ventilation hole in the side of
the MP-10x box.
2. Fasten the long bracket to the left-hand side of the MP-10x using
the 2 screws provided as shown in Figure 2-1, and carefully
positioning the peg into a convenient ventilation hole in the side of
the MP-10x box.
3. Insert the MP-10x into the 19-inch rack and fasten the left-hand
and right-hand brackets to the vertical tracks of the 19-inch rack,
using standard 19-inch rack bolts (not provided).
To connect the cables go to Step 4 (Section 2.1.4 on page 26)
MP-1xx User’s Manual 24 Document #: LTRT-00714
Page 25
MP-1xx User’s Manual 3. Software Installation
2.1.3 MP-10x Desktop Mounting
Figure 2-2: MP-10x Desktop or Shelf
The MP-10x is installed on a desk or shelf, without additional brackets, as
shown above.
To connect the cables, go to Step 4 (Section 2.1.4 on page 26)
Version 4.0 25 October 2002
Page 26
MP-1xx
2.1.4 Cable Connections
The RJ-45 (Ethernet) and RJ-11 (POTS) pinouts and connectors are shown in
Figure 2-3, and pins are numbered from the left with the latching finger
position at the bottom.
Figure 2-3: RJ-45 and RJ-11 Connectors and Pinouts
RJ-45 Connector and Pinout
1 2 3 4 5 6 7 8
To connect the cables for desktop or rack mount, go to
Step 4 When using MP-10x/FXS gateway, insert each of the RJ-11
1 - Tx+
2 - Tx3 - Rx+
6 - Rx-
4, 5, 7, 8
not
connected
Step 4 below:
connectors on the 2-wire line cords of the POTS phones into the
RJ-11 sockets on the rear of the gateway.
RJ-11 Connector and Pinout
1 2 3 4
Not connected
1 2 -
Tip
3 -
Ring
Not connected
4 -
When using MP-10x/FXO gateway, insert each of the RJ-11
connectors on the 2-wire line cords coming from PSTN/PBX into
the RJ-11 sockets on the rear of the gateway.
Telephone lines and extensions of up to 7,300 m (24,000 ft) can be
achieved using regular 24 AWG line cord with the MP-10x/FXO.
Telephone extensions of up to 3,000m (10,000 ft) can be achieved
using regular 24 AWG line cord with the MP-10x/FXS.
Step 5 Insert the RJ-45 connector on the 10/100 Base-T cable from your
LAN to the ETH RJ-45 socket (on the rear of the MP-10x) to
provide the link to your LAN.
Step 6 Connect the MP-10x Gateway to the correct AC power supply; the
installation is now complete.
The front panel LEDs indicate the activity of the MP-1xx, and the attached
devices.
MP-1xx User’s Manual 26 Document #: LTRT-00714
Page 27
MP-1xx User’s Manual 3. Software Installation
2.2 Front Panel LED Indicators
The MP-10x front panel LEDs indicate the Ethernet LAN status, Data (RTP)
activity and state of the MP-1xx ports.
Figure 2-4: MP-1xx Front Panel LED Indicators
Restart
Button
Functionality of the MP-10x Front Panel Network LEDs is described in Table
2-1.
Table 2-1: Front Panel Network LED Indicators & Restart
Label Type Color State Meaning
LAN
Data
Control
Ready
-
Ethernet
Link Status
Packet
Status
Control
Link
Device
Status
Restart
Green
Red
Green
Red
Blank
Green
Red
Orange
Green
Orange
Red
ON Valid Connection to 10/100 Base-T
hub/switch
ON Malfunction
Blinking Transmitting RTP Packets
Blinking Receiving RTP Packets
No traffic
Blinking Activity, when control messages
sent/received in Real Time
ON No registration with Call Agent, no
response from Call Agent/ Gatekeeper
ON No RT messages with Call Agent, but
Call Agent is responding
ON Device Powered, Self test OK
Blinking Software Loading/Initialization
ON Malfunction
Button Restarts MP-1xx
Version 4.0 27 October 2002
Page 28
# 1-8
Channels
# 1-4
Channels
MP-1xx
Functionality of the MP-1xx Front Panel Channel LEDs is described in the
following 3 tables.
Table 2-2: MP-108 Channel LEDs
MP-108 with 1 to 8 Channels
Off-hook for FXO; Ringing or off-hook
for FXS
Off-hook for FXO; Ringing or off-hook
for FXS
Telephone
Interface
Telephone
Interface
Green
Green
Red
Blank
ON
BLINKING Ringing on FXO & FXS
ON Line Malfunction
- Normal Status
Table 2-3: MP-104 Channel LEDs
MP-104 with 1 to 4 Channels
Green
Green
Red
Blank
ON
BLINKING Ringing on FXO & FXS
ON Line Malfunction
- Normal Status
Table 2-4: MP-102 Channel LEDs
MP-102 with 1 to 2 Channels
# 1-2
Channels
Telephone
Interface
Green
Green
Red
Blank
ON Ringing or off-hook for FXS
BLINKING Ringing on FXS
ON Line Malfunction
- Normal Status
MP-1xx User’s Manual 28 Document #: LTRT-00714
Page 29
MP-1xx User’s Manual 3. Software Installation
2.3 Rear Panel LED Indicators and Connectors
Figure 2-5: Rear Panel LED Indicators and Connectors
Power Supply
Chassis
Ground Screw
100-250 V ~1A
Inlet
10/100 Base-T
RJ-45 Port
ETH-1
123456
FXS-FXO
2 to 8 RJ-11
FXS or FXO Ports
9-pin RS-232
Status Port
RS-232
Table 2-5: Meaning of Rear Panel LED Indicators
Label Type Color State Meaning
ETH-1
Ethernet
Status
Yellow
Red
Table 2-6: Explanation of Rear Panel Connectors/Switches
ON Ethernet Port Receiving Data
ON Collision
FXS-FXO
8
7
Label Type Function Comment
100-240V ~ 1A
1 to 8
1 to 4
1 to 2
ETH 1
RS-232
3-pin power inlet AC input Connection to external power supply
RJ-11 8 FXS or FXO Ports
RJ-11 4 FXS or FXO Ports
RJ-11 2 FXS Ports
RJ-45 10/100 Base-T Port Shielded
DB-9, DCE Status Messages DCE connects to PC’s RS-232 port with
Grounding screw Chassis Ground
MP-108 2-wire Loop Start interface
MP-104 2-wire Loop Start interface
MP-102 2-wire Loop Start interface
a straight cable (
MUST be connected and securely
fastened
Figure 9-1 page 132).
Version 4.0 29 October 2002
Page 30
MP-1xx
2.4 Installation of the Life Line on FXS only
Note: The MP-124 and MP-10x/FXO Media Gateways do NOT support the Life
Line.
The MP-108/FXS and MP-104/FXS gateways provide a Life Line connection
ONLY on port #4.
The MP-102/FXS gateway provides a Life Line connection ONLY on port #2.
This feature provides a wired phone connection to any PSTN or PBX FXS port
when power-down conditions exist, or LAN fails.
The phone that is connected to port #4, on pins #2 and #3, is wired to the
PSTN or PBX FXS wires on pins #1 and #4 on the same connector.
Therefore, when the power outage or LAN failure occurs, the User of the MP-
1xx can use the phone even when the MP-1xx is not powered-on. To use this
function, the User must utilize a splitter that connects pins #1 and #4 to
another source of an FXS port, and pins #2 and #3 to the POTS phone.
The pinout of port #4 RJ-11 phone connector is as follows:
1 - Life Line TIP
2 - TIP
3 - RING
4 - Life Line RING
Refer to Figure 2-6 for the RJ-11 connector Life Line pinout.
Figure 2-6: RJ-11 Connector and Life Line Pinout for MP-10x/FXS
RJ-11 Connector and Life Line Pinout
1 2 3 4
Life Line Tip
1 2 -
Tip
3 -
Ring
Life Line Ring
4 -
Note: Life Line applies to only to FXS versions of MP-10x.
MP-1xx User’s Manual 30 Document #: LTRT-00714
Page 31
MP-1xx User’s Manual 3. MP-124 Hardware Installation
3
3
3
M
M
M
P
P
P
-
-
-
1
1
1
2
2
2
4
4
4
H
H
H
I
I
I
a
n
n
n
a
a
s
s
s
r
r
r
t
t
t
d
d
d
a
a
a
w
w
w
l
l
a
l
l
l
l
a
a
a
a
a
r
t
t
t
r
r
i
i
i
e
e
e
o
o
o
n
n
n
Version 4.0 31 October 2002
Page 32
MP-1xx
Note 1: The MP-124 24-port, MP-108 8-port, MP-104 4-port and MP-102 2-port
Media Gateways have similar functionality except for the number of channels
(the MP-124 and MP-102 support only FXS), and all versions are referred to
collectively in these release notes as the MP-1xx.
Note 2: MP-10x refers to MP-108 8-port, MP-104 4-port and MP-102 2-port
gateways.
Note 3: MP-1xx/FXS refers only to the MP-124/FXS, MP-108/FXS, MP-104/FXS and
MP-102/FXS gateways.
Note 4: MP-10x/FXO refers only to MP-108/FXO and MP-104/FXO gateways.
This section explains the installation procedure for the
MP-124 unit and describes the device’s appearance and
functionality, the LEDs and the various connectors.
The section has the following subsections:
Hardware Installation Procedure .................................... 33
MDF Adaptor and Cabling .............................................. 33
How to Install rack-mounts and desktops ...................... 36
Front Panel LED Indicators ............................................ 38
Rear Panel LED Indicators ............................................. 39
MP-1xx User’s Manual 32 Document #: LTRT-00714
Page 33
MP-1xx User’s Manual 3. MP-124 Hardware Installation
3.1 MP-124 Hardware Installation Procedure
3.1.1 Unpacking
To unpack the MP-124:
Open the carton and remove packing materials
Remove the MP-124 from the carton
Check that there is no equipment damage
Check, retain and process any documents
Notify AudioCodes of any damage or discrepancies
Retain any diskettes or CDs
Safety Notice
Installation and service of this device must only be performed by authorized, qualified
service personnel.
3.1.2 MDF Adaptor
To connect 24 2-wire lines into the MP-124, a Main Distribution Frame (MDF)
Adaptor Block should be used as shown in Figure 3-1. This converts the
standard RJ-11 connectorized phone line into a plain pair of wires that are
terminated within a 50-pin Telco connector.
Version 4.0 33 October 2002
Page 34
MP-1xx
Figure 3-1: MP-124 in a 19-inch Rack with MDF Adaptor
FRONT INPUT
24 line cords
2-wire with RJ-11
connectors
AC Power Cord
100 - 250V~
50 - 60Hz 2A
Grounding Strap
19-inch Rack
Rear View
M D F Adaptor Block - rear
REAR OUTPUT
24 wire pairs in
Octopus cable
with 50-pin male
Telco connector
Connect to
here
ANALOG LINES 1-20
Data Cntrl Ready
50-pin female
Telco connector
RS-232
1 2 3 4 5
ON
CONFIG
RS-232 Cable
Eth 1 Eth 2
Primary
LAN Cable
to Eth 1
Back-up
LAN Cable
to Eth 2
MP-124
Rear View
Note: The AudioCodes-supplied equipment shown in Figure 3-1 is
the MP-124 Media Gateway, and the MDF Adaptor Block.
As input (on the front of the 19-inch rack), the Adaptor Block takes in 24 2wire lines with standard RJ-11 connectors.
As output (on the rear of the 19-inch rack), the Adaptor Block provides 24
wire pairs, which need to be terminated into a single 50-pin male Telco
connector.
MP-1xx User’s Manual 34 Document #: LTRT-00714
Page 35
MP-1xx User’s Manual 3. MP-124 Hardware Installation
The 50-pin Telco connectors must be wired according to the pinout in Table
3-1 and Figure 3-2, shown below.
3.1.3 MP-124 Cable Connections
The 50-pin Telco connector mounted on the rear of the MP-124 is wired
according to the pinout in Table 3-1 and Figure 3-2, shown below. The User’s
cable-mounted 50-pin Telco connector, supporting the 24 2-wire phone lines,
must be wired identically.
Table 3-1: Pin Allocation in 50-pin Telco Connector
Phone Channel Connector Pins Phone Channel Connector Pins
1 1/26 13 13/38
2 2/27 14 14/39
3 3/28 15 15/40
4 4/29 16 16/41
5 5/30 17 17/42
6 6/31 18 18/43
7 7/32 19 19/44
8 8/33 20 20/45
9 9/34 21 21/46
10 10/35 22 22/47
11 11/36 23 23/48
12 12/37 24 24/49
Figure 3-2: 50-pin Telco Connector
Pin Numbers
50
Version 4.0 35 October 2002
125
26
Page 36
MP-1xx
The RJ-45 (Ethernet) and RJ-11 (POTS) pinouts and connectors are shown in
Figure 3-3. Pins are numbered from the left with the latching finger position at
the bottom.
Figure 3-3: RJ-45 and RJ-11 Connectors and Pinouts
RJ-45 Connector and Pinout
1 2 3 4 5 6 7 8
1 - Tx+
2 - Tx3 - Rx+
6 - Rx-
4, 5, 7, 8
not
connected
RJ-11 Connector and Pinout
1 2 3 4
3.1.4 MP-124 19-inch Rack Mounting
Figure 3-4: MP-124 with 19-inch Rack Mounting Ears
MP-124 gateway is supplied with brackets (‘ears’) fitted to each side of the
enclosure so that the MP-124 can be immediately installed in the 19-inch rack.
To install the rack mount MP-124, take the next 9 steps:
Not connected
1 2 -
Tip
3 -
Ring
Not connected
4 -
Step 1 Insert the MP-124 into the 19-inch rack, adjust it to the correct
position and use two standard rack-screws (not supplied) to secure
each of the two brackets to the rack frame.
Step 2 Insert each of the RJ-11 connectors on the 2-wire line cords of the
POTS phones into the RJ-11 sockets on the front of the MDF
Adaptor Block
Up to 3,000 m (10,000 feet) of 24 AWG line cord can be used to
MP-1xx User’s Manual 36 Document #: LTRT-00714
Page 37
MP-1xx User’s Manual 3. MP-124 Hardware Installation
connect telephones.
Step 3 Attach to the each of the sockets on the rear of the MDF Adaptor
Block one pair of wires from a 25-pair Octopus cable.
Step 4 Connect the wire-pairs at the other end of the Octopus cable to a
male 50-pin Telco connector. The pinout must be that shown in
Table 3-1 and Figure 3-2 on page 35.
Step 5 Insert and fasten this 50-pin connector into the female 50-pin Telco
connector mounted at the rear of the MP-124 and labeled Analog
Lines 1-24.
Step 6 Insert the RJ-45 connector of the 10/100 Base-T cable into the RJ-
45 connector mounted at the rear of the MP-124 and labeled Eth 1
for connection to your LAN.
Step 7 Connect an electrically grounded strap to the chassis ground screw
on the rear of the MP-124 and fasten it securely according to the
current standards.
Step 8 Connect an electric power cord of the correct rating, from a
grounded supply of the correct voltage, into the power socket
mounted at the rear of the MP-124 and labeled 100 - 250 V ~ 50 –
60 Hz 2A.
Step 9 Observe the front panel LEDs to determine the functioning of the
MP-124.
The Channel LEDs indicate that the telephones connected to the rear 50-pin
connector are each in one of the following states:
ringing or in the Off Hook position Green
normal operation Blank
not functioning Red
The functions of all LEDs of the MP-124 are shown in Table 3-2 on page 38.
Version 4.0 37 October 2002
Page 38
MP-1xx
3.2 MP-124 Front Panel LED Indicators
Figure 3-5: Front Panel LED Indicators
Table 3-2: Function of Front Panel LED Indicators
Label Type Color State Function
Channels
# 1-24
Data
LAN Reset
Ready Control
Data
Control
LAN
Ready
Channels
# 1- 24
Packet
Status
Control Link
Ethernet
Status
Device
Status
Tel Port Green ON Off-Hook/Ringing for FXS Phone Port
Tel Status
Green Blinking Transmitting RTP Packets
Red Blinking Receiving RTP Packets
Blank - No traffic
Green Blinking Currently not implemented
Red ON Currently not implemented
Orange Currently not implemented
Green ON Valid link to 10/100 Base-T hub/switch
Red ON Malfunction
Green ON Device Powered and Self-test OK
Orange Blinking Software Loading/Initialization
Red ON Malfunction
Red ON Malfunction
Blank - Normal
MP-1xx User’s Manual 38 Document #: LTRT-00714
Page 39
MP-1xx User’s Manual 3. MP-124 Hardware Installation
3.3 MP-124 Rear LED Indicators/Connectors
Figure 3-6: MP-124 Rear Panel LED Indicators and Connectors
Grounding
Screw
100 - 250V~
50 - 60Hz 2A
AC Power
Inlet
Data
LED
ANALOG LINES 1-2 0
50-pin Telco
Connector
Ready
LED
Data Cntrl Ready
Cntrl
LED
CONFIG
Table 3-3: Function of Rear Panel LED Indicators
1 2 3 4 5
ON
Monitor
Port
LAN
LEDs
RS-232
Eth 1 Eth 2
Eth 1 &
Eth 2
Label Type Color State Function
Data
Cntrl
Ready
Eth 1
Eth 2
Packet
Status
Control Link
Device
Status
Ethernet
Status
Ethernet
Status
Green ON Transmitting RTP Packets
Red ON Receiving RTP Packets
Blank - No traffic
Green ON Currently not implemented
Red ON Currently not implemented
Orange ON Currently not implemented
Green ON Device Powered and Self-test OK
Orange ON Software Loading/Initialization
Red ON Malfunction
Green ON Valid link to 10/100 Base-T hub/switch
Red ON Malfunction
Green ON Valid link to 10/100 Base-T hub/switch
Red ON Malfunction
Version 4.0 39 October 2002
Page 40
MP-1xx
Table 3-4: Function of Rear Panel Connectors/Switches
Label Type Function Comment
100-250 V~
50 - 60 Hz 1A
Analog Lines 1 to 24
Eth 1
Eth 2
RS-232
3-pin AC AC input Connection to AC power cord
Grounding Screw Chassis ground
50-pin Telco connector FXS Ports 2-wire Loop Start interface
RJ-45 10/100 Base-T Shielded port to Ethernet LAN.
This is the default port.
RJ-45 10/100 Base-T Shielded port to Ethernet LAN.
The port is not in use for
current SW release.
Gateway connects to PC’s
DB-9, DCE Status Messages
RS-232 port with a straight
cable (refer to
page 132)..)
Figure 9-1 on
Note: The DIP switch located on the MP-124 rear panel is not functional and
should not be used.
MP-1xx User’s Manual 40 Document #: LTRT-00714
Page 41
MP-1xx User’s Manual 4. Software Installation
4
4
4
S
S
S
I
I
I
n
o
o
o
n
n
f
s
s
s
f
f
t
t
t
t
w
t
t
a
a
a
w
w
l
l
l
a
a
a
l
l
l
r
a
a
a
r
r
t
t
t
e
e
e
i
o
i
i
o
o
n
n
n
Version 4.0 41 October 2002
Page 42
MP-1xx
Note 1: The MP-124 24-port, MP-108 8-port, MP-104 4-port and MP-102 2-port
Media Gateways have similar functionality except for the number of channels
(the MP-124 and MP-102 support only FXS), and all versions are referred to
collectively in these release notes as the MP-1xx.
Note 2: MP-10x refers to MP-108 8-port, MP-104 4-port and MP-102 2-port
gateways.
Note 3: MP-1xx/FXS refers only to the MP-124/FXS, MP-108/FXS, MP-104/FXS and
MP-102/FXS gateways.
Note 4: MP-10x/FXO refers only to MP-108/FXO and MP-104/FXO gateways.
This section explains how to install the MP-1xx software, as
well as Initialization.
The section has the following subsections:
Software Installation Procedure ................................... 43
The ini File Structure .....................................................48
Call Progress Tones & Distinctive Ringing....................50
The coeff.dat Configuration File ....................................64
MP-1xx User’s Manual 42 Document #: LTRT-00714
Page 43
MP-1xx User’s Manual 4. Software Installation
4.1 Software Installation Procedure
4.1.1 MP-1xx Initialization (BootP, TFTP)
The MP-1xx implements BootP and TFTP protocols for initialization and
software download. Each time the MP-1xx is powered-on, or when the reset
button is pushed, it performs the standard BootP procedure.
Usually, the application software already resides in the MP-1xx flash memory,
so there is no need to use the BootP or TFTP procedure. Their download
need only be used to change the MP-1xx configuration or for new software
upgrades. When working from flash, the programmed IP address, ram.cmp,
and ini files are used.
Note: The file ram.hex is a downloadable software image file. The file ram.cmp is
a compressed version of the ram.hex, enabling faster download and
reduced file size. The ram.cmp is the only version that can be burned to the
flash memory.
Bootstrap Protocol enables network administrators to manage the
configuration of the MP-1xx Media Gateway from a central configuration
server - BootP/DHCP server.
The following RFCs (IETF Requests for Comment) describe BootP in detail:
RFC 951, RFC 1542, and RFC 2132.
Downloading of the image file by the MP-1xx is performed using Trivial File
Transfer Protocol (TFTP). TFTP protocol is described in RFC 906 and RFC
1350.
Although DHCP and BootP servers are similar in operation, the DHCP server
includes some differences that prevent its operation with BootP clients.
However, many DHCP servers, such as Windows
backward compatible with BootP protocol and can be used for MP-1xx
configuration.
™
NT DHCP server, are
Note: The BootP server is normally used to configure the MP-1xx initial
parameters. Once this information has been provided, the BootP server is
no longer needed. All parameters are stored in non-volatile memory and
used when the BootP server is not accessible. The BootP server will be
required again if, for example, the MP-1xx IP address is to be changed.
Figure 4-1 illustrates the MP-1xx Initialization Procedure:
Version 4.0 43 October 2002
Page 44
MP-1xx
Figure 4-1: MP-1xx Initialization Procedure
RESET
BootP
NO YES
Server
?
Use Default
Network
Parameters
Run Software
from FLASH
Use previously stored
INI file/default
parameters and
configuration files
Run Software
from FLASH
NO
File Name
in BootP
Update Network
NO
INI
?
Parameters
Boot
File Name
?
YES
YES
TFTP Download of
Software Image File
Store file in FLASH
TFTP Download
of INI File
TFTP Download
Configuration files if
required in INI file
Update & Store INI
file parameters &
configuration files
RUN APPLICATION
MP-1xx User’s Manual 44 Document #: LTRT-00714
Page 45
MP-1xx User’s Manual 4. Software Installation
4.1.2 MP-1xx Initialization
The MP-1xx includes integral flash memory already programmed with
application software. Normally during the power-up procedure, MP-1xx only
performs BootP procedure to initialize its parameters such as IP address and
subnet mask.
During start-up procedure, the MP-1xx attempts to communicate with the
BootP server. If the BootP server is not found, the MP-1xx starts working from
its internal flash memory. The start-up procedure takes about 10 seconds.
After self-testing, the Ready LED turns to Green. Any malfunction causes the
Ready LED to change to Red.
Usually, BootP procedure is required only once to set up the MP-1xx
initialization parameters (such as IP address and subnet mask) and
configuration parameters (contained in the ini file). In subsequent operations,
the BootP procedure is no longer required, and all initial parameters are
retrieved from the MP-1xx non-volatile memory.
Refer to Figure 4-1 on page 44, for the flow chart illustrating MP-1xx
Initialization Procedure.
4.1.2.1 Command Line Switches
The following Command Line Switches are available:
-fb Burn ram.cmp in flash
-em Ethernet mode
-br BootP retries
-bd BootP delays
Example of use:
As shown in Section 4.1.3, Step 4:
“ramxxx.cmp -fb” to burn flash memory.
Example of use:
“ramxxx.cmp -fb -em 4” for Ethernet Mode 4 (auto-negotiate).
Note that such Command Line Switches can only be added in the BootP file
name location. The actual file name remains (e.g., ramxxx.cmp) and does not
change.
Version 4.0 45 October 2002
Page 46
MP-1xx
4.1.3 MP-1xx Software Upgrade Procedure
MP-1xx includes integral flash memory already programmed with application
software. The following procedure replaces the old stored software with the
new version. To run this procedure, BootP and TFTP servers are required.
Note 1: The file extensions cmp and ini should be written in lower case letters.
Note 2: The file name mp108.ini is used for the MP-108, MP-104 and MP-102.
To run the Software Upgrade take the following 3 steps:
1. Start the TFTP and BootP servers.
2. Copy the new ramxxx.cmp file, mp108.ini file and optional configuration
files (see Section 7.5) to the default TFTP server directory.
3. Set the Boot file name in the BootP server: ramxxx.cmp -fb;mp108.ini.
Other BootP parameters will stay unchanged (IP address, subnet
mask…). If required, it is possible to update only the mp108.ini
parameters. For this option, set the Boot file name to: mp108.ini (without
preceding ramxxx.cmp). After an MP-1xx power reset, the ini parameters
are downloaded using TFTP procedure and stored in non-volatile
memory.
The MP-1xx is supplied with an internal switch set so that every BootP or
TFTP loaded is automatically burned into the flash memory without User
intervention.
Note: The new software version can be downloaded and tested without being
saved to flash and without replacing the old version, by using the original
command line ramxxx.cmp.
4.1.4 AudioCodes’ BootP/TFTP Server Configuration Tool
AudioCodes’ BootP/TFTP Server Configuration Tool provides an easy way to
configure the MP-1xx. Similar to third party BootP/TFTP servers but with
added functionality, AudioCodes’ BootP/TFTP Server Configuration Tool can
be installed on Windows
BootP/TFTP Server Configuration Tool, it is possible to install a TFTP server
on a different host. Starting from software version 3.5, the server enables
remote reset of the MP-1xx to trigger the initialization procedure (BootP &
MP-1xx User’s Manual 46 Document #: LTRT-00714
™
98 or Windows™ NT/2000/XP. With AudioCodes’
Page 47
MP-1xx User’s Manual 4. Software Installation
TFTP). Refer to Appendix A in the AudioCodes "Software Utilities Manual",
Document #: LTRT-00702.
4.1.5 Microsoft™ DHCP/BootP Server
If you’re using the Microsoft™ DHCP server in your organization, it can be
used to provide an IP address and other necessary information to the MP-1xx
Media Gateway. If you’re not using it, any other third party BootP server can
be used.
To configure your Microsoft
address information 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 DHCP Manager.
The reservation builds an association between the Media Access Control
(MAC) address (12 digits, provided in MP-1xx documentation) and the IP
address. Windows
MAC address in the BootP request frame.
To configure your Microsoft
information to BootP clients, edit the BootP Table in DHCP Manager. The
BootP Table is located in the Server Properties dialog box that can be
accessed from the Server menu. For information on editing the BootP Table,
view the "BootP Table" Help topic in DHCP Manager.
™
NT Server provides the IP address based on the MP-1xx
™
Windows™ NT DHCP Server to assign IP
™
Windows™ NT DHCP server to provide boot file
4.1.6 Third Party TFTP & BootP Servers
Third party TFTP and BootP servers are commercially available. For details,
refer to Appendix C (BootP Server Installation and Configuration), and
Appendix D (TFTP Server Installation and Configuration) in the AudioCodes
"Software Utilities Manual", Document # LTRT-00702.
Note: The instructions for AudioCodes’ and 3rd party BootP and TFTP Server
Installation & Configuration are detailed, with examples of the individual
screens, in the AudioCodes "Software Utilities Manual", Document #: LTRT-
00702.
Version 4.0 47 October 2002
Page 48
MP-1xx
4.2 The ini File Structure
The ini file can contain any number of parameters. The parameters are
divided into groups by their functionality. The general form of the ini file is
shown below.
Figure 4-2: ini File Structure
[Sub Section Name]
Parameter_Name = Parameter_Value
Parameter_Name = Parameter_Value
.
..
; REMARK
[Sub Section Name]
.
4.2.1 The ini File Structure Rules
• Lines beginning with a semi-colon ‘;’ (as the first character) are ignored.
• Carriage Return must be the final character of each line.
• 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 wrong values).
• Sub-section names are optional.
• The values of String parameters, for example VoicePromptsFileName,
should be placed between two inverted commas (‘…’).
• The parameter field is NOT case sensitive.
• Parameter values should be entered only in decimal format, except for
the Call Agent IP address.
• The ini file should be ended with one or more carriage returns.
MP-1xx User’s Manual 48 Document #: LTRT-00714
Page 49
MP-1xx User’s Manual 4. Software Installation
4.2.2 The ini File Example
An example of an ini file is shown in the figure below:
Figure 4-3: ini File Example
[MGCP]
EndpointName = 'ACgw'
CallAgentIP = 192.1.10.3
CallAgentPort = 2427
BaseUDPPort = 4000
RingOnPeriod = 1000
RingOffPeriod = 3000
FlashHookPeriod = 700
[Channel Params]
DJBufferMinDelay = 75
RTPRedundancyDepth = 1
[Files]
CallProgressTonesFilename = 'CPUSA.dat'
BurnCallProgressTonesFile = 1
VoicePromptsFilename = 'tpdemo_723.dat'
BurnVoicePromptsFile = 0
FXSLOOPCHARACTERISTICSFILENAME = 'coeff.dat'
BurnCoefFile
Note 1: Using Windows Properties Display, verify that the MS-DOS name of the ini
file is in fact mp108.ini, and NOT by mistake mp.108.ini.ini, or mp108~.ini.
Note 2: To restore the MP-1xx default configuration parameters, mp108.ini file
should be used without any valid parameters or with a semicolon (;)
character preceding all lines in the file.
Version 4.0 49 October 2002
Page 50
MP-1xx
4.3 Call Progress Tones & Distinctive Ringing
The Call Progress Tones Configuration and Distinctive Ringing file consists of
2 parts. The first part contains the definitions of the Call Progress Tones to be
detected/generated by the MP-1xx. The second part contains the
configuration of the Distinctive Ringing patterns to be generated by the MP-
1xx. Users can use either one of the MP-1xx configuration files supplied by
AudioCodes, or construct their own file.
The Call Progress Tones and Distinctive Ringing Configuration file used by
the MP-1xx is a binary file (with the extension .dat). Users can construct their
own configuration file by starting from tone.ini file format, then modifying the
file, and finally, converting it into binary format using the “TrunkPack
Downloadable Conversion Utility” supplied with the MP-1xx package. Refer to
Section 4.3.5 for a description of the procedure of how to generate and
download the Call Progress Tone file using this utility.
To download the Call Progress Tones and Distinctive Ringing Configuration
file to the MP-1xx, a correct definition should be used in the mp108.ini file.
Refer to Sections 4.2.1 and 4.2.2 for the ini file structure rules and ini file
example.
4.3.1 Format of the Call Progress Tones Section
The Call Progress Tones section of the ini file format starts from the following
string:
• [NUMBER OF CALL PROGRESS TONES] – containing only the
following key:
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 1 and not exceeding the number of Call Progress Tones
defined in the first section) using the following keys:
Tone Type – Call Progress Tone type
1. Dial Tone
2. Ringback Tone
3. Busy Tone
MP-1xx User’s Manual 50 Document #: LTRT-00714
Page 51
MP-1xx User’s Manual 4. Software Installation
4. Congestion Tone
5. Special Information Tone
6. Warning Tone
7. Reorder Tone
8. Confirmation Tone
9. Call Waiting Tone
Low Freq [Hz] – Frequency in hertz of the lower tone component in
the case of a dual frequency tone, or the frequency of the tone in the
case of a single tone.
High Freq [Hz] – Frequency in hertz of the higher tone component
in the case of a dual frequency tone, or zero (0) in the case of a
single tone.
Low Freq Level [-dBm] – Generation level 0 dBm to -31 dBm. The
value should be zero (0) in the case of a single tone.
High Freq Level – Generation level. 0 to -31 dBm as shown in
Table 4-1 on page 52.
First Signal On Time [10 msec] – “Signal On” period (in 10 msec
units) for the first cadence on-off cycle.
First Signal Off Time [10 msec] – “Signal Off” period (in 10 msec
units) for the first cadence on-off cycle.
Second Signal On Time [10 msec] – “Signal On” period (in 10
msec units) for the second cadence on-off cycle.
Second Signal Off Time [10 msec] – “Signal Off” period (in 10
msec units) for the second cadence on-off cycle.
The tone level can be specified in one of two ways: in dBm units or using DSP
codes. To use dBm units, set “Use dBm units for Tone levels”, or else use the
code shown in Table 4-1 on page 52 to achieve the required dBm.
Using this configuration file, the User can create up to 16 different Call
Progress Tones using up to 15 different frequencies (in the range of 300 Hz to
2000 Hz). Each of the Call Progress Tones is specified by the following two
parameters: the tone frequency (either single or dual frequencies are
supported) and the tone cadence. This is specified by 2 sets of ON/OFF
periods, but Users can discard the use of the first On/Off cycle by setting the
relevant parameters to zero. When the tone is made up of a single frequency,
the second frequency field should be set to zero.
For a continuous tone (such as dial tone), only the “First Signal On time”
should be specified. In this case, the parameter specifies the detection period.
For example, if it equals 300, then the tone is detected after 3 seconds (300 x
10 msec).
Version 4.0 51 October 2002
Page 52
MP-1xx
Table 4-1 on page 52 shows the Output Tone Levels for each DSP code.
Note 1: When defining several continuous tones, the “First Signal On Time”
parameter should have the same value for all tones.
Note 2: The tones frequency should differ by at least 40 Hz from one tone to other
defined tones.
Table 4-1: Output Tone Levels
Code Output
Level
0 Mute 11 -21 dBm 22 -10 dBm
1 -31 dBm 12 -20 dBm 23 -9 dBm
2 -30 dBm 13 -19 dBm 24 -8 dBm
3 -29 dBm 14 -18 dBm 25 -7 dBm
4 -28 dBm 15 -17 dBm 26 -6 dBm
5 -27 dBm 16 -16 dBm 27 -5 dBm
6 -26 dBm 17 -15 dBm 28 -4 dBm
7 -25 dBm 18 -14 dBm 29 -3 dBm
8 -24 dBm 19 -13 dBm 30 -2 dBm
9 -23 dBm 20 -12 dBm 31 -1 dBm
10 -22 dBm 21 -11 dBm 32 0 dBm
Code Output
Level
Code Output
4.3.2 Format of the Distinctive Ringing Section
The distinctive ringing section of the ini file format starts from string:
• [NUMBER OF DISTINCTIVE RINGING PATTERNS] – containing only
the following key:
Number of Distinctive Ringing patterns – defines the number of
Call Progress Tones to be defined in the file.
Level
• [Ringing Pattern #X] – containing the Xth ringing pattern definition
(starting from 1 and not exceeding 16 using the following keys:
MP-1xx User’s Manual 52 Document #: LTRT-00714
Page 53
MP-1xx User’s Manual 4. Software Installation
Ring Type – ring type is equal to Ringing Pattern number.
Freq [Hz] – Frequency in hertz of the ringing tone.
First Ring On Time [10 msec] – “Ring On” period (in 10 msec
units) for the first cadence on-off cycle.
First Ring Off Time [10 msec] – “Ring Off” period (in 10 msec
units) for the first cadence on-off cycle.
Second Ring On Time [10 msec] – “Ring On” period (in 10 msec
units) for the second cadence on-off cycle.
Second Ring Off Time [10 msec] – “Ring Off” period (in 10 msec
units) for the second cadence on-off cycle.
Third Ring On Time [10 msec] – “Ring On” period (in 10 msec
units) for the third cadence on-off cycle.
Third Ring Off Time [10 msec] – “Ring Off” period (in 10 msec
units) for the third cadence on-off cycle.
Fourth Ring Off Time [10 msec] – “Ring Off” period (in 10 msec
units) for the forth cadence on-off cycle.
Fourth Ring Off Time [10 msec] – “Ring Off” period (in 10 msec
units) for the forth cadence on-off cycle.
Burst – configures the cadence to be a burst cadence in the whole
ringing pattern. The burst relates to On time and the Off time of the
same cadence. It must appear between “First/Second/Third/Forth”
string and the “Ring On/Off Time”
Using this configuration file, the User can create up to 16 different distinctive
ringing patterns. Every ringing pattern configures the ringing tone frequency
and up to 4 ringing cadences. The same ringing frequency is used for all the
ringing pattern cadences. The ringing frequency can be configured in the
range from 10 Hz up to 200 Hz with a 5 Hz resolution. Each of the ringing
pattern cadences is specified by the following parameters:
Burst cadence is specified by the “Burst” string. This cadence rings
once during the ringing pattern. Otherwise, the cadence is
interpreted as cyclic: it repeats for every ringing cycle.
Ring On Time – specifies the duration of the ringing signal.
Ring Off Time – specifies the silence period of the cadence.
Version 4.0 53 October 2002
Page 54
MP-1xx
Note: In the current software release, the distinctive ringing, as described, is not
implemented in the MGCP/MEGACO packages. Use RingOnPeriodN and
RingOffPeriodN configurations instead, where N specifies the number of
distinctive ringing 0...7.
4.3.3 Default Template for Call Progress Tones
The MP-1xx is initialized with default Call Progress Tones configuration (refer
to Table 4-2). 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 Table 4-2 with the following text:
#Dial tone
[CALL PROGRESS TONE #1]
Tone Type=1
Low Freq [Hz]=440
High Freq [Hz]=0
Low Freq Level [-dBm]=22 (-10dBm)
High Freq Level [-dBm]=0
First Signal On Time [10msec]=300; the dial tone will be detected after 3 sec
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=0
Second Signal Off Time [10msec]=0
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 ini file. The MP-1xx reports dial tone detection if
either one of the two tones has been detected.
Table 4-2: Call Progress Tones (continues on pages 54 to 57)
[NUMBER OF CALL PROGRESS TONES]
Number of Call Progress Tones=9
#Dial tone
[CALL PROGRESS TONE #0]
MP-1xx User’s Manual 54 Document #: LTRT-00714
Page 55
MP-1xx User’s Manual 4. Software Installation
Table 4-2: Call Progress Tones (continues on pages 54 to 57)
Tone Type=1
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
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=0
Second Signal Off Time [10msec]=0
#Dial tone
[CALL PROGRESS TONE #1]
Tone Type=1
Low Freq [Hz]=440
High Freq [Hz]=0
Low Freq Level [-dBm]=10 (-10dBm)
High Freq Level [-dBm]=0
First Signal On Time [10msec]=300
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=0
Second Signal Off Time [10msec]=0
#Ringback
[CALL PROGRESS TONE #2]
Tone Type=2
Low Freq [Hz]=440
High Freq [Hz]=480
Low Freq Level [-dBm]=19 (-19dBm)
High Freq Level [-dBm]=19
First Signal On Time [10msec]=0
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=200
Second Signal Off Time [10msec]=400
#Ringback
[CALL PROGRESS TONE #3]
Version 4.0 55 October 2002
Page 56
MP-1xx
Table 4-2: Call Progress Tones (continues on pages 54 to 57)
Tone Type=2
Low Freq [Hz]=440
High Freq [Hz]=0
Low Freq Level [-dBm]=16 (-16dBm)
High Freq Level [-dBm]=0
First Signal On Time [10msec]=0
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=100
Second Signal Off Time [10msec]=300
#Busy
[CALL PROGRESS TONE #4]
Tone Type=3
Low Freq [Hz]=480
High Freq [Hz]=620
Low Freq Level [-dBm]=24 (-24dBm)
High Freq Level [-dBm]=24
First Signal On Time [10msec]=0
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=50
Second Signal Off Time [10msec]=50
#Busy
[CALL PROGRESS TONE #5]
Tone Type=3
Low Freq [Hz]=440
High Freq [Hz]=0
Low Freq Level [-dBm]=20 (-20dBm)
High Freq Level [-dBm]=0
First Signal On Time [10msec]=0
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=50
Second Signal Off Time [10msec]=50
#Reorder tone
[CALL PROGRESS TONE #6]
Tone Type=7
MP-1xx User’s Manual 56 Document #: LTRT-00714
Page 57
MP-1xx User’s Manual 4. Software Installation
Table 4-2: Call Progress Tones (continues on pages 54 to 57)
Low Freq [Hz]=480
High Freq [Hz]=620
Low Freq Level [-dBm]=24 (-24dBm)
High Freq Level [-dBm]=24
First Signal On Time [10msec]=0
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=25
Second Signal Off Time [10msec]=25
#Confirmation tone
[CALL PROGRESS TONE #7]
Tone Type=8
Low Freq [Hz]=350
High Freq [Hz]=440
Low Freq Level [-dBm]=20 (-20dBm)
High Freq Level [-dBm]=20
First Signal On Time [10msec]=0
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=10
Second Signal Off Time [10msec]=10
#Call Waiting Tone
[CALL PROGRESS TONE #8]
Tone Type=9
Low Freq [Hz]=440
High Freq [Hz]=0
Low Freq Level [-dBm]=20 (-20dBm)
High Freq Level [-dBm]=0
First Signal On Time [10msec]=0
First Signal Off Time [10msec]=0
Second Signal On Time [10msec]=30
Second Signal Off Time [10msec]=900
Version 4.0 57 October 2002
Page 58
MP-1xx
4.3.4 Default Template for Distinctive Ringing Patterns
The MP-1xx is initialized with default Distinctive Ringing Patterns
configuration (refer to Table 4-3). To change one of the tones, copy the call
progress.txt file and edit the default distinctive ringing section.
For example: to change the Ringing Pattern 2 to frequency of 35 Hz with a
burst initial ringing of 300 ms on and 300 ms off
- replace the ring Freq = 35
- add 2 new lines with First Burst Ring On/Off Time = 30
- Replace the previous “First Ring On/Off Time” to “Second Ring On/Off Time”
Table 4-3: Number Of Distinctive Ringing Patterns (continues on pages 58 to 61)
[NUMBER OF DISTINCTIVE RINGING PATTERNS]
Number of Ringing Patterns=14
#Regular North American Ringing Pattern
[Ringing Pattern #0]
Ring Type=0
Freq [Hz]=20
First Ring On Time [10msec]=200
First Ring Off Time [10msec]=400
#GR-506-CORE Ringing Pattern 1
[Ringing Pattern #1]
Ring Type=1
Freq [Hz]=20
First Ring On Time [10msec]=200
First Ring Off Time [10msec]=400
#GR-506-CORE Ringing Pattern 2
[Ringing Pattern #2]
Ring Type=2
Freq [Hz]=20
First Ring On Time [10msec]=80
First Ring Off Time [10msec]=40
Second Ring On Time [10msec]=80
MP-1xx User’s Manual 58 Document #: LTRT-00714
Page 59
MP-1xx User’s Manual 4. Software Installation
Table 4-3: Number Of Distinctive Ringing Patterns (continues on pages 58 to 61)
Second Ring Off Time [10msec]=400
#GR-506-CORE Ringing Pattern 3
[Ringing Pattern #3]
Ring Type=3
Freq [Hz]=20
First Ring On Time [10msec]=40
First Ring Off Time [10msec]=20
Second Ring On Time [10msec]=40
Second Ring Off Time [10msec]=20
Third Ring On Time [10msec]=80
Third Ring Off Time [10msec]=400
#GR-506-CORE Ringing Pattern 4
[Ringing Pattern #4]
Ring Type=4
Freq [Hz]=20
First Ring On Time [10msec]=30
First Ring Off Time [10msec]=20
Second Ring On Time [10msec]=100
Second Ring Off Time [10msec]=20
Third Ring On Time [10msec]=30
Third Ring Off Time [10msec]=400
#GR-506-CORE Ringing Pattern 5 - One single Burst of 500 ms
[Ringing Pattern #5]
Ring Type=5
Freq [Hz]=20
First Burst Ring On Time [10msec]=50
First Burst Ring Off Time [10msec]=50
#EN 300 001 Ring - Belgium
[Ringing Pattern #6]
Ring Type=6
Version 4.0 59 October 2002
Page 60
MP-1xx
Table 4-3: Number Of Distinctive Ringing Patterns (continues on pages 58 to 61)
Freq [Hz]=25
First Ring On Time [10msec]=100
First Ring Off Time [10msec]=300
#EN 300 001 Ring - Finland
[Ringing Pattern #7]
Ring Type=7
Freq [Hz]=25
First Ring On Time [10msec]=50
First Ring Off Time [10msec]=550
#EN 300 001 Ring - Germany
[Ringing Pattern #8]
Ring Type=8
Freq [Hz]=25
First Ring On Time [10msec]=95
First Ring Off Time [10msec]=450
#EN 300 001 Ring - Italy
[Ringing Pattern #9]
Ring Type=9
Freq [Hz]=35
First Ring On Time [10msec]=100
First Ring Off Time [10msec]=400
#EN 300 001 Ring - Netherlands & Norway
[Ringing Pattern #10]
Ring Type=10
Freq [Hz]=25
First Ring On Time [10msec]=100
First Ring Off Time [10msec]=400
#EN 300 001 Ring - Sweden
[Ringing Pattern #11]
Ring Type=11
MP-1xx User’s Manual 60 Document #: LTRT-00714
Page 61
MP-1xx User’s Manual 4. Software Installation
Table 4-3: Number Of Distinctive Ringing Patterns (continues on pages 58 to 61)
Freq [Hz]=35
First Ring On Time [10msec]= 100
First Ring Off Time [10msec]=500
#EN 300 001 Ring - UK
[Ringing Pattern #12]
Ring Type=12
Freq [Hz]=20
First Ring On Time [10msec]= 40
First Ring Off Time [10msec]= 20
Second Ring On Time [10msec]=40
Second Ring Off Time [10msec]=200
#EN 300 001 Ring - Finland
(informative ringing nr. 3: three ringing bursts preceding cyclic ringing)
[Ringing Pattern #13]
Ring Type=13
Freq [Hz]=25
First Burst Ring On Time [10msec]=30
First Burst Ring Off Time [10msec]=30
Second Burst Ring On Time [10msec]=30
Second Burst Ring Off Time [10msec]=30
Third Burst Ring On Time [10msec]=30
Third Burst Ring Off Time [10msec]=30
Fourth Ring On Time [10msec]=100
Fourth Ring Off Time [10msec]=400
Version 4.0 61 October 2002
Page 62
MP-1xx
4.3.5 Call Progress Tone Generation and Download Procedure
Follow the directions below for generation and download of the Call Progress
Tone file.
To run the procedure, take the following 10 steps:
1. Prepare the tone.ini file.
2. Use the “TrunkPack Downloadable Conversion Utility” to generate a
binary tone.dat file.
Figure 4-4: Download Selection Screen
3. Click “Process a new file…”
4. Select the input file such as usa_tone.ini and fill the Vendor and Version
fields.
MP-1xx User’s Manual 62 Document #: LTRT-00714
Page 63
MP-1xx User’s Manual 4. Software Installation
Figure 4-5: File Selection Screen
5. Check the checkbox “Use dBm units for Tone Levels”.
Note: dBm units should be used for Tone Levels.
6. Click the “Make File” button and then close the application.
7. Edit the mp108.ini file and add the following two lines:
CallProgressTonesFilename = 'usa_tone.dat'
BurnCallProgressTonesFile = 1
8. Save the “usa_tone.dat” and “mp108.ini” files in TFTP folder
9. Set the Boot file name in the BootP server: mp108.ini.
10. Activate the BootP and TFTP servers and reset the MP-1xx (see Section
7 describing MP-1xx provisioning).
Version 4.0 63 October 2002
Page 64
MP-1xx
4.4 The coeff.dat Configuration File
The purpose of the coeff.dat configuration file is to provide best termination
and transmission quality adaptation for different line types. The file consists of
a set of parameters for the signal processor of the loop interface devices. This
parameter set provides control of the following AC and DC interface
parameters:
DC characteristics (V / I curve and max current)
AC impedance matching
Transmit gain
Receive gain
Hybrid balance
Frequency response in transmit and receive direction
Hook Thresholds (FXS only)
Ringing detection parameters
Metering parameters
This means, for example, that changing impedance matching or hybrid
balance requires no hardware modifications, so that a single device is able to
meet requirements for different markets. The digital nature of the filters and
gain stages also ensures high reliability, no drifts (over temperature or time),
and simple variations between different line types.
The MP1xx.dat configuration file is produced by AudioCodes for each market
after comprehensive performance analysis and testing, and can be modified
on request. The current file supports US line type of 600 ohm AC impedance
(and for FXS, 40 V RMS ringing voltage for REN = 2).
The following list describes which coeff.dat file is to be used with which MP
device. The files are located under “Analog_Coefficients_Files” folder:
MP-102, MP-104/FXS, MP-108/FXS and MP-124 revC should use:
MP1xx10-1-fxs.dat.
MP-104/FXO and MP-108/FXO should use: MP1xx10-1-fxo.dat.
MP-124 revB should use: MP124B10-1-fxs.dat.
MP-1xx User’s Manual 64 Document #: LTRT-00714
Page 65
MP-1xx User’s Manual 5. Operation & Configuration
5
5
5
O
O
O
p
p
p
e
e
e
r
r
r
a
a
a
t
t
t
i
i
i
o
o
o
n
n
n
&
&
&
C
C
C
Version 4.0 65 October 2002
o
o
o
n
n
n
f
f
f
i
i
i
g
g
g
u
u
u
r
r
r
a
a
a
t
t
t
i
i
i
o
o
o
n
n
n
Page 66
MP-1xx
Note 1: The MP-124 24-port, MP-108 8-port, MP-104 4-port and MP-102 2-port
Media Gateways have similar functionality except for the number of channels
(the MP-124 and MP-102 support only FXS), and all versions are referred to
collectively in these release notes as the MP-1xx.
Note 2: MP-10x refers to MP-108 8-port, MP-104 4-port and MP-102 2-port
gateways.
Note 3: MP-1xx/FXS refers only to the MP-124/FXS, MP-108/FXS, MP-104/FXS and
MP-102/FXS gateways.
Note 4: MP-10x/FXO refers only to MP-108/FXO and MP-104/FXO gateways.
This section describes the MP-1xx MGCP and its various
supported packages.
This section has the following subsections:
MGCP Control Protocol .............................................. 68
MEGACO Protocol...................................................... 74
TPNCP Profile ............................................................ 91
MP-1xx User’s Manual 66 Document #: LTRT-00714
Page 67
MP-1xx User’s Manual 5. Operation & Configuration
5.1 General
The MP-1xx can be controlled from the Gateway Controller/Call Agent using
standard MGCP (Media Gateway Control Protocol), MEGACO (Media
Gateway Control Protocol), and AudioCodes proprietary TPNCP (TrunkPack
Network Control Protocol).
MGCP (Media Gateway Control Protocol) is a standards-based (IETF RFC
2705), network-based control protocol. MGCP assumes a call control
architecture where the call control intelligence is outside the Media Gateway
and handled by an external Gateway Controller (Call Agent). MGCP is a
master/slave protocol, where the Gateway is expected to execute commands
sent by the Gateway Controller. As this is a standard control protocol,
AudioCodes does not provide any special software library to enable Users to
construct their own Call Agent (many such stacks are available in the market
and Users can choose any one of them).
MEGACO (Media Gateway Control) Protocol is a standard network-based
control protocol (based on ITU-T recommendation H.248). MEGACO assumes
a call control architecture where the call control intelligence is outside the
Media Gateway (the TrunkPack board, in this case) and handled by an
external Call Agent. MEGACO is a master/slave protocol, where the gateway
is expected to execute commands sent by the Call Agent.
TPNCP (TrunkPack Network Control Protocol) is AudioCodes’ proprietary
network-based protocol, enabling the MP-1xx Media Gateway to be controlled
over the network using the same API as that used in the AudioCodes VoIPLib
or PSTNLib over PCI. In other words, this is effectively VoIPLib or PSTNLib
over the Network. All commands and statuses are sent/received through the
IP network using a proprietary protocol. TPNCP protocol is described in the
AudioCodes “VoPLib Reference Library User's Manual”, Document #: LTRT-
00744.
Contact AudioCodes Customer Support (support@audiocodes.com
details.
MGCP, MEGACO and TPNCP protocols can coexist (controlling different
channels). For example, an MGCP Gateway Controller can control one of the
MP-1xx channels, while a control application using TPNCP can control
another channel.
) for
Version 4.0 67 October 2002
Page 68
MP-1xx
5.2 MGCP Control Protocol
5.2.1 MGCP Overview
MGCP assumes a call control architecture where the call control intelligence is
outside the Media Gateway and handled by an external Call Agent. MGCP is
a master/slave protocol, where the Gateway is expected to execute
commands sent by the Call Agent.
The MP-1xx currently supports MGCP described in the IETF RFC 2705,
located in the IETF web site: http://www.ietf.org/rfc/
For more details on MGCP commands and parameters, refer to the
AudioCodes “VoPLib Reference Library User's Manual”, Document #: LTRT-
00744.
5.2.2 Operation
MGCP commands, received from an external Call Agent through the IP
network, are decoded and executed in the MP-1xx Media Gateway.
Commands can create new connections, delete connections, or modify the
connection parameters.
There are several commands that support the basic operations required to
control a Media Gateway:
Connection commands: Allow the creation and deletion of call connection
inside the Media Gateway. These commands allow the application to create
new connections, delete existing connections, and modify the connection
parameters.
Notify commands: Using notifications, the Gateway can inform the Call
Agent of events occurring on one of the Endpoints. Notify commands can also
generate signals on the Endpoints.
Audit commands: These commands are used to query the Gateway about
the Endpoints' configuration and state. This information helps managing and
controlling the Gateway.
Events and signals are grouped in packages. Each package supports several
events and signals.
The MP-1xx MGCP supports LINE, DTMF, Generic and handset emulation
packages.
5.2.3 MGCP Call Agent IP Address
The User can set the IP address of the MGCP Call Agent by using the BootP
extension # 200 (IP Address Array) or MGCPCallAgentIPAddr parameter in
the ini file. This setting is used only until the first command is received from an
actual Call Agent (that is, only for the RSIP message). If the RSIP message is
MP-1xx User’s Manual 68 Document #: LTRT-00714
Page 69
MP-1xx User’s Manual 5. Operation & Configuration
not in use, set this parameter to 0. From then on, the MP-1xx uses the
address of the “real” Call Agent.
If a Call Agent fails, a redundant Call Agent can immediately take control of
the MP-1xx by stating to send commands to the MP-1xx gateway. For correct
operation, only a single Call Agent should control the MP-1xx gateway at the
same instant.
5.2.4 MP-1xx Compression Codecs
MGCP supports the compression Codecs listed below. The selected coders(s)
should be used in Local Connection Option line, "a=" parameter.
For example: Create connection command with G.711 coders will look like:
CRCX 10060 Acgw0@[10.1.37.5]
C: 35
L: a:G.711
Table 5-1: MP-1xx Compression Codecs
Codec Name Description
PCMU
PCMA G.711 A-law, 64 kbps
G.711
G726_16 G.726 16 kbps ADPCM
G726_24 G.726 24 kbps ADPCM
G726_32 G.726 32 kbps ADPCM
G726_40 G.726 40 kbps ADPCM
G727_16 G.727 16 kbps E-ADPCM
G727_24 G.727 24 kbps E-ADPCM
G727_32 G.727 32 kbps E-ADPCM
G727_40_32 G.727 40 kbps E-ADPCM
G.723 MP-MLQ at 6.3 kbps
G729 G.729A, 8 kbps
NetCoder_6_4 NetCoder at 6.4 kbps
NetCoder_7_2 NetCoder at 7.2 kbps
NetCoder_8 NetCoder at 8 kbps
NetCoder_8_8 NetCoder at 8.8 kbps
G.711 µ-law, 64 kbps
G.711 µ -law, 64 kbps
Version 4.0 69 October 2002
Page 70
MP-1xx
5.2.5 Supported MGCP Packages
Notes for Tables on supported MGCP Packages (Table 5-2 to Table 5-6):
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:
OO signal: On/Off signal is turned ON until commanded by the Call Agent
to turn it OFF, and vice versa.
TO signal: Timeout signal lasts for a given duration unless it is superseded
by a new signal.
BR signal: Brief signal event has a short, known duration.
Duration: Specifies the duration of TO signals.
5.2.5.1 DTMF Package - D
Table 5-2: DTMF Package - D
Symbol Definition R S Duration
0 DTMF 0 x BR
1 DTMF 1 x BR
2 DTMF 2 x BR
3 DTMF 3 x BR
4 DTMF 4 x BR
5 DTMF 5 x BR
6 DTMF 6 x BR
7 DTMF 7 x BR
8 DTMF 8 x BR
9 DTMF 9 x BR
# DTMF # x BR
* DTMF * x BR
A DTMF A x BR
B DTMF B x BR
C DTMF C x BR
D DTMF D x BR
T Inter-digit Timer x 4 sec
X Wildcard, match any digit 0 to 9 x
of Report Failure x
MP-1xx User’s Manual 70 Document #: LTRT-00714
Page 71
MP-1xx User’s Manual 5. Operation & Configuration
When using a digit map, the following notations can be used:
R: D/X(D) D: 2xxx|88#|7xx|3xxT|5x.T|93x.#
up to 12 digits map can be specified per each Endpoint.
5.2.5.2 Generic Media Package - G
Table 5-3: Generic Media Package - G
Symbol Definition R S Duration
mt Modem detected x
ft Fax tone detected x
rt Ringback tone TO
rbk Ring back on connection TO 180 sec
5.2.5.3 Line Package - L
Table 5-4: Line Package - L
Symbol Definition R S Duration
0-9, #, *, ABCD DTMF tones BR
hd**
hu**
hf Flash hook x
aw Answer tone x OO
bz Busy tone TO 30 sec
ft Fax tone x
mt Modem tones x
dl 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 x
wt Waiting tone
ci (ti,nu,na) Caller Id (ci(time, number, name) Time =
Sup[addr(“digits”)] DTMF dialing BR
of Report Failure x
Off hook transition x
On hook transition
MM/DD/HH/MN
** Persistence
Events
x
BR
Version 4.0 71 October 2002
Page 72
MP-1xx
5.2.5.4 PacketCable (NCS) Line Package - L
Table 5-5: PacketCable (NCS) Line Package - L
Symbol Definition R S Duration
0-9, *, #, A,B,C,D DTMF tones x BR
aw Answer tone x
bz Busy tone TO 30 seconds
cf Confirmation tone BR
ci(ti, nu,na) Caller Id BR “ti” denotes time, “nu”
denotes number, and “na”
denotes name
dl Dial tone TO
ft Fax tone x
hd Off-hook transition P,S
hf Flash hook P
hu On-hook transition P,S
mt Modem tones x
mwi Message waiting indicator TO 16 seconds
oc Operation complete x
of Operation failure x
ot Off-hook warning tone TO Time-out = infinite
r0, r1, r2, r3, r4, r5,
r6 or r7
rg Ringing TO 180 seconds
ro Reorder tone TO 30 seconds
rt Ring back tone C,TO 180 seconds
sl Stutter dial tone
wt1, wt2, wt3, wt4 Call waiting tones BR
x DTMF tones wildcard x Matches any of the digits
Distinctive ringing (0…7) TO 180 seconds
“0-9”
MP-1xx User’s Manual 72 Document #: LTRT-00714
Page 73
MP-1xx User’s Manual 5. Operation & Configuration
5.2.5.5 Announcement Package - L
Table 5-6: Announcement Package - L
Symbol Definition R S Duration
ann(index) Play an announcement TO Variable
oc Report on completion x
of Report failure x
Version 4.0 73 October 2002
Page 74
MP-1xx
5.3 MEGACO Protocol
5.3.1 MEGACO Overview
MEGACO (Media Gateway Control) Protocol is a standard network-based
control protocol (based on IETF RFC 3015 document and ITU-T
recommendation H.248 V1). MEGACO assumes a call control architecture
where the call control intelligence is outside the media gateway (the
MediaPack board in this case) and handled by an external Media Gateway
Controller (MGC). MEGACO is a master/slave protocol, where the gateway is
expected to execute commands sent by the Call Agent (another name for
MGC).
The connection is handled using two elements: Terminations and Contexts.
A Termination is the basic element of the call. There is a physical
Termination, representing a physical entity (e.g., analog line), and an
ephemeral Termination representing the generated stream. To create a
connection, a Context is used.
A Context contains 1 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).
Note that as this is a standard control protocol, AudioCodes does not provide
any special software library to enable Users to construct their own Call Agent
(many such stacks are available in the market and the User is able to choose
any one of them).
5.3.2 MEGACO Operation
5.3.2.1 Executing MEGACO Commands
MEGACO commands, received from an external Call Agent through the IP
network, are decoded and executed in the board. . Both text encoding and
binary encoding are supported. Commands can create new connections,
delete connections, or modify the connection parameters.
There are several commands that support the basic operations required to
control a media gateway:
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 effects the whole gateway.
Connection commands: The commands Add, Move, Modify and Subtract
allow the creation and deletion of call connection inside the media gateway.
These commands allow the application to create new connections, delete
MP-1xx User’s Manual 74 Document #: LTRT-00714
Page 75
MP-1xx User’s Manual 5. Operation & Configuration
existing connections, and modify the connection parameters.
Notify command: The Notify command is used by the gateway 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 gateway about the Termination’ configurations and state. This
information helps in managing and controlling the gateway.
The MEGACO gateway 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 gateway registration, the
session can start. From now on, the gateway responds to the MGC
commands. Even the notifications are sent only if the MGC requested them
specifically. If the KeepAlive mechanism is enabled, the gateway sends a
NOP serviceChange command when it detects a long period with no
commands from MGC. (The current period is set to 8 seconds.) If no response
is received from the MGC, the retransmission mechanism works and
eventually causes a new serviceChange to be sent to the next available MGC.
5.3.2.2 Setting MEGACO Call Agent IP Address and Port
Users can provide the gateway with up to 5 IP addresses of the MEGACO
Call Agents using the parameters ‘ProvisionedCallAgents’ and
‘ProvisionedCallAgentsPorts’ (shown in Table 7-3: MEGACO-Specific
Parameters).
The first Call Agent in the list is the primary one. In the case of connection
loss, the gateway tries to connect with the next on the list, and continues
trying until one of the Call Agents accepts the registration request. The actual
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, the MEGACO can not be
operational.
Instead of defining an IP address, Users can use a domain name for the call
agent, using the ‘CallAgentDomainName’ parameter. When using it, the User
should define also the ‘DNSPRISERVERIP’ and ‘DNSSECSERVERIP’
parameters (refer to Table 7-3: MEGACO-Specific Parameters). When using a
domain name, the gateway will resolve the name on each disconnection,
allowing the User to switch to another call agent.
5.3.2.3 Handling Events
Events are declared in an eventsDescriptor. This descriptor has an ID, and a
list of events that the call agent wants to be notified about. Up to 4 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 will get a notification when digit starts (dd/std{tl=d1}), and when it ends
(dd/etd{tl=d1}). The event dd/d1 will not be sent, as it is included in the other
Version 4.0 75 October 2002
Page 76
MP-1xx
two. An event can have parameters, for example the KeepActive flag. When
the event is received and it has the KeepActive flag, it will not stop the
currently played signals.
An event can have an embedded descriptor in it. It can be a signalsDescriptor
(see next section), a new eventDescriptor, or both. The embedded descriptor
replaces the current descriptor.
5.3.2.4 Playing Signals
Signals in MEGACO reside in a signalDescriptor. Only one signal is allowd in
the descriptor, as the boards cannot play more than one signal at a time.
However, this one signal can be of the type signalList. In this case, there can
be up to 30 signals in the list, and they will be played one after the other, until
the list ends or the execution is interrupted. Interrupting the execution can be
one of the following:
Event – Only events that were required by the Call agent stop the
execution, and only if they don’t 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 will be ignored.
Subtracting the termination from the call.
When a signal is ended, a signal completion notification will be sent only if:
The signal has the notifyCompletion parameter, and the completion
reason (TimeOut, Interruptted by Signal, Interrupted by Event)
matches one of the notifyCompletion parameters.
The events descriptor contains the signal completion event (g/sc).
The notification will include the signal id that was ended, and the signal list id if
it was a signal list.
A signal duration can be defined as a parameter in the signal. If omitted, a
default value is used, (refer to the packages description).
The signals to be played should be defined by the user in a call progress
tones (CPT) file. An off-line utility is supplied to convert this file to a binary file.
Each tone has a toneId in the file, which is used by the MEGACO when
playing the signal. For the correlation between signal names and CPT file IDs,
refer to the package tables in Section 5.3.3, Supported MEGACO Packages,
in the column “Map to CPT file”. When a CPT file is missing, the board defines
default values only for the following signals:
Dial tone
MP-1xx User’s Manual 76 Document #: LTRT-00714
Page 77
MP-1xx User’s Manual 5. Operation & Configuration
Ringing tone
Busy tone
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}}}}}
5.3.2.5 SDP Support in MEGACO
The MEGACO supports the basic SDP, as defined in RFC 2327. It supports
also the SDP-ATM, as defined in RFC 3108. However, the only supported
attributes in the 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: 97 is the payload number to be used
G723 is the encoding 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: : 97 is the payload number to be used
Version 4.0 77 October 2002
Page 78
MP-1xx
bitrate is a parameter of G.723 coder.
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 in on (yes or
no)
• PTIME
Defines the paketization time for the session. The format is:
a=ptime:20
5.3.2.6 Mapping of Payload Numbers to Coders
The following table 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 board defines
which coder is supported on this board).
Table 5-7: MGCP/MEGACO Mapping of Payload Numbers to Coders
(continues on pages 78 to 80)
Default Payload Number Encoding Name Coder
0 “PCMU” G711Mulaw
2 "G726-32" G726_32
3 "GSM" GSM
84 “GSM-EFR” GSM-EFR
4 "G723" G723 (High)
80 "G723" G723 (Low)
8 "PCMA" G711Alaw_64
15 "G728" G728
18 "G729" G729
35 "G726-16" G726_16
36 "G726-24" G726_24
MP-1xx User’s Manual 78 Document #: LTRT-00714
Page 79
MP-1xx User’s Manual 5. Operation & Configuration
Table 5-7: MGCP/MEGACO Mapping of Payload Numbers to Coders
(continues on pages 78 to 80)
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 "EVRC" EVRC
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
Version 4.0 79 October 2002
Page 80
MP-1xx
Table 5-7: MGCP/MEGACO Mapping of Payload Numbers to Coders
(continues on pages 78 to 80)
Default Payload Number Encoding Name Coder
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 )
69 "AMR" AMR (7.95 )
70 "AMR" AMR (10.2)
71 "AMR" AMR (12.2)
96 “telephone-event” RFC2833
104 “RED” Redundancy per RFC2198
13 “CN” Comfort Noise
MP-1xx User’s Manual 80 Document #: LTRT-00714
Page 81
MP-1xx User’s Manual 5. Operation & Configuration
5.3.3 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 client supports the basic set of packages as
defined in Annex E of the RFC 3015 document.
In addition to the Annex E packages, the MEGACO supports currently the
following packages (See tables below for the exact packages supported):
Annex K – Generic announcements package.
Enhanced Alerting packages from draft-boyle-megaco-alerting-02.txt
(only for the analog boards)
Q.1950 tone packages: Expanded Call Progress Tones Generation
package, Basic Services Tones Generation Package, Expanded
Services Tones Generation Package
Enhanced Analog Line Packages from draft-taylor-megaco-enhalpkgs-00.txt
Note: Unlike MGCP control protocol, the MEGACO must define ALL the events it
with which it needs to be notified. There are NO persistent events in the
MEGACO protocol.
5.3.3.1 Generic Media Package: G
Table 5-8: Generic Media Package: G
Symbol Definition Type
cause General failure report event
sc Signal completion event
Notes for Tables on MEGACO Packages (Table 5-9 to Table 5-27):
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
TO signal: The Timeout signal lasts for a given duration unless it is
Version 4.0 81 October 2002
Call Agent to turn it OFF, and vice versa.
Page 82
MP-1xx
superseded by a new signal.
BR signal: The Brief signal event has a short, known duration.
Duration: Specifies the duration of TO signals.
5.3.3.2 Base Root Package: ROOT
Table 5-9: Base Root Package: ROOT
Symbol Definition Type
maxNumberOfContexts Maximal number of contexts in the GW property
maxTerminationsPerContext Maximal Terminations in a Context. property
normalMGExecutionTime Timer for Retransmission property
normalMGCExecutionTime Timer for Retransmission property
ProvisionalResponseTimerValue Timer for Retransmission property
5.3.3.3 Tone Generator Package: ToneGen
Table 5-10: Tone Generator Package: ToneGen
Symbol Definition Type S Duration
pt Plays audio tone Signal BR
5.3.3.4 Tone Detection Package: ToneDet
Table 5-11: Tone Detection Package: ToneDet
Symbol Definition Type
std Detect the start of a tone Event
etd Detects the end of a tone Event
ltd Detects a long tone Event
MP-1xx User’s Manual 82 Document #: LTRT-00714
Page 83
MP-1xx User’s Manual 5. Operation & Configuration
5.3.3.5 DTMF Generator Package: DG (Extends ToneGen)
Table 5-12: DTMF Generator Package: DG
Symbol Definition Type S 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.0 83 October 2002
Page 84
MP-1xx
5.3.3.6 DTMF Detection Package: DD (Extends ToneDet)
Table 5-13: 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
MP-1xx User’s Manual 84 Document #: LTRT-00714
Page 85
MP-1xx User’s Manual 5. Operation & Configuration
5.3.3.7 Call Progress Tone Generator Package- CG (Extends
ToneGen)
Table 5-14: Call Progress Tones Generator Package- CG
Symbol Definition Type S Duration Map to CPT file
dt Dial tone Signal TO 180 sec 1
rt Ringing tone Signal TO 180 sec 2
bt Busy tone Signal TO 180 sec 3
ct Congestion tone Signal TO 180 sec 4
sit Special Information
Tone
wt Warning Tone Signal TO 180 sec 16
pt Payphone
Recognition Tone
cw Call Waiting Tone Signal BR 1 sec 9
cr Caller Waiting Tone Signal TO 180 sec 15
Signal BR 2 sec 5
Signal Not supported
5.3.3.8 Call Progress Tones Detection Package- CD (Extends
ToneDet)
Table 5-15: 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
Version 4.0 85 October 2002
Page 86
MP-1xx
5.3.3.9 Analog Line Supervision Package - AL
Table 5-16: Analog Line Supervision Package- AL
Symbol Definition Type S Duration
of Off hook transition Event
on On hook transition Event
fl Flash hook Event
ri Ringing on the line Signal TO 180 sec
5.3.3.10 Network Package- NT
Table 5-17: Network Package- NT
Symbol Definition Type
jit Maximal jitter buffer size Property
netfail Network failure Event
qualert Quality alert Event
dur Termination’s InContext duration Statistics
os Octets sent Statistics
or Octets received Statistics
5.3.3.11 RTP Package- RTP (Extends: NT)
Table 5-18: RTP Package- RTP
Symbol Definition Type
pltran Payload Transition Event
ps Packets sent Statistics
pr Packets received Statistics
pl Packet loss Statistics
jit Current inter-arrival jitter value Statistics
delay Current packets propagation delay Statistics
MP-1xx User’s Manual 86 Document #: LTRT-00714
Page 87
MP-1xx User’s Manual 5. Operation & Configuration
5.3.3.12 TDM Circuit Package – TDMC (Extends - NT)
Table 5-19: TDM Circuit Package - TDMC
Symbol Definition Type
ec Maximal jitter buffer size Property
gain Gain control Property
5.3.3.13 Generic Announcement Package - AN
Table 5-20: Generic Announcement Package
Symbol Definition Type Supported parameters
apf Initiates the play of a fixed
announcement
apv Initiates the play of a
variable announcement
Signal An – Announcement number
Av – Used as a barge-in value
Noc – Number of cycles
Signal Treated just like apf
5.3.3.14 Expanded Call Progress Tones Generator Package XCG (Extends - ToneGen)
Table 5-21: Expanded Call Progress Tones Generator Package - XCG
Symbol Definition Type S Duration Map to CPT file
cmft Comfort tone Signal TO 180 sec 18
roh Off-hook warning
tone
nack Negative
Acknowledgement
vac Vacant Number Tone Signal TO 180 sec 20
spec Special Conditions
Dial Tone
Signal TO 180 sec 16
Signal TO 180 sec 19
Signal TO 180 sec 21
Version 4.0 87 October 2002
Page 88
MP-1xx
5.3.3.15 Basic Service Tones Generation Package - SRVTN (Extends - ToneGen)
Table 5-22: Basic Service Tones Generation Package - SRVTN
Symbol Definition Type S Duration Map to CPT file
rdt Recall Dial Tone Signal TO 180 sec 22
conf Confirmation Tone Signal BR 1 sec 8
ht Held Tone Signal TO 180 sec 23
mwt Message Waiting
Tone
5.3.3.16 Expanded Services Tones Generation Package XSRVTN (Extends - ToneGen)
Table 5-23: Expanded Services Tones Generation Package - XSRVTN
Signal TO 180 sec 17
Symbo
l
Xferdt Call Transfer Dial Tone Signal TO 180 sec 24
Cft Call Forward Tone Signal BR 1 sec 25
Ccst Credit Card Service
Srdt Special Recall Dial
Definition Type S Duration Map to CPT file
Signal BR 1 sec 26
Tone
Signal TO 180 sec 27
Tone
5.3.3.17 Enhanced Alerting Package - ALERT
Table 5-24: Enhanced Alerting Package - ALERT
Symbol Definition Type S Duration Map to CPT file
Ri Ring Signal OO 60 sec Pattern parameter
refers to the ID of
distinctive ringing
Rs RingSplash Signal BR Not Supported
Cw Call Waiting Signal BR 1 sec 9 (Pattern
parameter not
used)
MP-1xx User’s Manual 88 Document #: LTRT-00714
Page 89
MP-1xx User’s Manual 5. Operation & Configuration
5.3.3.18 Analog Display Signaling Package – ANDISP (Extends:
ALERT)
Table 5-25: Analog Display Signaling Package - ANDISP
Symbol Definition Type S Duration Map to CPT file Note
dwa Display With
Alert
data Generic
Data
Signalling
Signal BR Time
needed for
the
CallerId
transmissio
n
Signal BR Time to
transmit
data
Pattern
parameter refers
to the ID of
distinctive ringing
none
To see the
callerId, the
ringing off-time
should be more
than 500 msec.
5.3.3.19 Extended Analog Line Supervision Package – XAL (Extends:
AL)
Table 5-26: Extended Analog Line Supervision Package- XAL
Symbol Definition Type S Duration Map to CPT file Note
las Line-side
Answer
Supervision
nd Network
Disconnect
Signal OO Until
turned off
Signal BR none Uses forced
none Uses
reversal
polarity
disconnect
5.3.3.20 FXO Package - FXO
Table 5-27: FXO Package – FXO
Symbol Definition Type S Duration
of Off hook transition Signal BR
on On hook transition Signal BR
fl Flash hook Signal BR
ri Ringing on the line Event TO 60 sec
Version 4.0 89 October 2002
Page 90
MP-1xx
5.3.4 MEGACO Terminations Naming
The basic entities that are controlled by MEGACO protocol are called
Terminations. There are physical Terminations, which represent a physical
entity, and ephemeral Terminations, which represent the stream. The
ephemeral Terminations exist only during a connection.
Physical Terminations names have up to two components: The gateway (in
this case, the MediaPack device name and the endpoint name.
Ephemeral Terminations names have two components: The gateway name,
and a constant string – ‘RTP/’. for RTP terminations and ‘ATM/’ for ATM
terminations. So assuming that the gateway name is ‘gw’, if first ephemeral
termination is of RTP type, it will be called ‘gwRTP/1’ and if it is of ATM type it
will be called ‘gwATM/1’.
The name parts can be set by the user, using the following parameters, the
last two being used only for physical terminations, (refer toTable 7-3:
MEGACO-Specific Parameters).
‘GATEWAYNAME’, ‘TRUNKNAME’, ‘ENDPOINTNAME’.
Note that the ‘/’ should be part of the name used. It is not added automatically.
The default values forthe termination name parts depends on the board type:
For analog boards (such as MP-104, MP-108, MP-124), the default
gateway name is NULL, the trunk name is not used, and the
endpoint name is ‘line/’. So the first line on an analog board when
using defaults will be ‘line/1’.
The endpoint number corresponds to the number of the analog port (i.e., line/2
corresponds to analog port #2). The numbering plan of the analog ports can
be found in the board-specific Installation and User’s Manual.
MP-1xx User’s Manual 90 Document #: LTRT-00714
Page 91
MP-1xx User’s Manual 5. Operation & Configuration
5.4 TPNCP Profile
5.4.1 TPNCP Overview
TPNCP (TrunkPack Network Control Protocol) is AudioCodes’ proprietary
network-based protocol. TPNCP can use either the UDP or TCP transport
layer. BoardNetworkSettings.TPNCPControlTransportType board
configuration parameter controls the selection between the different transport
layers. Using TPNCP, the User can use a large functions set from different
user libraries, provided by AudioCodes VoPLib. The following tables list the
usable functions, where the term “Usability” indicates that this function may be
used by the MP-1xx.
5.4.2 VoP Library Functions
5.4.2.1 Library Initialization/Cleanup Functions
Table 5-28: Library Initialization/Cleanup Functions
Usability Function Purpose
Use acInitLib()
Use acCloseLib()
The acInitLib() function initializes the VoIP Library by setting call-back
functions, and initializing all static variables to their default values.
acCloseLib() terminates library operations and releases all related resources.
Initializes the VoIP Library.
Frees all VoIP Library resources.
5.4.2.2 Board Configuration Functions
Table 5-29: Board Configuration Functions
Usability Function Purpose
Don’t use acOpenBoard()
Don’t use acCloseBoard()
Use acOpenRemoteBoard()
Use acCloseRemoteBoard()
Use acResetRemoteBoard
Use acGetDefaultBoardParameters()
Use acGetBoardStatus()
Opens and initializes a board.
Closes a board.
Opens a board using TPNCP protocol.
Closes a board using TPNCP protocol.
Resets a board using TPNCP protocol.
Returns default board config structure.
Returns the current status of the board.
Version 4.0 91 October 2002
Page 92
MP-1xx
These functions open and close a board through TPNCP. When opening a
board, it is first initialized and then set up according to the parameters set by
the User. The function returns with a unique device handle, to be used
whenever this device is to be referenced in the future. The handle is the only
way the device can be identified once it has been opened.
5.4.2.3 Channel Configuration Functions
Table 5-30: Channel Configuration Functions
Usability Function Purpose
Use acOpenChannel()
Use acCloseChannel()
Use acGetDefaultChannelParameters()
Use acGetChannelParameters()
Use acChangeChannelParameters()
Use acQueryChannelParameters()
These functions handle channel setup. The acOpenChannel() function
initializes and sets up a channel according to the parameters set by the User.
The function returns with a unique channel handle, to be used whenever this
channel is to be referenced in the future. Users can also modify a channel’s
settings “on-the-fly” (that is, without stopping and restarting the channel) after
the channel has been initially set up by acOpenChannel().
Opens, initializes, activates a channel.
Closes a channel.
Returns default channel config structure.
Gets channel parameters.
Changes channel params “on-the-fly”.
Get channel parameters.
MP-1xx User’s Manual 92 Document #: LTRT-00714
Page 93
MP-1xx User’s Manual 5. Operation & Configuration
5.4.2.4 IVR-Supporting Functions
Table 5-31: IVR-Supporting Functions
Usability Function Purpose
Don’t use acAddVoicePrompt()
Use acPlayVoicePrompt()
Use acStopVoicePrompt()
Use acDial()
Use acStopDial()
Use acPlayCallProgressTone()
Use acStopCallProgressTone()
Use acRecord()
Use acPlay()
Use acStopRecord()
Use acStopPlay()
Use acGetChannelTransferState()
Adds User-defined voice prompt.
Plays User-defined voice prompt.
Stops Playing User-defined voice prompt.
Dials a string of DTMF/MF digits.
Stops Dialing a string of DTMF/MF digits.
Plays a User-defined call progress tone.
Stops Playing a call progress tone.
Records voice data to file/memory buffer.
Plays voice data from file/memory buffer.
Stops acRecord() operation.
Stops acPlay() operation.
Returns a channel’s Play/Record state.
These IVR-supporting functions support an Interactive Voice Response (IVR)
session by enabling Users to play either Call Progress Tones, DTMF/MF digits
or prerecorded voice prompts.
5.4.2.5 RTP/RTCP-Related Functions
Table 5-32: RTP/RTCP-Related Functions
Usability Function Purpose
Use acActivateRTP_RTCPChannel()
Use acGetRTP_RTCPAddress()
Use acRTCPSetExtension()
Starts RTP/RTCP transport.
Gets local RTP/RTCP IP address & port.
Sets RTCP extension message.
These RTP/RTCP-related function-setup parameters are required for the
RTP/RTCP protocols or to retrieve RTP/RTCP-related information.
Version 4.0 93 October 2002
Page 94
MP-1xx
5.4.2.6 Event Handling Functions
Table 5-33: Event Handling Functions
Usability Function Purpose
Use acGetEvent()
Gets events from board.
acGetEvent() returns the oldest event reported by the board. The types of
events that may be issued by the device are listed in the AudioCodes “VoPLib
Reference Library User's Manual”, Document #: LTRT-00744.
5.4.2.7 Analog Interface Control Functions
Table 5-34: Analog Interface Control Functions
Usability Function Purpose
Use acAnalogIFSetLoopBack()
Use acAnalogIFQueryStatus()
Use acAnalogIFGenerateReversalPolarity()
Use acAnalogIFGenerateMeteringTonePulse()
Use acAnalogIFGenerateRing()
Use acAnalogIFGenerateDistinctiveRing()
Use acAnalogIFGenerateMessageWaiting
Indication()
Use acAnalogIFForcedDisconnect()
Use acGenerateRing()
Don’t use acSetHook()
Don’t use acAnalogIFSetHook()
Don’t use acAnalogIFGenerateFlash()
Activates/De-activates internal loop
back.
Query analog interface status.
Changes polarity of the voltage
between TIP-RING for FXS port.
Generates a metering pulse tone for
FXS port.
Generates/Stops ringing for FXS port
(same as acGenerateRing()).
Generates/Stops distinctive ring for
FXS port.
Generates/Stops a Message Waiting
Indication for FXS port.
Generates a short loop disconnect for
FXS port
Generates/Stops ringing for FXS port.
Sets FXO port to on-hook or off-hook
state.
Sets FXO port to on-hook or off-hook
state (same as acSetHook()).
Generates a “flashhook” for FXO port
MP-1xx User’s Manual 94 Document #: LTRT-00714
Page 95
MP-1xx User’s Manual 5. Operation & Configuration
These Analog Interface Control functions enable the User to control the
analog PSTN interface existing in some TrunkPack boards.
5.4.2.8 TFTP Server Related Functions
Table 5-35: TFTP Server Related Functions
Usability Function Purpose
Use acStartInternalTFTPServer()
Use acStopInternalTFTPServer()
Starts the internal TFTP server.
Stops the internal TFTP server.
5.4.2.9 Auxiliary Functions
Table 5-36: Auxiliary Functions
Usability Function Purpose
Don’t use acReplaceDSPSoftware()
Use acTestIPConnection()
Downloads new DSP software.
Tests if destination IP address is reachable.
5.4.2.10 Callback Functions
Table 5-37: Callback Functions
Usability Function Purpose
Use ErrorHandler()
Use TerminatePollingThreads()
Don’t use HotswapHandler()
These Callback functions should be written by the User. The functions are
called from inside the VoIP library.
Handles error reports from VoIP Library.
Terminates all threads accessing the board.
Handles Hot Swap activity detection.
Version 4.0 95 October 2002
Page 96
MP-1xx
5.4.2.11 Operating System Wrapper Functions
Table 5-38: Operating System Wrapper Functions
Usability Function Purpose
Use acSleep()
Use acSocket()
Use acCloseSocket()
Use acShutdown()
Use acBind()
Use acConnect()
Use acIOCtl()
Use acGetSockOpt()
Use acSetSockOpt()
Use acRecv()
Use acSend()
Use acRecvFrom()
Use acSendTo()
Use acGetHostByName()
Use acGetHostName()
Use acGetPeerName()
Use acGetLocalIPAddress()
This function delays the execution of program
for a specified length of time.
Opens a socket.
Closes a socket.
Shuts down a part of a full-duplex connection.
Gives the socket the local address.
Connects socket to the given remote address.
Control the mode of a socket.
Gets options on socket.
Sets options on socket.
Receives data from a connected socket.
Sends data on a connected socket.
Receives data from a connected/unconnected
socket.
Sends data to a specific destination.
Retrieves host information corresponding to a
host name from a host database.
Returns the standard host name for the local
machine.
Retrieves the name of the peer to which a
socket is connected.
Returns the local address of the given network
interface.
Users can customize AudioCodes’ software libraries to support their specific
operating system (usually when the User’s operating system is not one of the
operating systems supported by AudioCodes software libraries) as a standard
feature, such as Windows
Solaris
™
, VxWorks™ and pSOS™) using the operating system wrapper
™
NT, Windows™ 2000, Windows™ XP, Linux™,
mechanism.
To achieve this, Users should implement the operating system wrapper
MP-1xx User’s Manual 96 Document #: LTRT-00714
Page 97
MP-1xx User’s Manual 5. Operation & Configuration
functions listed above to fit their own operating system.
Usually, the functions described above are no more than a wrapper to
corresponding POSIX functions. Most are used as internal services by VoP
library functions. For details on the functions, arguments and options, refer to
any POSIX functions manual.
5.4.3 IP-Media Library
Not in use.
5.4.4 VoATM Library
Not in use.
5.4.5 PSTN Library Functions
Not in use.
Version 4.0 97 October 2002
Page 98
MP-1xx
MP-1xx User’s Manual 98 Document #: LTRT-00714
Page 99
MP-1xx User’s Manual 6. Management
6
6
6
M
M
M
a
a
a
n
n
n
a
a
a
g
g
g
e
e
e
m
m
m
e
e
e
n
n
n
t
t
t
Version 4.0 99 October 2002
Page 100
MP-1xx
Note 1: The MP-124 24-port, MP-108 8-port, MP-104 4-port and MP-102 2-port
Media Gateways have similar functionality except for the number of channels
(the MP-124 and MP-102 support only FXS), and all versions are referred to
collectively in these release notes as the MP-1xx.
Note 2: MP-10x refers to MP-108 8-port, MP-104 4-port and MP-102 2-port
gateways.
Note 3: MP-1xx/FXS refers only to the MP-124/FXS, MP-108/FXS, MP-104/FXS and
MP-102/FXS gateways.
Note 4: MP-10x/FXO refers only to MP-108/FXO and MP-104/FXO gateways.
This section describes SNMP Management. This section
also describes the Embedded Web Server and shows
supporting examples of screen information.
The section has the following subsections:
SNMP Management ................................................. 101
Embedded Web Server ........................................... 105
MP-1xx User’s Manual 100 Document #: LTRT-00714
Loading...