[asterisk-bugs] [JIRA] (ASTERISK-26630) Make logging PJPROJECT messages a bit easier

[Friendly Automation (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Friendly Automation closed ASTERISK-26630.
------------------------------------------

    Resolution: Fixed

> Make logging PJPROJECT messages a bit easier
> --------------------------------------------
>
>                 Key: ASTERISK-26630
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26630
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Core/General, Resources/res_pjsip/Bundling
>    Affects Versions: 13.13.0, 14.2.0
>            Reporter: Richard Mudgett
>            Assignee: Richard Mudgett
>
> Rusty was debugging an issue where Asterisk was sending a 481 response to an incoming CANCEL. In order to help troubleshoot, [~mmichelson] suggested using PJSIP's transaction layer messages to determine when the transaction was destroyed, and see if the CANCEL arrived after that.
> One problem though: the transaction level messages were not showing up in the debug. The problem was that using bundled PJProject, we set PJ_LOG_MAX_LEVEL to 3 in our config_site.h file. Changing that value to 5 and recompiling got the messages to show up as expected.
> What this means is, in order to have high level PJProject messages show up in Asterisk logs, you have to:
> * Set PJ_LOG_MAX_LEVEL to a high enough value before compiling PJProject
> * Make sure that your pjproject.conf file associates those level messages to appropriate Asterisk log levels
> * Ensure that you have set core debug to a high enough value to make Asterisk debug messages get logged
> * Set up logger.conf so that debug messages are actually going to a file somewhere.
> That's a lot of hoops to jump through in order to get PJSIP messages into your logs. What is suggested to do is to try to eliminate at least one of these steps. Perhaps
> * Set PJ_LOG_MAX_LEVEL to a higher default value in bundled PJPROJECT, or
> * Use PJProject runtime API to set the max level based on whatever core debug is set to (or something similar), or
> * Eliminate the need for associating PJProject levels to Asterisk levels. Some sane default should be fine.



--
This message was sent by Atlassian JIRA
(v6.2#6252)