[Live-devel] RTCP RR reports do not reach to the server using UDP

[Muhammad Mohsin Abbasi]

Hi Ross,

We are using Amazon Server having public and private ip addresses for their server instances. There is no NAT on Amazon or on our Client side. our Client also has the public IP address.

By default with live555, when RR reports are sent from testRTSPClient using UDP, the destination of the RR report is the private IP address of the amazon server instead of public IP. client gets this private IP address from the SDP sent by the live555 server in response to DESCRIBE command. We want to change it to public IP address because our server has the public IP address as well.  Just for testing,  we changed the live555 library function as below and RR reports work fine.

void MediaSubsession::setDestinations(netAddressBits defaultDestAddress) {
netAddressBits destAddress = connectionEndpointAddress();  //BY DEFAULT THIS FUNCTION RETURNS PRIVATE IP OF THE AMAZON SERVER INSTANCE
if (destAddress == 0) destAddress = defaultDestAddress;
struct in_addr destAddr; destAddr.s_addr = destAddress;
//-----------------------------------------
destAddr.S_un.S_un_b.s_b1=AA;     //  //AA.BB.CC.DD IS THE PUBLIC IP OF THE SERVER WE CHANGED HERE WITH THIS IP
destAddr.S_un.S_un_b.s_b2=BB;
destAddr.S_un.S_un_b.s_b3=CC;
destAddr.S_un.S_un_b.s_b4=DD;
 //-----------------------------------------------

What we want is that when RR packets are sent, the destination address should be the public IP of the server not its private, we don't want to make change in the library method as the way we did in above code. what should we do in this case? 

Best Regards

Mohsin

________________________________________
From: live-devel <live-devel-bounces at ns.live555.com> on behalf of Ross Finlayson <finlayson at live555.com>
Sent: Thursday, November 5, 2015 3:18 AM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] RTCP RR reports do not reach to the server    using   UDP

It wasn’t totally clear from your message, but you seem to be implying that there is a NAT between your server and your client - with your server on the public Internet, and your client in a private IP address space (i.e., behind a NAT).

In general, you *cannot* expect RTP/RTCP/RTSP streaming to work in such an environment (because RTSP ***was not designed to work across NATs***).

For RTSP to work reliably, both the server and client(s) should all be on the public Internet (or all on the same private Internet).  Sorry.

Ross Finlayson
Live Networks, Inc.
http://www.live555.com/


_______________________________________________
live-devel mailing list
live-devel at lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel