Automatic Update Facility - AudioCodes Mediant 2000 User Manual

Mgcp, megaco, tpncp voip mediant media gateways
Hide thumbs Also See for Mediant 2000:
Table of Contents

Advertisement

User's Manual
"CASTablesNum" - Indicates how many CAS protocol configuration files are
loaded. Its range is 1-8. It should match the number of "CASFileName_X" fields.
CASTableIndex_TrunkNum (TrunkNum should be an integer) - This field is a
CAS protocol file index. It indicates the CAS protocol file to use in a specific
Trunk. The index value corresponds to the number in the field "CASFileName_X".
SaveConfiguration - (default = 1 = enabled) This parameter replaces the following
parameters: BlastCallProgressSetupFile, BlastCASProtocolSetupFile,
BlastVoicePromptsFile. When enabled, all configuration and downloadable files
are stored in non-volatile memory.
6.4.2.2
Call Progress Tone and User-Defined Tone Auxiliary Files
The auxiliary source file for Call Progress Tones and User-Defined Tones contains the
definitions
detected/generated by the Mediant 2000. The Call Progress Tones are mostly used
for Telephony In-Band Signaling applications (e.g., Ring Back tone). Each tone can
be configured as one of the following types:
Continuous
Cadence (up to 4 cadences)
Burst
A tone can also be configured for Amplitude Modulated (AM) (only 8 of the Call
Progress Tones can be AM tones). The Call Progress Tones frequency range is 300
Hz to 1890 Hz.
The User-Defined Tones are general purpose tones to be defined by the user. They
can be set only as 'Continuous' and their frequency range is 300 Hz to 3800 Hz. The
maximum number of tones that may be configured for the User Defined and Call
Progress Tones together is 32. The maximum frequencies that may be configured in
the User Defined and Call Progress Tones together is 64. The Mediant 2000 sample
configuration file supplied by AudioCodes can be used to construct your own file.
The Call Progress Tones and User-Defined Tones file used by the Mediant 2000 is a
binary file with the extension tone.dat. Only this binary tone.dat file can be loaded to a
Mediant 2000. Users can generate their own tone.dat file by opening the modifiable
tone.ini file (supplied with the tone.dat file as part of the software package on the CD
accompanying the Mediant 2000) in any text editor, modify it, and convert the modified
tone.ini back into a binary tones.dat file using the DConversion Utility supplied with the
Mediant 2000 software package. (Refer to the Appendix, ''Utilities'' on page
description of the procedure for generating and downloading the Call Progress Tone
file using this utility.)
To load the Call Progress Tones and User-Defined Tones configuration file to the
Mediant 2000, correctly define their parameters in the Mediant 2000's ini file. (Refer
to' 'Initialization ('ini') Files'' on page
example.)
6.4.3

Automatic Update Facility

The Mediant 2000 is capable of automatically downloading updates to the ini file,
auxiliary files and firmware image. Any standard Web server, FTP server or NFS
server may be used to host these files.
The Automatic Update processing is performed:
Version 5.0
of
the
Call
Progress
71
6. Mediant 2000 Initialization & Configuration Files
Tones
and
User-Defined
64
for the ini file structure rules and ini file
Tones
to
be
471
for a
June 2006

Advertisement

Table of Contents
loading

Table of Contents