> The problem in this particular case is that the actual monitor object is on > A's > channel. When A is no longer involved in the call, the monitor is gone, and > so > the call cannot be recorded further. One possible solution is to run the > Monitor > application on B's channel instead. This can be done by using the M option in > the Dial application. The M option allows you to run a macro on the *called* > channel's party when he answers. If you start the Monitor application from > this > macro, you should find that things will work as you expect.
> Note that the issue you linked was about MixMonitor, not Monitor. They are > completely different beasts when it comes to how they operate. In fact, > MixMonitor recordings can be set to survive a transfer if you are using > Asterisk > 1.4.23 and make use of the AUDIOHOOK_INHERIT function. For more information > on > its use, you can issue the command "core show function AUDIOHOOK_INHERIT" > from > the Asterisk CLI. > Mark Michelson Thank you very much for your explanation! Gunnar Schaller _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
