> I am working on rtsp client software. Everything works fine until the > transport on the server side was changed to tcp. I got the 461 error in > “after-setup” handler. Ok, this is the easiest part – I just make some > modification to code and handle this case (another try to setup session is > done with the call to sendSetupCommand() and streamUsingTcp set to “true”, > hope this is enough?).
I think you are misunderstanding what is happening here. When you (the client) request RTP-over-TCP streaming (by adding the "-t" option to "openRTSP"), the server decides whether or not it wants to support this. Because it returns a 461 error (meaning "Unsupported Transport"), this suggests that the server *does not* support RTP-over-TCP streaming. You cannot 'fix' this, and you should not modify the existing client code; the existing code is working OK. (Note also that if you modify the supplied code, you cannot expect any support on this mailing list.) Because this server apparently does not support RTP-over-TCP streaming, the "-t" option to "openRTSP" will not work, and you should not use it. (If you don't receive any data when you don't use "-t", then that probably means that you are behind a firewall that is blocking UDP packets. If so, you will need to fix (or remove) your firewall.) Ross Finlayson Live Networks, Inc. http://www.live555.com/
_______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
