Displaying 2 results from an estimated 2 matches for "lock_info_destroy".
2023 Sep 08
1
Asterisk 18.14.0 vs 18.18.0 and chan_console/chan_alsa
On 9/8/2023 8:18 AM, Jerry Geis wrote:
> But when I do a second test. Asterisk HANGS on ChanIsAvail()
>
> Then I thought lets SKIP that - and just let it do the Dial() - I
> stopped everything - got it running again. - and then the Dial() hangs
> on the second call.
>
> So both ChanIsAvail() or Dial() both hang on the second call in.
>
> So only 1 call in will work.
2023 Sep 08
2
Asterisk 18.14.0 vs 18.18.0 and chan_console/chan_alsa
...le.
>
Well this is a bummer....
[Sep 8 08:45:28] WARNING[313684][C-00000001]: chan_console.c:651
console_indicate: Don't know how to display condition 26 on Console/default
--- <("<) --- Hangup on Console --- (>")> ---
[Sep 8 08:45:28] ERROR[313683]: utils.c:1027 lock_info_destroy: Thread
'stream_monitor started at [ 390] chan_console.c start_stream()'
still has a lock! - 'pvt' (0x55e647a245e0) from 'stream_monitor' in
chan_console.c:281!
How do we get this working????
Jerry
-------------- next part --------------
An HTML attachment was scrub...