Dialplan Reload Not Showing Debug Info Even With Debug On (ast 15.5)

Home » Asterisk Users » Dialplan Reload Not Showing Debug Info Even With Debug On (ast 15.5)
Asterisk Users 3 Comments

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 -rvvvvvddddd
(enters console)
dialplan reload Dialplan reloaded.
[…]
— pbx_config successfully loaded 125 contexts (enable debug for details).

—

3 thoughts on - Dialplan Reload Not Showing Debug Info Even With Debug On (ast 15.5)

  • 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
    —————-

  • 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 -rvdddd 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!
    —

  • When you connect to a remote asterisk with the -r option, there are a couple commands automatically sent every time. These automatic commands tell the remote asterisk what verbose and debug level you passed on the command line.

    core set verbose at least X silent core set debug atleast X

    That is why the debug level does not go down. Another thing is that the debug level is global to the system. Thus if you set the level in one connection it affects all connections including future ones. The verbose level is per connection.

    Richard