Summary: | ASTERISK-27633: PJSIP crash phone using UDP on TCP endpoint in ast_sip_failover_request | ||||
Reporter: | snuffy (snuffy) | Labels: | patch pjsip | ||
Date Opened: | 2018-01-28 23:58:13.000-0600 | Date Closed: | 2018-02-21 17:10:35.000-0600 | ||
Priority: | Major | Regression? | Yes | ||
Status: | Closed/Complete | Components: | Resources/res_pjsip | ||
Versions: | GIT | Frequency of Occurrence | Constant | ||
Related Issues: |
| ||||
Environment: | debian 9 --enable-dev-mode DONT_OPTIMIZE BETTER_BACKTRACES | Attachments: | ( 0) 0001-res_pjsip-Add-a-check-for-NULL-tdata-in-ast_sip_fail.patch ( 1) 0002-pjsip_distributor-Fix-tdata-leak-in-authenticate.patch ( 2) 0003-AST-2018-005-res_pjsip_transport_management-Move-to-.patch ( 3) core.asterisk-22142-1517185776-brief.txt ( 4) core.asterisk-22142-1517185776-full.txt ( 5) core.asterisk-22142-1517185776-locks.txt ( 6) core.asterisk-22142-1517185776-thread1.txt ( 7) core.asterisk-22219-1517185779-brief.txt ( 8) core.asterisk-22219-1517185779-full.txt ( 9) core.asterisk-22219-1517185779-locks.txt (10) core.asterisk-22219-1517185779-thread1.txt (11) core.asterisk-26356-1517185133-brief.txt (12) core.asterisk-26356-1517185133-full.txt (13) core.asterisk-26356-1517185133-locks.txt (14) core.asterisk-26356-1517185133-thread1.txt (15) error-out.txt (16) error-out-2.txt | ||
Description: | Have a Cisco 7941 phone.
Tell it to connect via UDP to asterisk server. Asterisk has endpoint as being TCP. Attempt to make call: CRASH. | ||||
Comments: | By: Asterisk Team (asteriskteam) 2018-01-28 23:58:15.116-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: George Joseph (gjoseph) 2018-02-08 08:29:29.193-0600 Hey, Give the attached patches a shot. By: snuffy (snuffy) 2018-02-15 17:57:32.076-0600 Hello George, The patches appears to work fine, the phone no longer causes asterisk to crash. One minor thing though, asterisk seems to 'accept' the endpoint as a Contact via UDP then immediately remove it from the AOR listing, causing the phone to think it successfully registered. -- Added contact 'sip:3202@10.21.16.102:5060;transport=udp' to AOR '3202' with expiration of 3600 seconds == Contact 3202/sip:3202@10.21.16.102:5060;transport=udp has been created == Endpoint 3202 is now Reachable -- Contact 3202/sip:3202@10.21.16.102:5060;transport=udp is now Unreachable. RTT: 0.000 msec == Endpoint 3202 is now Unreachable |