First, please upgrade to the latest version of the “LIVE555 Streaming Media”
source code (the only version that we support); see
http://live555.com/liveMedia/faq.html#latest-version
Your problem, however, is with your RTSP servers - i.e., your cameras.
Specifically: In their RTSP “DESCRIBE” responses, your servers each specify
that they will be streaming only to port number 5004. I.e.,
> m=video 5004 RTP/AVP 26
Because *both* of your cameras do this, they *both* send RTP packets to port
number 5004 (and both send RTCP packets to port number 5005). Therefore, your
RTSP client (“testRTSPClient”) cannot distinguish between the two streams.
Specifying a non-zero port number in a SDP “m=” line is usually done only when
the stream is multicast. For unicast streams like this, it is more common for
the server to put “0” as the port number in the “m=“ line. This tells the
client that it should choose its own, ephemeral, port number for each stream,
which it will put in its subsequent RTSP “SETUP” command - to tell the server
which port to stream to.
So, please tell your camera manufacturer (Point Grey) about this bug. If they
don’t fix this bug - or if you can’t reconfigure your cameras to use different
static client port numbers - then you won’t be able to use more than one of
these cameras when streaming to the same client host.
Finally, you should note that streaming JPEG is generally a bad idea; see
http://live555.com/liveMedia/faq.html#jpeg-streaming
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
_______________________________________________
live-devel mailing list
[email protected]
http://lists.live555.com/mailman/listinfo/live-devel
