Synopsis

Record a telephone conversation to a sound file

Description

• Monitor(ext,basename)
• Monitor(ext,basename,flags) — New feature added to CVS 2004-06-03

The Monitor command starts recording a channel. The channel's input and output voice packets are saved to separate sound files. You may change filenames during a recording by using the ChangeMonitor command. Recording continues until either the StopMonitor command is executed or the channel hangs up.
If you don't specify a full path, the file will be stored in the "monitor" subdir of the path specified with astspooldir in asterisk.conf (so default will be /var/spool/asterisk/monitor).

A more detailed description on recording with Asterisk can be found at Asterisk cmd Record.

Command Parameters

• ext: The sound file format to save in, which will be also used as the filename extension. Default: wav

• basename: The base filename to use when saving the sound files. If not supplied, the default basename is constructed on the channel name plus a number, for example, IAX2[foo@bar]-3. The channel's input voice packets will be saved to basename-in.ext and the output voice packets will be saved to basename-out.ext. The default location for saved files is the /var/spool/asterisk/monitor directory.

• flags: If flags contains the letter m, then when recording finishes, Asterisk will execute a unix program to combine the two sound files into a single sound file. By default, Asterisk will execute soxmix and then delete the original two sound files. Note that sox/soxmix may not necessarily understand the sound format (e.g. alaw) and can't therefore mix the in and out files down to one single file. You may specify a different mixing method by setting the MONITOR_EXEC channel variable to the path of the unix program you wish executed, then call Monitor to begin recording. At the completion of recording, the specified unix program will be executed with three command-line parameters: the two sound files and the filename where the program should save the combined sound file. In this situation, earlier versions of Asterisk will not delete the two original sound files; it's up to your program to do that if you need/wish to. The "m" flag is settable through the manager interface. Also see b - Don't begin recording unless a call is bridged to another channel.

Example 1

When a call is sent to extension 2060, recording of the call will begin, and the caller is sent to conference number 1 with the MeetMe command.

 exten => 2060,1,Answer
 exten => 2060,2,Wait(1)
 exten => 2060,3,Monitor(wav,myfilename)
 exten => 2060,4,Meetme(1,ps)

For an extensive example of using Monitor, see:

• Monitor Setup Example

Example 2: 512 Simultaneous Calls with Digital Recording

How to use a RAM disk to eliminate the I/O bottleneck associated with digitally recording calls via the Monitor application:

• Original posting by Matt Roth
• Follow-Up with more details

See also

• MixMonitor: Monitoring & recording with native call leg mixing (Asterisk 1.2)
• Recording Calls with Asterisk
• Asterisk cmd Dial with options w or W for in-conversation recording (Asterisk v1.2.x)
• SoX Sound processing software
• AgentMonitorOutgoing: Monitor an agent's outgoing call
• Record: Record a channel
• ControlPlayback: Play a recording to the user
• PlaySip: SIP tool that can be used for recording
• Asterisk cmd Monitor Cleanup: Cleanup those pesky in and out files.
• Monitor stereo-example Example on how to record in stereo using MP3 compression

---

Asterisk | Configuration | Asterisk config extensi
ons.conf|The Dialplan - extensions.conf | Dialplan Commands