[Live-devel] Live555 Proxyserver not working on Android (Nexus5)

Indu Girish indu.girish at gadgeon.com
Tue Dec 19 04:20:04 PST 2017


Hi Ross,

We are trying to integrate live555 into an android app which is intended to
run on consumer mobile handsets. Adding a route into those devices is
impossible from an app perspective.

We tried to implement an alternate logic ( for ourIPAddress()
GroupsockHelper.cpp) to obtain the IP address and tried. The proxystream
url changed to the obtained ip address instead of 0.0.0.0. But couldn't
connect to the stream.

We also tried to change the
SendingInterfaceAddr = INADDR_ANY;
ReceivingInterfaceAddr = INADDR_ANY;

part from INADDR_ANY to the IP address of the interface (including all the
permutations). Still it didn't work.

Even when the ip in the supplied url is 0.0.0.0 we can tell that the server
is listening for a connection. When we tried to telnet into IP of the
device and port 8554, connection is established and we did get "400 bad
request" reply from the server.

Do we have any other means to solve this issue by modifying the source code?



Thanks & Regards,
Indu

On Tue, Dec 19, 2017 at 3:56 AM, Ross Finlayson <finlayson at live555.com>
wrote:

>
>
> > On Dec 14, 2017, at 12:10 AM, Indu Girish <indu.girish at gadgeon.com>
> wrote:
> >
> > HI,
> >
> > We are trying to proxy an RTSP stream from an IP camera using Live555
> Proxyserver. In certain mobile devices like Nexus5, it fails to provide the
> stream.
> >
> > Nexus 5, Android 6.0.1, Kernel 3.4.0
> >
> > In the devices in which it works the server listens on its own IP.
> Something like rtsp://192.168.10.1:8554/proxyStream.
> > But in nexus 5 the URL is rtsp://0.0.0.0:8554/proxyStream.
>
> By default, the server uses the network interface that’s used for IP
> multicast routing - i.e., the one that has a route for 224.0.0.0/4.  (The
> reason for this is that it uses IP multicast to detect its own IP address.)
>
> So, the easiest way to choose a particular network interface is to
> reconfigure your host so that it uses that network interface for IP
> multicast routing.  You should be able to do this by running (as root):
>         route add 224.0.0.0/4 ip-address-for-that-nic
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20171219/466019f9/attachment.html>


More information about the live-devel mailing list