[asterisk-bugs] [JIRA] (ASTERISK-20670) Wrong error correction in T38 INVITE when multiple Asterisk servers are involved.
Mike Walker (JIRA)
noreply at issues.asterisk.org
Fri Nov 9 16:50:21 CST 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Walker updated ASTERISK-20670:
-----------------------------------
Description:
When Asterisk is sending a T38 INVITE to an ATA when faxing though more than one Asterisk server, the final Asterisk server in the chain always sends FEC error correction regardless of the initial INVITE sent to Asterisk from the originating ATA, or what the error correction is set to any of the sip.conf files.
ATA > Asterisk > ATA works
ATA > Asterisk > Asterisk > ATA fails
The initial INVITE from the originating ATA has T38FaxUdpEC:t38UDPRedundancy set, the INVITE from first Asterisk server to second Asterisk server contains T38FaxUdpEC:t38UDPRedundancy, but the INVITE from second Asterisk server to terminating ATA has T38FaxUdpEC:t38UDPFEC instead of T38FaxUdpEC:t38UDPRedundancy. This happens regardless of directmedia setting, and even when t38pt_udptl=yes,redundancy,maxdatagram=400 is set in all sip.conf files.
No matter what we try, we can never get the final T38 INVITE to T38FaxUdpEC:t38UDPRedundancy when attempting to fax through more then one Asterisk server.
We are using two Grandstream HT502 ATA's with the latest firmware and have tried several versions of Asterisk 1.8 and 10 to no avail.
was:
When Asterisk is sending a T38 INVITE to an ATA when faxing though more than one Asterisk server, the final Asterisk server in the chain always sends FEC error correction regardless of the initial INVITE sent to Asterisk from the originating ATA, or what the error correction is set to in sip.conf.
ATA > Asterisk > ATA works
ATA > Asterisk > Asterisk > ATA fails
The initial INVITE from the originating ATA has T38FaxUdpEC:t38UDPRedundancy set, the INVITE from first Asterisk server to second Asterisk server contains T38FaxUdpEC:t38UDPRedundancy, but the INVITE from second Asterisk server to terminating ATA has T38FaxUdpEC:t38UDPFEC instead of T38FaxUdpEC:t38UDPRedundancy. This happens regardless of directmedia setting, and even when t38pt_udptl=yes,redundancy,maxdatagram=400 is set in all sip.conf files.
No matter what we try, we can never get the final T38 INVITE to T38FaxUdpEC:t38UDPRedundancy when attempting to fax through more then one Asterisk server.
We are using two Grandstream HT502 ATA's with the latest firmware and have tried several versions of Asterisk 1.8 and 10 to no avail.
> Wrong error correction in T38 INVITE when multiple Asterisk servers are involved.
> ---------------------------------------------------------------------------------
>
> Key: ASTERISK-20670
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-20670
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_sip/T.38, Core/UDPTL
> Affects Versions: 1.8.18.0, 10.8.0, 10.9.0, 10.10.0
> Environment: Debian 6 x86_64 8-Way 16GB RAM.
> Reporter: Mike Walker
>
> When Asterisk is sending a T38 INVITE to an ATA when faxing though more than one Asterisk server, the final Asterisk server in the chain always sends FEC error correction regardless of the initial INVITE sent to Asterisk from the originating ATA, or what the error correction is set to any of the sip.conf files.
> ATA > Asterisk > ATA works
> ATA > Asterisk > Asterisk > ATA fails
> The initial INVITE from the originating ATA has T38FaxUdpEC:t38UDPRedundancy set, the INVITE from first Asterisk server to second Asterisk server contains T38FaxUdpEC:t38UDPRedundancy, but the INVITE from second Asterisk server to terminating ATA has T38FaxUdpEC:t38UDPFEC instead of T38FaxUdpEC:t38UDPRedundancy. This happens regardless of directmedia setting, and even when t38pt_udptl=yes,redundancy,maxdatagram=400 is set in all sip.conf files.
> No matter what we try, we can never get the final T38 INVITE to T38FaxUdpEC:t38UDPRedundancy when attempting to fax through more then one Asterisk server.
> We are using two Grandstream HT502 ATA's with the latest firmware and have tried several versions of Asterisk 1.8 and 10 to no avail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list