[asterisk-bugs] [JIRA] (ASTERISK-28747) YES/NO attributes are not set properly when creating PJSIP sorcery objects via ARI

[George Joseph (JIRA)]

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

George Joseph commented on ASTERISK-28747:
------------------------------------------

We've had this issue before when sorcery writes to a database from ARI.  

Some of the database columns are defined as 
{noformat}
YESNO_VALUES = ['yes', 'no']
{noformat}

while others are defined 

{noformat}
AST_BOOL_VALUES = [ '0', '1',
                    'off', 'on',
                    'false', 'true',
                    'no', 'yes' ]
{noformat}

[~andresag] If you change "true" to "yes" in your ARI call it should work.  In the mean time, I'm opening an internal issue to fix the column definition.


> YES/NO attributes are not set properly when creating PJSIP sorcery objects via ARI
> ----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28747
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28747
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/AstDB, Core/Sorcery, Resources/res_ari
>    Affects Versions: 17.1.0
>         Environment: - CentOS release 7.7.1908 (Core) kernel 3.10.0-1062.4.3.el7.x86_64
> - mysql  Ver 15.1 Distrib 5.5.64-MariaDB
>            Reporter: Andrés Alonso
>            Assignee: Unassigned
>            Severity: Minor
>         Attachments: extconfig.conf, sorcery.conf
>
>
> When creating PJSIP object through the Sorcery API, *yes/no attributes* are not created according to the given payload data.
> For instance, creating an AOR object passing:
> * max_contacts=1
> * remove_existing=yes
> Request ends succesfully, but the resulting object has (pjsip show aor):
> * max_contacts: 1 (as expected)
> * remove_existing: *false*



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