[asterisk-bugs] [JIRA] (ASTERISK-25653) Deadlock - PJ_ENOMEM errors when using PJSIP TLS extensions
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Mon Jan 4 08:35:35 CST 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-25653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-25653:
------------------------------------
Assignee: Phi Tran
Status: Waiting for Feedback (was: Triage)
> Deadlock - PJ_ENOMEM errors when using PJSIP TLS extensions
> -----------------------------------------------------------
>
> Key: ASTERISK-25653
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25653
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: pjproject/pjsip
> Affects Versions: 13.4.0, 13.5.0, 13.6.0
> Environment: CentOS 7 (with Asterisk installed separately), FreePBX 13 (with Asterisk bundled)
> Reporter: Phi Tran
> Assignee: Phi Tran
>
> Deadlock occurs when PJSIP TLS connections to Asterisk fail after 8-30 hours. The logs show "PJ_ENOMEM" errors right around the time this happens. Happens after a variable period of time once Asterisk is started; normally happens when I am moving between Wi-Fi and LTE networks on Bria for iOS v3.5.2. System has 4GB of RAM.
> Tried first on a FreePBX distro. When testing on a completely separate CentOS 7 clean install, this issue also happens. Followed the Asterisk Secure Calling wiki instructions exactly. Connections are stable when Asterisk is first started and calls can occur successfully over SRTP.
> Telnet to TCP 5061 is successful even after deadlock occurs, but no registrations can occur. Bria shows "TLS connection errors" in logs.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list