Re: [asterisk-users] dialplan reload not showing debug info even with debug on (ast 15.5)
OK, many thanks for that. Not sure I see the point of the change, but at least I can get the info back by changing console => notice,warning,error to console => notice,warning,error,debug That said, dialplan reload seems to show significantly fewer items than before. I've got loads of extensions, and it does indeed seem to reload them all, but only shows about 1/4 of them in the console when doing dialplan reload. Hmmm... Incidentally, just while I'm here, is there a particular reason that debug can only every be pushed higher when connecting to the console? it's always been the case since I started using Asterisk 3 years ago so I guess there's a reason, and I never questioned it before. I'm just curious! For example: asterisk -rvddd Core debug was 2 and is now 3. asterisk -rv Core debug was 3 and is now 4. asterisk -rvdd Core debug is still 4. asterisk -rvd Core debug is still 4. But it always respects "core set debug" in whichever direction of verbosity is required. Thanks again! On Sun, 29 Jul 2018 at 13:14, Richard Mudgett wrote: > > > > On Sat, Jul 28, 2018 at 1:10 PM, Jonathan H wrote: >> >> I've not needed to do a dialplan reload for a while, so I don't know >> exactly which version is stopped working, but on 15.5, I'm not seeing >> ANY debug info at any debug level. >> So I'm not really sure how to find mistakes in the dialplan. This is >> all I get... how do I enable this debug mode to see the previous >> behaviour? Thanks >> >> asterisk -rvd >> (enters console) >> dialplan reload >> Dialplan reloaded. >> [...] >> -- pbx_config successfully loaded 125 contexts (enable debug for >> details). > > > Many of those messages now go out as DEBUG level 1 messages. You would > need to enable those to go out to your console in logger.conf if they aren't > enabled. > Or you need to look at one of the logging files (like full) that has debug > messages > routed to it. > > https://issues.asterisk.org/jira/browse/ASTERISK-27084 is the issue that did > that > which went out in v15.3.0 and is mentioned in the CHANGES file: > > Core > -- > * During dialplan reload log messages are produced for each context, >extension and include. These messages are no longer printed by the >verbose loggers, they are now only logged as debug messages. > > > Richard > -- > _ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > Check out the new Asterisk community forum at: https://community.asterisk.org/ > > New to Asterisk? Start here: > https://wiki.asterisk.org/wiki/display/AST/Getting+Started > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: >http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk? Start here: https://wiki.asterisk.org/wiki/display/AST/Getting+Started asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Any way of "flattening out" 2 channels back into one?
On Sat, Jul 28, 2018 at 4:08 PM, Jonathan H wrote:
> Last question for today, I promise!
>
> The problem: In order to disconnect calls after x minutes, I need to do
> this:
>
> [setup]
> exten => setup,1,Answer()
> same => n,Set(LIMIT_PLAYAUDIO_CALLER=yes)
> same => n,Set(LIMIT_WARNING_FILE=/var/lib/asterisk/sounds/en_GB_TNS/
> time_limit_reached)
> same => n,Dial(Local/s@root/n,3,L(354:6))
> same => n,Hangup()
>
> [root]
> exten => s,1,Verbose(1,Call to: ${CALLERID(name)} from: ${CALLERID(num)})
> same => n,Set(CHANNEL(hangup_handler_push)=hdlr1,s,1)
>
> etc etc
>
> Works well, but the result is it looks like there are 2 active calls
> in the console. Is there any way of forcing the drop of a call after x
> minutes without doing this "double dialling" business?
>
Heh. This is similar to the example given describing local channel
optimization [1] and
what happens to state information on those channels when local channels
optimize out.
The "call" counter you mention from the CLI "core show channels" output is
an
approximation and is not very accurate. Asterisk has no concept of what a
"call" is.
That counter simply counts the number of channels that started PBX's to
execute
dialplan normal. In your dialplan you have two channels that do this and
thus two
"calls" are counted.
If you want to eliminate the "double dialing" business avoid using local
channels. Have your
incoming PJSIP channels call other PJSIP channels directly. Or you can
make it so the
local channels can optimize themselves out. Remember you cannot have state
information
stored on an optimizing local channel as that information goes away when
the local
channels optimize out.
The Dial 'L' option currently puts state on the caller and called channels
depending on which
features are configured (who hears things). If you set the verbose level
to 4 you get information
in the log about that.
Richard
[1] https://wiki.asterisk.org/wiki/display/AST/Local+Channel+Optimization
--
_
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Check out the new Asterisk community forum at: https://community.asterisk.org/
New to Asterisk? Start here:
https://wiki.asterisk.org/wiki/display/AST/Getting+Started
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] dialplan reload not showing debug info even with debug on (ast 15.5)
On Sat, Jul 28, 2018 at 1:10 PM, Jonathan H wrote: > I've not needed to do a dialplan reload for a while, so I don't know > exactly which version is stopped working, but on 15.5, I'm not seeing > ANY debug info at any debug level. > So I'm not really sure how to find mistakes in the dialplan. This is > all I get... how do I enable this debug mode to see the previous > behaviour? Thanks > > asterisk -rvd > (enters console) > dialplan reload > Dialplan reloaded. > [...] > -- pbx_config successfully loaded 125 contexts (enable debug for > details). > Many of those messages now go out as DEBUG level 1 messages. You would need to enable those to go out to your console in logger.conf if they aren't enabled. Or you need to look at one of the logging files (like full) that has debug messages routed to it. https://issues.asterisk.org/jira/browse/ASTERISK-27084 is the issue that did that which went out in v15.3.0 and is mentioned in the CHANGES file: Core -- * During dialplan reload log messages are produced for each context, extension and include. These messages are no longer printed by the verbose loggers, they are now only logged as debug messages. Richard -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk? Start here: https://wiki.asterisk.org/wiki/display/AST/Getting+Started asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
