[asterisk-bugs] [JIRA] (ASTERISK-24210) T.38 UDPTL Frames are sent to wrong destination IP
Joshua Colp (JIRA)
noreply at issues.asterisk.org
Wed Aug 13 08:23:28 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-24210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joshua Colp closed ASTERISK-24210.
----------------------------------
Resolution: Not A Bug
This does not appear to be a bug with Asterisk.
Asterisk correctly sends a re-invite to T.38 to the remote endpoint. It informs the endpoint that it would like to receive UDPTL traffic on IP address 192.168.115.27 port 4473.
The remote endpoint accepts the re-invite and tells Asterisk it would like to receive UDPTL traffic on IP address 192.168.115.27 port 10002. This is incorrect as that is the IP address of Asterisk. It should instead be saying it wants UDPTL traffic on IP address 192.168.125.102. It does not do this.
Asterisk respectively sends to where it is told, which is the incorrect IP address. Until any traffic is received from the device (since comedia is on) this is the only address that Asterisk can send to.
> T.38 UDPTL Frames are sent to wrong destination IP
> --------------------------------------------------
>
> Key: ASTERISK-24210
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24210
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_fax
> Affects Versions: 11.11.0
> Environment: Linux vargas 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux
> compiled asterisk from here:
> http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-11-current.tar.gz
> Reporter: Daniel Steglich
> Assignee: Matt Jordan
> Attachments: asterisk-cli-debug.txt, asterisk-fax-env.txt, extensions.conf, sip.conf
>
>
> I configured a Fax2Mail extension (details see extensions.conf)
> Now I delete the following lines from sip.conf (see attached)
> nat=comedia
> t38pt_usertpsource=yes
> Then send a Fax from my peer 550000 to 429 (with T.38 enabled).
> Asterisk is sending re-invite and switching to T.38 which works fine.
> But the "connection information" from the "200 OK with SDP" from the client will be ignored.
> This means, when I start network trace on ethernet Interface connected to my peer, I do not see any udptl frames. When I start network trace on "lo" Interface of debian Server, I can see the udptl Frames (destination IP = IP where asterisk is bound to i.e. IP adress of eth1) which are rejected with icmp port unreachable.
> when adding the lines from above:
> nat=comedia
> t38pt_usertpsource=yes
> udptl is sent correctly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list