[asterisk-bugs] [JIRA] (ASTERISK-24210) T.38 UDPTL Frames are sent to wrong destination IP

Daniel Steglich (JIRA) noreply at issues.asterisk.org
Wed Aug 13 08:49:30 CDT 2014


    [ https://issues.asterisk.org/jira/browse/ASTERISK-24210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221632#comment-221632 ] 

Daniel Steglich commented on ASTERISK-24210:
--------------------------------------------

Hi Joshua, you are right - the "connection Information" is used twice within the SDP Part of the "200 OK" and the second one is filled with asterisk IP.
When I was debuggin, I have only noticed the first "connection Information" field. On first view It seems like client causes the issue.

But one thing is strange:
The re-Invite (sent from asterisk to SIP Peer) already contains connection information twice. The SIP client simply clones the SDP Part of the SIP Message and replaces the "Connection Information Field" by his own IP address Information. During this operation he replaces only the first occurrence of connection Information. 

So the question is, why is the connection information sent twice within the re-Invite (from asterisk)?

BTW: We previously used asterisk 1.8 and never had this issue with our SIP client. Also Network traces from this older asterisk instance does not show this connection information twice.

> 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