On Wed, May 2, 2012 at 3:11 PM, Ben Langfeld <
b...@langfeld.co.uk> wrote:
> Are you sure it's Asterisk, and not your determination of the Channel
> header on the AMI action, that is at fault?
I'm not sure that I understand your question (English is not my native
language).
The AMI header looks like this:
DEBUG ami 2012-05-02 15:43:53 Sending AMI action:
>>> Action: monitor
>>> ActionID: pZWLT4gi-3OFk-emUX-6xiu-4GptK0BXJXuR
>>> Channel: Local/leg_a@some-context-9710;2
>>> File: /var/spool/asterisk/recordings/wav/121e0009a9327900c0b9b3d5d5db7426
>>> Mix: 0
>>>
(I edited the number and context name)
It always record, but sometimes leg a is is "in" and sometimes leg a
is "out" in the outcome, when i listen to the file itself.