[asterisk-bugs] [JIRA] (ASTERISK-27407) Boolean types in sorcery that map to yes/no Enum values are not correctly mapped to database

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27407:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Boolean types in sorcery that map to yes/no Enum values are not correctly mapped to database
> --------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27407
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27407
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 14.7.1, 15.1.1
>         Environment: Debian 9 amd64 (irrelevant though)
>            Reporter: Florian Floimair
>
> When pushing configuration via ARI into Asterisk with a realtime database backend, values that match to a "yes"/"no" Enum value are not inserted into the database, leaving the respective row empty. Therefore Asterisk falls back to default values for these rows.
> The reason for this is the mapping of Boolean values (OPT_BOOL_T) in sorcery which causes the generated strings to be "true"/"false" rather than "yes"/"no". This has previously been identified by Mark Michelson and (partially) fixed in commit b6bd97eea2d, which introduced the new type OPT_YESNO_T.
> I already discussed this issue and the fix with Joshua Colp on the asterisk-dev mailing-list.
> Patch will follow shortly.



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