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

[Andrés Alonso (JIRA)]

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

Andrés Alonso commented on ASTERISK-28747:
------------------------------------------

Goot to know, it makes sense actually. Thanks!
I've been testing it a bit more and same thing happens with several other yes/no fields in ps_endpoints.
I will probably try postgres integration, since I see the config sql scripts differ in many type definitions.

> 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)