Summary:	ASTERISK-27962: res_pjsip_t38: Reinvite after 491 includes audio stream and T.38, not just T.38
Reporter:	Michael Maier (micha)	Labels:	fax pjsip
Date Opened:	2018-07-13 13:10:51	Date Closed:
Priority:	Minor	Regression?
Status:	Open/New	Components:	Resources/res_pjsip_t38
Versions:	13.22.0	Frequency of Occurrence	Constant
Related Issues:	is related to ASTERISK-28865 FAX T.38 re-Invite failed on '491 Another INVITE transaction in progress' is related to ASTERISK-28539 Failed t.38 negotiation when B leg sends t.38 re-invite
Environment:	CentOS 6 / 64 Bit	Attachments:	( 0) Screenshot_20180713_155546.png ( 1) Screenshot_20180714_163521.png ( 2) t38negerror
Description:	A lot of the following log entries can be found in the log: NOTICE[20870][C-00000024] udptl.c: UDPTL (PJSIP/telekomPJSIP-226-00000050): Transmission error to 217.0.5.183:0: Invalid argument during receiving a fax. The receiving of the fax fails. This situation happens, if the following takes place (see attached screenshot): - inbound fax - t.38 udptl is activated on the incoming trunk - the fax device sends a t.38 reinivte - but the peer doesn't answer with 488 not accepted - instead the peer sends an INVITE "g711" (see screenshot) - fax reception is broken from that point.
Comments:	By: Asterisk Team (asteriskteam) 2018-07-13 13:10:52.220-0500 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: Michael Maier (micha) 2018-07-13 13:14:03.622-0500 See initial bug entry By: Kevin Harwell (kharwell) 2018-07-13 16:20:45.713-0500 We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. Also please include the protocol specific debug ('pjsip set logger on') captured at the time of the issue. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Michael Maier (micha) 2018-07-14 09:40:28.251-0500 This is the debug file which belongs to the second screen shot.