Define the recording policy first
Choose the calls to record, who can retrieve recordings, retention duration and deletion process. Notification and consent requirements depend on jurisdiction and use case; resolve them for your deployment before enabling capture. A recording feature is not a compliance program.
Understand the application lifecycle
MixMonitor records channel audio through an audiohook. Its options determine behaviors such as recording only while bridged. StopMixMonitor is relevant when later dialplan work must safely use the completed recording file. Consult the Asterisk 22 application reference for the exact options you choose.
Keep filenames under server control
Use a controlled directory and a server-generated identifier. Do not concatenate untrusted caller ID or other call-supplied text into filenames or command arguments. Keep any post-processing execution separate from unvalidated input. Restrict filesystem access to the service and authorized operators.
Verify the result rather than the call alone
Place a consented test call, speak in both directions, transfer and hang up. Check that the expected recording exists, contains the intended audio and has the right ownership. Test disk-full handling and retention cleanup in a lab. If a call succeeds but a recording is empty, inspect recording scope, bridging and storage before changing SIP authentication.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.