search for: console_ind

Displaying 4 results from an estimated 4 matches for "console_ind".

Did you mean: console_id
2023 Sep 07
2
Asterisk 18.14.0 vs 18.18.0 and chan_console/chan_alsa
ok switching to "Console/default" does show the text --- <("<) --- Call to device 'default' on console from 'default' <2564286000> --- (>")> --- --- <("<) --- Auto-answered --- (>")> --- However I don't hear any audio. Thanks Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL:
2023 Sep 08
1
Asterisk 18.14.0 vs 18.18.0 and chan_console/chan_alsa
...;")> --- -- Called Console/default -- Console/default answered SIP/devgeis_to_nuc11cdev2-00000000 -- Channel Console/default joined 'simple_bridge' basic-bridge <e6f6e4e9-aa1f-452d-883d-65c4d93c59b1> [Sep 8 08:07:10] WARNING[282457][C-00000001]: chan_console.c:651 console_indicate: Don't know how to display condition 26 on Console/default -- Channel SIP/devgeis_to_nuc11cdev2-00000000 joined 'simple_bridge' basic-bridge <e6f6e4e9-aa1f-452d-883d-65c4d93c59b1> > 0x7feeec0086b0 -- Strict RTP learning complete - Locking on source address 192.1...
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
...lock issue that has not been resolved: > https://issues-archive.asterisk.org/ASTERISK-30481 > It's quite easy to reproduce, so it may be the case that the module is > currently unusable. > 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...