[asterisk-bugs] [Asterisk 0013405]: [patch] T38 gateway

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=13405 
====================================================================== 
Reported By:                dafe_von_cetin
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13405
Category:                   Applications/app_fax
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     confirmed
Asterisk Version:           SVN 
JIRA:                       SWP-115 
Regression:                 No 
Reviewboard Link:           https://reviewboard.asterisk.org/r/459/ 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 140548 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-30 16:44 CDT
Last Modified:              2010-03-21 16:34 CDT
====================================================================== 
Summary:                    [patch] T38 gateway
Description: 
Hi all,

I'm sending you patch containing new application app_faxgateway.c
("FaxGateway") which is able to mediate T30 to T38 and vice versa.
Feature is using spands library (I used spandsp-0.0.4pre18 and
spandsp-0.0.5pre4).

Best regards
Daniel.

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

---------------------------------------------------------------------- 
 (0119632) klaus3000 (reporter) - 2010-03-21 16:34
 https://issues.asterisk.org/view.php?id=13405#c119632 
---------------------------------------------------------------------- 
@steinwej: Yes, Dial(,,b) is better as pre-answer phase is better handled
by Dial as by FaxGAteway.
Fax-ToneDetection always worked in my scenarios. But I do not remember now
if it was CED or CNG which actually triggered the reINVITE. If enable
"full" logging (logger.conf) and set a high debug level, you should see
status of tone detection in the logs.

Why is it better to send T.38 request to the "active" channel instead of
"inactive"? Actually I do not see a difference. Just because a tone is
detected on a channel does not mean that this channel can handle T.38. Maye
we could also send on both channels?

Probably the fastet approach would be to put technology information
directly into the gateway application. If the application knows that all
channels except SIP can not handle T.38, the gateway application could be
started faster. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-21 16:34 klaus3000      Note Added: 0119632                          
======================================================================