Summary: | ASTERISK-26829: res_pjsip: Assertion when applying transport configuration via push | ||
Reporter: | Leif Madsen (lmadsen) | Labels: | |
Date Opened: | 2017-02-28 18:22:59.000-0600 | Date Closed: | |
Priority: | Major | Regression? | No |
Status: | Open/New | Components: | Resources/res_pjsip |
Versions: | 14.3.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | CentOS 7.3, virtualized, x86_64 | Attachments: | ( 0) backtrace.txt ( 1) push.py |
Description: | Working on building out a dynamic configuration controller via ARI and sorcery. Configuration for PJSIP is being pushed from a script living on localhost.
When running the script, I get this message from the console: {code} *CLI> asterisk: ../src/pj/os_core_unix.c:674: pj_thread_this: Assertion `!"Calling pjlib from unknown/external thread. You must " "register external threads with pj_thread_register() " "before calling any pjlib functions."' failed. Aborted (core dumped) {code} Script attached to issue to reproduce. Core dump attached to issue. My script returns the following Python traceback (last line possibly useful): {code} # ./push.py Traceback (most recent call last): File "./push.py", line 46, in <module> transport_resp = resp_push(transport_url, transport_config) File "./push.py", line 24, in resp_push resp = requests.put(url, auth=('asterisk', 'asterisk'), json=config) File "/usr/lib/python2.7/site-packages/requests/api.py", line 121, in put return request('put', url, data=data, **kwargs) File "/usr/lib/python2.7/site-packages/requests/api.py", line 50, in request response = session.request(method=method, url=url, **kwargs) File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 464, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 576, in send r = adapter.send(request, **kwargs) File "/usr/lib/python2.7/site-packages/requests/adapters.py", line 415, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', BadStatusLine("''",)) {code} | ||
Comments: | By: Asterisk Team (asteriskteam) 2017-02-28 18:22:59.765-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]. By: Rusty Newton (rnewton) 2017-02-28 18:28:49.632-0600 bq. Core dump attached to issue. Hi Leif! I don't see a backtrace from Asterisk attached to the issue. By: Rusty Newton (rnewton) 2017-02-28 18:29:06.698-0600 Oops now I do! I spoke too soon! :) By: Leif Madsen (lmadsen) 2017-03-08 08:46:38.385-0600 Just had to wait for me to attach it :) (I don't think you can attach from inside the Create window.) |