Inalp Networks SmartWare Release 2.10, Software Configuration Manual, Page: 267 / 357

Tone Configuration 267
Procedure
To configure a tone-set profile
Mode
configure
Command Purpose
Step 1 node (cfg)#profile call-progress-tone name Creates a call-progress-tone profile
with name
name and enters call-
progress-tone configuration mode.
Step 2 node (pf-callp)[ name ]#play duration
frequency1 level1 [frequency2 level2]
Defines a tone with duration duration ,
frequency frequency1 and volume level1 .
If a second frequency is defined both
frequencies are played in parallel and
for the same duration
Step 3 node (pf-callp)[ name ]#no play duration
Defines a pause of duration
milliseconds
Step 4 node (pf-callp)[ name ]#... Repeat step 2 and / or step 3 to define
a tone sequence. Always when you
enter a “play” or “no play” command,
it is appended to the already existing
tone.
Step 5 node (pf-callp)[ name ]#flush-play-list
Resets the tone cadence. Same as
deleting and re-creating the tone.
Example: Define the Belgian special information tone
The first line defines the first element of the tone: 330ms of 950Hz at –4dB. The second line the
element that is played when the first element has finished: 330ms of 144Hz at –4dB, and so on. The
last line defines a pause of 1 second after the three tones. The cadence is repeated infinitely.
SN(cfg)# profile call-progress-tone belgienSpec
SN(pf-callp)[belgien~]# play 330 950 -4
SN(pf-callp)[belgien~]# play 330 1400 -4
SN(pf-callp)[belgien~]# play 330 1800 -4
SN(pf-callp)[belgien~]# no play 1000
Tones and pauses can be arbitrarily sequenced up to a number of 10 elements per call-progress-tone.
The “default” call-progress-tone is an empty tone. The total number of different “play” elements
across all configured call-progress-tones must not exceed 15 (an error is thrown if it does). If the call-
progress-tone consists of only one element, this element has infinite duration. The
duration parameter
is ignored in this case.
Note: The play command is new since SmartWare Release 2.10. All your currently used
configuration, be it in config files on TFTP servers or stored in the startup-config of the SmartNode,
are automatically converted into the new format. In the running-config you always see the new
format, and also new tones have to be configured in the new format. The new tone configuration
format is not backwards compatible.
Software Configuration Guide Release 2.10, Revision 1.00