[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-14 07:21 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.

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

---------------------------------------------------------------------- 
 (0119334) klaus3000 (reporter) - 2010-03-14 07:21
 https://issues.asterisk.org/view.php?id=13405#c119334 
---------------------------------------------------------------------- 
There are several possibilities to verify if T.38 is used, for example:
A) activate channel debugging "core set debug channel all". Then you
should see CONTROL frames (for T.38 negotiation) and the MODEM frames in
the log file (activate "full" logging of debug messages in logger.conf)

B) watch the SIP signalling: "sip set debug on". Then you will see the
reINVITE to T.38. If the reINVITE gets answered with 200 OK then you should
have T.38 transmission.

C) watch RTP and UDPTL packets: "updtl set debug on", "rtp set debug on".
After T.38 reINVITE the RTP logging changes to UDPTL logging 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-14 07:21 klaus3000      Note Added: 0119334                          
======================================================================