[asterisk-bugs] [JIRA] (ASTERISK-29414) res_pjsip_outbound_publish reload with config change results in FRACK! error

Asterisk Team (JIRA) noreply at issues.asterisk.org
Mon May 24 12:00:16 CDT 2021


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

Asterisk Team commented on ASTERISK-29414:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> res_pjsip_outbound_publish reload with config change results in FRACK! error
> ----------------------------------------------------------------------------
>
>                 Key: ASTERISK-29414
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29414
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_outbound_publish
>    Affects Versions: 18.3.0
>            Reporter: Andrew Yager
>            Assignee: Andrew Yager
>
> Replacing an existing outbound publish entry with a new one and requesting pjsip reload creates records for bad objects.
> To reproduce:
> [publishconfig]
> type=outbound-publish
> server_uri=sip:192.168.1.1
> from_uri=sip:192.168.1.2
> expiration=3600
> event=dialog
> multi_user=yes
> @body=application/dialog-info+xml
> @context=^publish_hints
> and load asterisk
> now edit config:
> [publishconfig]
> type=outbound-publish
> server_uri=sip:192.168.1.1
> from_uri=sip:127.0.0.1
> expiration=3600
> event=dialog
> multi_user=yes
> @body=application/dialog-info+xml
> @context=^publish_hints
> and reload pjsip with 'pjsip reload'
> Asterisk will now report on the cli on notification events:
> [May  6 00:09:35] ERROR[582959]: res_pjsip_outbound_publish.c:563 sip_outbound_publish_client_get_publisher: FRACK!, Failed assertion bad magic number 0x0 for object 0x55e8e99c5620 (0)
> [May  6 00:09:35] ERROR[582959]:   Got 17 backtrace records
> # 0: [0x55e8e32ea334] asterisk utils.c:2454 __ast_assert_failed()
> # 1: [0x55e8e31494b3] asterisk astobj2.c:220 log_bad_ao2()
> # 2: [0x55e8e314be86] asterisk astobj2_container.c:244 internal_ao2_traverse()
> # 3: [0x55e8e314c49e] asterisk astobj2_container.c:414 __ao2_callback()
> # 4: [0x55e8e314c55e] asterisk astobj2_container.c:437 __ao2_find()
> # 5: [0x7fc53965bcca] res_pjsip_outbound_publish.so res_pjsip_outbound_publish.c:563 sip_outbound_publish_client_get_publisher()
> # 6: [0x7fc53965bd7f] res_pjsip_outbound_publish.so res_pjsip_outbound_publish.c:580 ast_sip_publish_client_get_user_from_uri()
> # 7: [0x7fc539535435] res_pjsip_exten_state.so res_pjsip_exten_state.c:655 exten_state_publisher_cb()
> # 8: [0x55e8e32d2dab] asterisk taskprocessor.c:1239 ast_taskprocessor_execute()
> # 9: [0x55e8e32dd2f6] asterisk threadpool.c:1354 execute_tasks()
> #10: [0x55e8e32d2dab] asterisk taskprocessor.c:1239 ast_taskprocessor_execute()
> #11: [0x55e8e32dac11] asterisk threadpool.c:367 threadpool_execute()
> #12: [0x55e8e32dca9b] asterisk threadpool.c:1137 worker_active()
> #13: [0x55e8e32dc7fe] asterisk threadpool.c:1057 worker_start()
> #14: [0x55e8e32e6ec7] asterisk utils.c:1299 dummy_start()
> #15: [0x7fc587a64609] libpthread.so.0 pthread_create.c:478 start_thread()
> #16: [0x7fc58769f293] libc.so.6 :0 clone()
> Expected behaviour:
> No FRACK! errors



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



More information about the asterisk-bugs mailing list