[asterisk-bugs] [Asterisk 0017573]: T.38 UDPTL Port Negotiation Fails
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Jul 1 12:15:22 CDT 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=17573
======================================================================
Reported By: scratchspace1
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17573
Category: Channels/chan_sip/T.38
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
Asterisk Version: 1.4.33.1
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-06-30 20:58 CDT
Last Modified: 2010-07-01 12:15 CDT
======================================================================
Summary: T.38 UDPTL Port Negotiation Fails
Description:
T.38 calls into SIP provider (Broadvox Sonus switch) result in UDPTL data
being sent to Asterisk instead of T.38 peer (Linksys 2102 ATA firmware
5.2.10). Asterisk server and ATA have public non-NAT IP addresses with no
firewall.
The peers appear to negotiate T.38, with messages from Asterisk indicating
that it knows the correct IP addresses and UDPTL ports of both peers, but
asterisk returns a reinvite to the SIP provider with it's own IP address
rather than the IP address of the ATA.
t38state never gets beyond state 4 (successful T38 would get to state 5).
After several seconds, the ATA terminates the call due to lack of T.38 data
stream.
Same result with Grandstream ATA.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-07-01 12:15 lmadsen Description Updated
======================================================================
More information about the asterisk-bugs
mailing list