|Summary:||ASTERISK-18706: UDPTL fail while using directmedia|
|Reporter:||Jeremy Kister (jkister)||Labels:|
|Date Opened:||2011-10-11 18:05:00||Date Closed:||2013-09-19 11:41:03|
|Versions:||22.214.171.124 11.5.0||Frequency of|
|Environment:||Attachments:||( 0) pbx1.txt|
( 1) pbx1-noreinvite-on-s3.txt
( 2) s3.txt
( 3) s3-noreinvite-on-s3.txt
|Description:||I'm trying to receive a t.38 fax from a Metaswitch 7.3.|
I have the Metaswitch hooked to Asterisk 126.96.36.199 (middleman named s3).
Then I have the target Asterisk 188.8.131.52 with res_fax_digum 1.8.4_1.3.0
(named pbx1) registered to s3.
s3 has directmedia=yes in sip.conf
attempts to receive fax on pbx1 over t.38 always error in res_fax with "fax
|Comments:||By: Jeremy Kister (jkister) 2011-10-11 18:09:54.613-0500|
with kevin's help (see http://lists.digium.com/pipermail/asterisk-users/2011-October/266997.html), setting directmedia=no on s3 fixed the issue.
By: Malcolm Davenport (mdavenport) 2011-10-12 08:41:50.563-0500
Further note to anyone triaging this issue that UDPTL should *not* fail, even if directmedia is specified, so this is an unresolved bug.
By: Ian Ruddell (email@example.com) 2012-11-01 20:33:33.196-0500
Hi Am testing in 184.108.40.206-rc1 and have the same issue. When using Direct media and a reinvite happens with T.38 between two peers the PORT between the received and sent re invites are different. However the IP address is the same. I can provide debug messages if required.
By: Matt Jordan (mjordan) 2012-11-01 20:35:53.083-0500
This issue still Open and has not yet received a patch from a developer; as such, its expected that this problem still exists in the latest release candidate.
Please be patient; the issue will be addressed given time and sufficient resources.
By: Jonathan Rose (jrose) 2013-09-18 15:19:57.427-0500
As we mentioned on the review discussion through mailing lists, please verify if this patch fixes the problem:
By: Jeremy Kister (jkister) 2013-09-18 19:22:22.548-0500
rb2853 does fix the issue on asterisk 11.5.0!
By: Walter Doekes (wdoekes) 2013-09-19 01:49:24.160-0500
<jkister> Your [r2853] patch does fix the problem.