[asterisk-bugs] [JIRA] (ASTERISK-26035) PJSIP driver, TLS client in ringgroup crashes asterisk with incoming trunk call

[Asterisk Team (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-26035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asterisk Team updated ASTERISK-26035:
-------------------------------------

    Assignee: Asterisk Team  (was: J. Lance Cotton)
      Status: Triage  (was: Waiting for Feedback)

> PJSIP driver, TLS client in ringgroup crashes asterisk with incoming trunk call
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-26035
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26035
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.8.2, 13.9.0, 13.9.1
>         Environment: FreePBX Distro 10.13.66-11. Mix of hardware clients (Panasonic KX-TG550, Snom M9) and softphone clients (MicroSIP 3.12.1, win32)
>            Reporter: J. Lance Cotton
>            Assignee: Asterisk Team
>         Attachments: backtrace_full.txt, backtrace.txt, bt_threadtrace.txt, PJSIP_Log_withTLS_Crash.txt, TLS_Crash.txt, UDP_NoCrash.txt
>
>
> Have 6 extensions in a ringgroup. One is a MicroSIP 13.12.1 softphone. The other 5 are hardware IP (SIP) devices that do not support TLS, so they connect by UDP all the time.
> When the softphone is connected by TLS transport and a call comes in from our SIP trunk provider the call is directed to the ringgroup. Asterisk crashes.
> When the softphone is set to connect to the UDP transport, no crash.
> When the softphone is using the TLS transport and a call comes in from the trunk provider, but doesn't go through a ringgroup, no crash.
> When the ringgroup is dialed directly from another extension in the office, no crash (TLS).
> PJSIP Log of crash, File: TLS_Crash.txt
> Same setup, but softphone using UDP transport (only change), File: UDP_NoCrash.txt



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