Yes I use ast_waitfor with 2nd parameter -1 into a detached background
thread. The function ast_waitfor used into my application function
called from the dialplan and also into the dtmf read thread. This
behavior is observed after bridging the incoming channel(the channel
where I try to read
vassilux . wrote:
Yes I use ast_waitfor with 2nd parameter -1 into a detached
background thread. The function ast_waitfor used into my application
function called from the dialplan and also into the dtmf read thread.
This behavior is observed after bridging the incoming channel(the
channel where
Thank for the information about the frame hook.
I understand that both functions can be called by different threads because
lock/unlock used internally.
2014-08-04 11:44 GMT+02:00 Joshua Colp jc...@digium.com:
vassilux . wrote:
Yes I use ast_waitfor with 2nd parameter -1 into a detached
vassilux . wrote:
Thank for the information about the frame hook.
I understand that both functions can be called by different threads
because lock/unlock used internally.
If you are referring to ast_waitfor and ast_read those functions are NOT
safe to be called form separate threads
ok Joshua thank again
2014-08-04 12:28 GMT+02:00 Joshua Colp jc...@digium.com:
vassilux . wrote:
Thank for the information about the frame hook.
I understand that both functions can be called by different threads
because lock/unlock used internally.
If you are referring to ast_waitfor
vassilux . wrote:
Hi,
Kia ora,
I try to read DTMF digits from a channel after calling ast_bridge_call.
There are a lot of errors about : called with no recorded file
descriptor from
static struct ast_frame *__ast_read(struct ast_channel *chan, int
dropaudio) function.
I can read DTMF
Hi,
I try to read DTMF digits from a channel after calling ast_bridge_call.
There are a lot of errors about : called with no recorded file
descriptor from
static struct ast_frame *__ast_read(struct ast_channel *chan, int
dropaudio) function.
I can read DTMF digits before execute
