[asterisk-bugs] [JIRA] (ASTERISK-28445) res_pjsip_session: ast_json_vpack: Invalid UTF-8 string on hangup when TEST_FRAMEWORK enabled

Petros Moisiadis (JIRA) noreply at issues.asterisk.org
Thu Jul 4 10:35:47 CDT 2019


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

Petros Moisiadis commented on ASTERISK-28445:
---------------------------------------------

We can confirm this issue with the asterisk package in Debian Buster. Moving the configuration to a .conf file resolves the issue, so the problem should be related with what __ast_test_suite_event_notify  is doing when realtime is used. However, debug information is not enough to understand exactly what could be wrong. Rebuilding the asterisk package without TEST_FRAMEWORK resolves the issue too.

> res_pjsip_session: ast_json_vpack: Invalid UTF-8 string on hangup when TEST_FRAMEWORK enabled
> ---------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-28445
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28445
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_session
>    Affects Versions: 16.2.1
>         Environment: Debian Buster
>            Reporter: Bernhard Schmidt
>            Assignee: Bernhard Schmidt
>            Severity: Minor
>              Labels: pjsip
>         Attachments: aor, endpoint
>
>
> On every hangup the following error is logged
> {code}
> [2019-06-12 00:11:07] ERROR[12584]: json.c:607 ast_json_vpack: Error building JSON from '{s: s, s: s, s: s, s: s, s: i, s: s}': Invalid UTF-8 string.
> [2019-06-12 00:11:07] ERROR[12584]:   Got 11 backtrace records
> # 0: /usr/sbin/asterisk(ast_json_pack+0x99) [0x5557a3eda459]
> # 1: /usr/sbin/asterisk(__ast_test_suite_event_notify+0x1be) [0x5557a3f6bbae]
> # 2: /usr/sbin/asterisk(__ao2_ref+0xa6) [0x5557a3e503a6]
> # 3: /usr/lib/asterisk/modules/res_pjsip_session.so(+0x6564) [0x7f8665c19564]
> # 4: /usr/sbin/asterisk(ast_taskprocessor_execute+0xd8) [0x5557a3f62f58]
> # 5: /usr/sbin/asterisk(+0x1821c0) [0x5557a3f6d1c0]
> # 6: /usr/sbin/asterisk(ast_taskprocessor_execute+0xd8) [0x5557a3f62f58]
> # 7: /usr/sbin/asterisk(+0x1819a4) [0x5557a3f6c9a4]
> # 8: /usr/sbin/asterisk(+0x18843f) [0x5557a3f7343f]
> # 9: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3) [0x7f868888efa3]
> #10: /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f) [0x7f86885e94cf]
> {code}
> Other than being a big fat RED ERROR in the console it seems to have no ill consequences. 
> There is no non-ASCII character in the callerid or in the dialplan
> Possibly related judging from the backtrace, the Debian package for Asterisk builds with TEST_FRAMEWORK to run the testsuite in CI tests.



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



More information about the asterisk-bugs mailing list