[asterisk-bugs] [JIRA] (ASTERISK-30344) ari: Memory leak in create when specifying JSON

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-30344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-30344:
--------------------------------------

    Summary: ari: Memory leak in create when specifying JSON  (was: Memory leaks in ARI when using Content-Type: application/json )

> ari: Memory leak in create when specifying JSON
> -----------------------------------------------
>
>                 Key: ASTERISK-30344
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30344
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_ari
>    Affects Versions: 18.11.3, 18.15.1, 20.0.1
>         Environment: Red Hat Enterprise Linux 8.5
> jansson-2.14-1.el8.x86_64
>            Reporter: Saken
>
> To make calls, we use ARI requests with Content-Type: application/json
> Memory leaks when creating a channel with variables.
> We tried 18.11.3 and latest  18.15.1 and 20.0.1 and all these versions are affected.
> Steps to reproduce:
> 1. Run asterisk with MALLOC_DEBUG
> 2. Check memory allocation in json
>     asterisk  -rx 'memory show summary' | grep json.c
> 3. Create a channel through postman
> Example POST request with Body in JSON format:
> http://asteriskhost:8088/ari/channels/create?endpoint=PJSIP%2F8707398****%40cusp&app=test&channelId=26&api_key=asterisk:asterisk
> { "variables": { 
> "CHANNEL(hangup_handler_push)": "hdlr1,s,1", "callid": "38", "callbackdatetime": "2022-12-07 17:19:00", "priority": "priority", "phone": "8707398****", "clientid": "clientid", "agreementid": "agreementid", "CONNECTEDLINE(num)": "9013****", "linetype": "Outbound", "skillgroupnumber": "skillgroupnumber", "sourcesystem": "    ", "mode": "auto", "camptype": "auto"} }
> 4. Check memory allocation in json after creating channel 
> asterisk  -rx 'memory show summary' | grep json.c



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