[asterisk-bugs] [JIRA] (ASTERISK-26743) PJPROJECT: Detecting compiled max log level does not work.

[Friendly Automation (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234897#comment-234897 ] 

Friendly Automation commented on ASTERISK-26743:
------------------------------------------------

Change 4770 merged by George Joseph:
PJPROJECT logging: Fix detection of max supported log level.

[https://gerrit.asterisk.org/4770|https://gerrit.asterisk.org/4770]

> PJPROJECT: Detecting compiled max log level does not work.
> ----------------------------------------------------------
>
>                 Key: ASTERISK-26743
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26743
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip, Resources/res_pjsip/Bundling
>    Affects Versions: GIT
>            Reporter: Richard Mudgett
>            Assignee: Richard Mudgett
>
> The mechanism used for detecting the maximum log level compiled into the linked pjproject does not work.  The API call simply stores the requested level into an integer and does no range checking.  Asterisk was assuming that there was range checking and limited the new value to the allowable range.  To get the actual maximum log level compiled into the linked pjproject we need to get and save off the initial set log level from pjproject.  This is the maximum log level supported.
> The issue was found because building Asterisk with TEST_FRAMEWORK enabled needed pjsua to build with a lower max log level enabled.



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