[asterisk-bugs] [Asterisk 0017091]: T.38 faxmaxdatagram overflows with UDPFEC, works with "t38pt_udptl=yes, redundancy" (udptl.c)
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Mar 24 09:51:28 CDT 2010
The following issue requires your FEEDBACK.
======================================================================
https://issues.asterisk.org/view.php?id=17091
======================================================================
Reported By: rlr2maverick
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17091
Category: Channels/chan_sip/T.38
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
Asterisk Version: 1.6.1.18
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-03-24 09:36 CDT
Last Modified: 2010-03-24 09:51 CDT
======================================================================
Summary: T.38 faxmaxdatagram overflows with UDPFEC, works
with "t38pt_udptl=yes,redundancy" (udptl.c)
Description:
Our 1.6.1.18 works with any sort of fax call using standard ReceiveFax and
SendFax provided by appfax, only after changing UDPFEC default parameter
which causes a buffer overflow with faxmaxdatagram (properly negotiated as
per 180 among ATA and Cisco 3825).
The environment consist of:
FAX <-> ATA <-> ASTERISK <-> ROUTER 3825 <-> PSTN (audio fax)
^^^ ^^^
faxmaxdatagram=180 faxmaxdatagram=180
SIP debug shows faxmaxdatagram properly negotiated but following ECM
packets are discarded by 3825 causing either fax call to abort
prematurely, packets encoded with UDPFEC overflow the maximum admitted
size.
changing udpfec (default) with "t38pt_udptl=yes,redundancy" we got near
100% fax send/receive success.
======================================================================
----------------------------------------------------------------------
(0119800) lmadsen (administrator) - 2010-03-24 09:51
https://issues.asterisk.org/view.php?id=17091#c119800
----------------------------------------------------------------------
Could you provide some logging that shows what is going on here? Also
someone in support mentioned that this may already be a known problem in
the binary, and that it should be fixed in 1.1.7.
Issue History
Date Modified Username Field Change
======================================================================
2010-03-24 09:51 lmadsen Note Added: 0119800
2010-03-24 09:51 lmadsen Status new => feedback
======================================================================
More information about the asterisk-bugs
mailing list