As soon as your Apply Changes, your change will be overwritten. If you’re going to do this, you’re going to need to use extensions_custom.conf or the “extensions override” config file.
I’m also pretty sure that some of the parameters you are trying to pass to MixMon aren’t preset for you, so you’re probably going to need some variable setting steps in your context as well.
I’ve found that one of the easiest ways to learn about contexts is to look in /var/log/asterisk/full.
In there, you will find examples of contexts being actually executed, including the setup steps. For example, your MixMonitor() looks perfectly sensible, but look for that in the log file and you’ll see dozens of steps setting that function call up.
One last item - I don’t know about Intercoms at all, but this doesn’t seem like something that would work, even if you get the syntax right. Intercom traffic is handled on its own merits, so MixMinitor() may or may not be able to interact with the Intercom subsystem.
Are you looking to only record this call when it is answered via Intercom mode or just record the call in general? The first option is going to require custom dialplan while the second requires you to enable call recording on the extension.
Well actually, you need to enable the call recording on the extension regardless.
You aren’t making sense. Call Recording has nothing to do with the Intercom. Intercom is a method of calling the device and sending an Auto Answer request to the device. Call Recording doesn’t care if the call was auto answered or answered just that it was answered and it will record the audio.
I understand that intercom recording and telephone conversations are not interconnected. But I don’t understand how to record conversations on the intercom. (I read the Internet and documentation, I can not find what I need).