Thanks for the input. I think that works as my other recordings work. I will
test that again regardless.
Is there no real other way to know why MixMonitor fails or look more into
it?
Regards,
Bruce
On Wed, May 4, 2011 at 5:03 AM, salaheddine elharit <
salah.elharit...@gmail.com> wrote:
> hi
>
>
hi
you can add this in extenssion.conf
exten => 223,1,Answer()
exten => 223,2,MixMonitor(test_${UNIQUEID}.wav|av(0)V(0))
exten => 223,3,Dial(SIP/223)
exten => 223,4,Hangup()
i can record without any issue in /var/spool/asterisk/monitor
2011/5/4 Bruce B
> Thanks for the input.
>
> Yes, I
Thanks for the input.
Yes, I did call out many times, but the recording doesn't happen even after
the call is bridged and there is two way audio. I also took out the "b"
option and so it should recording the ringing right (even before call is
bridged) but it doesn't do that or any recording at all
Hi,
As per your Dialplan MixMonitor will work after call bridge, In you case
still call is not bridge. That's why MixMonitor is waiting of call bridge...
*MixMonitor(Q-${QDIALER_QUEUE}-${UNIQUEID}.WAV,b,)
option b=>** A bridge flag allows recording to only take place when the
channel is bridged.*
Hi everyone,
For some reason MixMonitor doesn't record when it should; It actually shows
the MixMonitor line just fine on the CLI. How can MixMonitor be debugged for
things like privilege issues or filename issues?
**I had this working at one point and then stopped working. Not sure what I
change
