[asterisk-bugs] [Asterisk 0015453]: There are no faxes!

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15453 
====================================================================== 
Reported By:                eyatsko
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15453
Category:                   Channels/chan_sip/T.38
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.25.1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-07-06 07:11 CDT
Last Modified:              2009-07-16 07:51 CDT
====================================================================== 
Summary:                    There are no faxes!
Description: 
We have Debian Etch with Asterisk 1.4.25.1 installed (via make&&make
install) and several mediagateways Quintum AS/AF/CMS which are set up for
faxes in the same way.
We have trouble with fax movement!
Hereinafter:
   80.251.131.142 - Asterisk
   10.0.101.13 - Quintum AS
   10.0.101.250 - Quintum AF
   10.0.101.31 - Quintum CMS
There are "t38pt_udptl=yes" in [general] and in [peer]. And I've tried to
insert "t38pt_usertpsource=yes/no" with no effect.

Output:
~# tshark -ni bond0 -R t38
35.476270 10.0.101.250 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00036
t30ind: v21-preamble
35.478562 10.0.101.13 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00000
t30ind: no-signal
35.546414 10.0.101.250 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00036
t30ind: v21-preamble
35.548914 10.0.101.13 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00000
t30ind: no-signal
35.616491 10.0.101.250 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00036
t30ind: v21-preamble
35.618576 10.0.101.13 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00000
t30ind: no-signal
35.686391 10.0.101.250 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00036
t30ind: v21-preamble
35.688580 10.0.101.13 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00000
t30ind: no-signal
35.756311 10.0.101.250 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00036
t30ind: v21-preamble
35.758603 10.0.101.13 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00000
t30ind: no-signal
35.826283 10.0.101.250 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00036
t30ind: v21-preamble
35.828587 10.0.101.13 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00000
t30ind: no-signal
35.896289 10.0.101.250 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00036
t30ind: v21-preamble
35.898613 10.0.101.13 -> 80.251.131.142 T.38 UDP: UDPTLPacket Seq=00000
t30ind: no-signal


====================================================================== 

---------------------------------------------------------------------- 
 (0107842) lmadsen (administrator) - 2009-07-16 07:51
 https://issues.asterisk.org/view.php?id=15453#c107842 
---------------------------------------------------------------------- 
There has been a bunch of work on T.38 recently, so please keep an eye out
for new releases that may contain some of this work. The 1.4.26 that will
be released next week won't have it, but any 1.4.27 release candidates
should.

Any new 1.6.x release candidates should also contain any of the T.38
changes that will be going in shortly. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-16 07:51 lmadsen        Note Added: 0107842                          
======================================================================