[asterisk-bugs] [Asterisk 0016411]: IP and port is not transferred for t.38

[Asterisk Bug Tracker]

The following issue has been REOPENED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16411 
====================================================================== 
Reported By:                stanusr
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16411
Category:                   Channels/chan_sip/T.38
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.1.11 
JIRA:                       SWP-507 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-12-08 07:32 CST
Last Modified:              2009-12-09 03:56 CST
====================================================================== 
Summary:                    IP and port is not transferred for t.38
Description: 
A SIP audio call is set up between two parties with an Asterisk server in
between. The media  stream goes directly from the caller to the callee.
When Asterisk receives a re-invite on channel leg2 (callee) to change to
T.38 it does not transfer the new media IP address and Port to the invite
for channel leg1 (caller), as expected. It sends the ”old” media IP
address and presumably a PORT generated by Asterisk self in the
udptlstart-udptlend range specified in udptl.conf.


====================================================================== 

---------------------------------------------------------------------- 
 (0114969) stanusr (reporter) - 2009-12-09 03:56
 https://issues.asterisk.org/view.php?id=16411#c114969 
---------------------------------------------------------------------- 
I think that there should be an indication that it is not supported. I
would expect Asterisk to give a warning or send an error back in response
to the INVITE and not just setup a wrong media path. Another acceptable
handling would be that Asterisk automatically change back from direct media
stream as I have not set directrtpsetup=yes. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-09 03:56 stanusr        Note Added: 0114969                          
2009-12-09 03:56 stanusr        Status                   closed => new       
2009-12-09 03:56 stanusr        Resolution               won't fix => reopened
======================================================================