Recording Sound Files
Sound files can be recorded for the identifier and to override node numbers on connection and disconnection.
Sound files can have any valid file name, but the extension must identify one of the supported formats (i.e. gsm, pcm, or ulaw)
Custom connect and disconnect messages can be specified to override the default numerical connect and disconnect messages. To do so, store a file with the same name as the numerical node to override and an extension indicating the the sound file format in /var/lib/asterisk/sounds/rpt/nodenames
A procedure to record the sound files using Audacity is documented here.
Sound File Locations
Asterisk searches a default sound file path of /var/lib/asterisk/sounds unless a path name is specified with the name of the sound file.
Asterisk/app_rpt stores its sound files in /var/lib/asterisk/sounds/rpt. Custom connect and disconnect messages are stored in /var/lib/asterisk/sounds/rpt/nodenames The sound file for the ID message is traditionally placed in /etc/asterisk so that Limey Linux systems will save the file across power cycles.
Supported Sound File Formats
Asterisk supports three sound file formats ulaw, pcm, and gsm. All sound files should be recorded at 8KHz in one of these formats. All files should be headerless.
Sound File Naming Convention
Note: When specifying an ID message file in rpt.conf, omit the extension and just supply the file name.
Custom Connect and Disconnect Messages
Creating Sound Files
- Login to post comments
Recent comments
1 year 2 weeks ago
1 year 2 weeks ago
1 year 2 weeks ago
1 year 2 weeks ago