[asterisk-bugs] [JIRA] (ASTERISK-27407) Boolean types in sorcery that map to yes/no Enum values are not correctly mapped to database
Sean Bright (JIRA)
noreply at issues.asterisk.org
Wed May 26 08:44:17 CDT 2021
[ https://issues.asterisk.org/jira/browse/ASTERISK-27407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Bright closed ASTERISK-27407.
----------------------------------
Resolution: Duplicate
> 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, Resources/res_pjsip_endpoint_identifier_ip, Resources/res_pjsip_outbound_registration, Resources/res_pjsip_publish_asterisk
> Affects Versions: 14.7.1, 15.1.1
> Environment: Debian 9 amd64 (irrelevant though)
> Reporter: Florian Floimair
> Severity: Major
>
> 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)
More information about the asterisk-bugs
mailing list