[asterisk-bugs] [Asterisk 0009356]: T38 outbound

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=9356 
====================================================================== 
Reported By:                mindthegap
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   9356
Category:                   Core/RTP
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.13  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             03-23-2007 09:21 CDT
Last Modified:              02-14-2008 13:15 CST
====================================================================== 
Summary:                    T38 outbound
Description: 
Asterisk 1.4.1 rpm with NAT upgraded to 1.4.2 
ATA (Wellgate 3701B) with T38 connects to Asterisk (ext 401) 
t38pt_udptl= yes both in sip.conf and extension 
canreinvite=yes 

Receiving faxes: OK 
Sending faxes: first page gets sent, then line goes down 
In Asterisk full log a ""RTP re-invite after T38 session not handled yet"
gets logged 

If I set canreinvite=yes to canreinvite=no, nothing works (not even
receiving). 

The firewall statically nats ports 5060/5060 and 4000-4999 and 8000 to
20000 to the asterisk box. 
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0009759 T.38 Fax Outbound (revision of bug 9356)
====================================================================== 

---------------------------------------------------------------------- 
 file - 02-14-08 13:15  
---------------------------------------------------------------------- 
After looking over things, comparing old code/new code, and trying a few
things I am confident this issue no longer exists in the current 1.4 tree. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-14-08 13:15  file           Status                   assigned => resolved
02-14-08 13:15  file           Resolution               open => fixed       
02-14-08 13:15  file           Note Added: 0082259                          
======================================================================