[asterisk-bugs] [JIRA] (ASTERISK-27037) Segfault in pjsip
Joshua Colp (JIRA)
noreply at issues.asterisk.org
Mon Jun 12 09:07:57 CDT 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-27037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Colp updated ASTERISK-27037:
-----------------------------------
Assignee: Martin Tomec
Status: Waiting for Feedback (was: Triage)
I don't think this is a problem really in PJSIP itself, but may be in our websocket transport implementation.
What is the Asterisk console output when this happens? Is the Websocket still active? (I don't see it in the backtrace but some threads don't have data - do you have DONT_OPTIMIZE set?)
> Segfault in pjsip
> -----------------
>
> Key: ASTERISK-27037
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-27037
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: pjproject/pjsip
> Affects Versions: 13.15.1
> Environment: CentOS 7.3
> Reporter: Martin Tomec
> Assignee: Martin Tomec
> Attachments: backtrace.txt, endpoint.txt, pjproject_buildopts.txt
>
>
> We were experiencing frequent asterisk crash in production enviroment. Maybe it was caused by some mallformed webrtc registration. For now we can´t reproduce the issue, so I send only backtrace from coredump. In logs I failed to find any common line for all crashes, only this is suspicious:
> {noformat}
> [Jun 7 12:10:55] ERROR[21634] res_pjsip.c: Error 171060 'Unsupported transport (PJSIP_EUNSUPTRANSPORT)' sending OPTIONS request to endpoint webrtc_kaplan
> {noformat}
> Please let mi know if I can get more from coredump or log
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list