[Live-devel] [PATCH] Transport: Use port instead of client_port for multicast
Julian Scheel
julian at jusst.de
Thu Jun 18 07:56:14 PDT 2015
According to RFC2326 p59 the ports to be used for multicast sessions shall be
specified through a parameter named port instead of client_port, which has to
be used for unicast streams. Some SAT>IP servers deny SETUP requests for
multicast streams when client_port is specified.
Signed-off-by: Julian Scheel <julian at jusst.de>
---
liveMedia/RTSPClient.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/liveMedia/RTSPClient.cpp b/liveMedia/RTSPClient.cpp
index e49afbe..3bdab2f 100644
--- a/liveMedia/RTSPClient.cpp
+++ b/liveMedia/RTSPClient.cpp
@@ -687,7 +687,7 @@ Boolean RTSPClient::setRequestFields(RequestRecord* request,
Boolean requestMulticastStreaming
= IsMulticastAddress(connectionAddress) || (connectionAddress == 0 && forceMulticastOnUnspecified);
transportTypeStr = requestMulticastStreaming ? ";multicast" : ";unicast";
- portTypeStr = ";client_port";
+ portTypeStr = requestMulticastStreaming ? ";port" : ";client_port";
rtpNumber = subsession.clientPortNum();
if (rtpNumber == 0) {
envir().setResultMsg("Client port number unknown\n");
--
2.4.3
More information about the live-devel
mailing list