[OpenSER-Devel] [ openser-Bugs-1523753 ] mediaproxy assumes UDP transport

SourceForge.net noreply at sourceforge.net
Fri May 9 19:29:13 CEST 2008


Bugs item #1523753, was opened at 2006-07-17 12:49
Message generated for change (Comment added) made by dan_pascu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1523753&group_id=139143

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: None
Status: Open
Resolution: None
Priority: 2
Private: No
Submitted By: Rémi Denis-Courmont (rdenisc)
Assigned to: Dan (dan_pascu)
Summary: mediaproxy assumes UDP transport

Initial Comment:
The mediaproxy SDP rewriting engine assumes that media
is transport via UDP, regardless of the transport that
is actually specified in the rewritten m= line.

This wreaks havoc when the transport is, typically,
TCP-based, even if it would have worked with mediaproxy!

IMHO, the plugin had better not rewrite the thing if
the transport is neither UDP/something or
RTP/something, so that it can at least work properly
when proxying is not needed.

----------------------------------------------------------------------

>Comment By: Dan (dan_pascu)
Date: 2008-05-09 20:29

Message:
Logged In: YES 
user_id=1296758
Originator: NO

It should be fixed in mediaproxy version 2.0 which will be commited soon
to svn to replace the old mediaproxy. In the new version, if a session has
both streams with supported and unsupported transports, only the streams
with supported transport will be modified, while streams with unsupported
transports will be left alone.

----------------------------------------------------------------------

Comment By: Daniel-Constantin Mierla (miconda)
Date: 2006-08-10 12:34

Message:
Logged In: YES 
user_id=1246013

It is able to relay only UDP media. Therefore the fix should
be that for other type of media transport protocol it should
return error in the script and do not change anything in SDP.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743020&aid=1523753&group_id=139143



More information about the Devel mailing list