Summary:	ASTERISK-17187: [patch] No timeout on T.38 re-INVITE
Reporter:	Kristijan Vrban (vrban)	Labels:	patch
Date Opened:	2010-12-30 06:25:27.000-0600	Date Closed:
Priority:	Minor	Regression?	No
Status:	Open/New	Components:	Channels/chan_sip/T.38
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) debug.txt ( 1) quickfix_issue_18557.patch ( 2) sip_history.txt ( 3) sipp_scenario.xml
Description:	I noticed, then when chan_sip send out a T.38 re-INVITE and get a "100 Trying", there no timeout set for this INVITE. So when there is no further response to the T.38 -re-INVITE then the "100 Trying", then the sip channel will hang forever. Despite app_fax/res_fax will notice that there is something wrong after a timout with no media, and the channels hang up, but the SIP channels does not send a CANCEL or BYE and never hang up. Attached is the full SIP and dialplan debug to and the sipp scenario reproduce the issue.
Comments:	By: Kristijan Vrban (vrban) 2010-12-30 08:10:19.000-0600 upps, the test was made with 1.6.2.13 with app_fax with asterisk 1.8, res_fax does not hang up and the call never get canceled. So with res_fax it is even worse. By: Kristijan Vrban (vrban) 2011-01-03 08:16:23.000-0600 the sip channels does not get cleared, because function "sip_cancel_destroy" is called in chan_sip where the comment: "Note we will need a BYE when this all settles out but we can't send one while we have "INVITE" outstanding" is. There seems to be a missing logic issue what to do in this specific case. By: Kristijan Vrban (vrban) 2011-01-03 10:42:10.000-0600 with quickfix_issue_18557.patch i made myself a quickfix. dont think this should be the final fix, but it's working for me with app_fax