[Home]

Summary:ASTERISK-28329: RTCP - Error building JSON
Reporter:Andres Miedzowicz (amiedzow)Labels:
Date Opened:2019-03-07 16:19:22.000-0600Date Closed:2019-03-12 08:09:03
Priority:MinorRegression?
Status:Closed/CompleteComponents:Resources/res_hep_rtcp
Versions:16.1.0 16.2.0 16.2.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:OS: CentOS 6.7 Kernel: 2.6.32-573.22.1.el6.x86_64 Asterisk version: 16.1.0/16.2.0/16.2.1 Hardware: Dell PE R200Attachments:( 0) config.log
( 1) debug_log.txt
Description:When a call is established, logs indicating that there was an error building JSON appear every 5 seconds which is the frequency of RTCP packets.
Comments:By: Asterisk Team (asteriskteam) 2019-03-07 16:19:22.405-0600

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
By: Andres Miedzowicz (amiedzow) 2019-03-07 16:26:40.543-0600

This is the Asterisk debug log that shows the JSON error reported
By: Sean Bright (seanbright) 2019-03-07 16:29:13.196-0600

Are you building from source? If so can you attach your {{config.log}} file?
By: Andres Miedzowicz (amiedzow) 2019-03-07 16:32:01.716-0600

Asterisk was built from source. Attached is the config.log file
By: Sean Bright (seanbright) 2019-03-07 16:35:42.297-0600

Try configuring like this:

{code}
./configure --with-jansson-bundled
{code}

(You don't need the {{--with-pjproject-bundled}} with Asterisk 16+ - it is enabled by default)

Let us know if you still see the same error.
By: Corey Farrell (coreyfarrell) 2019-03-07 16:38:44.246-0600

Can you post the output of {{yum list installed '\*jansson\*'}} on the system where Asterisk is installed?
By: Andres Miedzowicz (amiedzow) 2019-03-07 16:53:50.905-0600

Hi Corey,

here it is:

[root@asterisk-lab asterisk]# yum list installed '\*jansson\*'
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
* base: ftp.swin.edu.au
* epel: epel.mirror.digitalpacific.com.au
* extras: ftp.swin.edu.au
* updates: ftp.swin.edu.au
Installed Packages
jansson.x86_64                                                                                                                2.11-1.el6                                                                                                           @epel
jansson-devel.x86_64                                                                                                          2.11-1.el6                                                                                                           @epel
By: Sean Bright (seanbright) 2019-03-07 17:10:54.248-0600

[~amiedzow], is there any chance you have another version on jansson installed on your library search path?

{code}
ldconfig --print | grep jans
{code}
By: Andres Miedzowicz (amiedzow) 2019-03-11 21:15:43.940-0500

Hi Sean,

I've re-installed Asterisk from source using the flag suggested:

./configure --with-jansson-bundled

and that seems to have fixed the issue as it installed a newer version of jansson.

By: Sean Bright (seanbright) 2019-03-12 08:09:04.024-0500

[~amiedzow], you most likely have multiple versions of Jansson on your runtime library search path.

We've [made a change|https://gerrit.asterisk.org/c/asterisk/+/11112] that will prevent Asterisk from starting up if it encounters this situation in the future.

Asterisk 16.3 will have this change when it is released.