[asterisk-bugs] [JIRA] (ASTERISK-28473) res_pjsip_t38: Crash on Asterisk 16.4

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-28473:
------------------------------------------

A couple of suggestions. 

1. Sounds like it doesn't happen every time for the same scenario. Maybe compare the pcaps of a good vs bad run to see if anything stands out.

2. Same for the Asterisk logs. Compare a good vs bad run. Unfortunately of course once a crash occurs there is no more logging. Do however check the log file after each crash because depending on the timing (logs are written in a separate thread)more or less log statements might get written out. So maybe one of the times you might see a relevant error/warning in the log.

> res_pjsip_t38: Crash on Asterisk 16.4
> -------------------------------------
>
>                 Key: ASTERISK-28473
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28473
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip_t38
>    Affects Versions: 16.4.0
>            Reporter: Joshua Elson
>            Assignee: Unassigned
>            Severity: Minor
>              Labels: fax
>         Attachments: asterisk-core-20190708-092625-brief.txt, asterisk-core-20190708-092625-full.txt, asterisk-core-20190708-092625-locks.txt, asterisk-core-20190708-092625-thread1.txt, HOMER5-45.32.207.203-4804996066-7_8_2019 9_25_49.pcap
>
>
> This is likely related to ASTERISK-27944... but we're seeing our favorite T38 negotiation crash again. Still looking for a scenario to reproduce cleanly, but this appears to happen in an odd T38 negotiation failure.



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