Hi,
Thanks for your apt response.
I also tried by starting the recording before the dial command through AMI.
But in that scenario also, there are some issue such that both the streams are
not getting updated at the same time. Sometimes one stream takes nearly 2
seconds to getting
On Wed, Sep 10, 2008 at 9:48 AM, bala krishnan [EMAIL PROTECTED] wrote:
Hi,
Thanks for your apt response.
I also tried by starting the recording before the dial command through AMI.
But in that scenario also, there are some issue such that both the streams
are not getting updated at the
On Tue, Sep 9, 2008 at 3:19 PM, bala krishnan [EMAIL PROTECTED] wrote:
Hi,
The problem is, when i was starting the recording on zap channels
through AMI by Monitor command, always the out stream recorded as 0 bytes.
So that i did the searching and got the response that t option would
On Mon, Sep 8, 2008 at 11:39 AM, bala krishnan [EMAIL PROTECTED] wrote:
Hi,
To disallow the native bridge between the zap channels, i enabled the t
flag in the Dial application. But i dont want to allow the callee/caller to
transfer the call.
Why would you need this? It should just take
Hi,
To disallow the native bridge between the zap channels, i enabled the t flag
in the Dial application. But i dont want to allow the callee/caller to transfer
the call.
Could you please tell me if any configuration needs to set in such a way
to disallow the native bridge?
I am
