> We are using Amazon cloud, Amazon EC2 g2xlarge Server Instance. IP multicast
> is not supported on amazon server.
But you should still be able to add a route for 224.0.0.0/4 for your ‘public’
IP address. Run (as root)
route add 224.0.0.0/4 your-public-ip-address
That would be the be
From: live-devel on behalf of Ross
Finlayson
Sent: Monday, November 9, 2015 3:35 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] RTCP RR reports do not reach to the server using
UDP
OK, you confused me by talking about ‘pri
OK, you confused me by talking about ‘private’ and ‘public’ addresses. That
actually turns out to be irrelevant.
The real issue is that your server is multi-homed (i.e., has more than one IP
address), and is currently choosing (for LIVE555) an address that you don’t
want.
The best way to fix
] RTCP RR reports do not reach to the serverusing
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).
I
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 t
Best Regards
Mohsin
From: live-devel on behalf of Ross
Finlayson
Sent: Tuesday, November 3, 2015 11:28 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] RTCP RR reports do not reach to the server using
UDP
> But we are having problem with UDP
> But we are having problem with UDP (REQUEST_STREAMING_OVER_TCP false) . First
> issue was that SR reports were sent by the server but were not reaching the
> client. the wireshark on the server shows the ICMP destination unreacheable
> (port unreachable) message from the client in response to
