Re: [Mplayerplug-in-devel] Plugin parameters
Brought to you by:
kdekorte
From: Kevin D. <kde...@gm...> - 2008-09-02 21:34:31
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike Mueller wrote: | On Tue, Sep 02, 2008 at 02:46:21PM -0600, Kevin DeKorte wrote: |> Mike, |> |> Generally the config options cannot be specified in the EMBED command. |> Also if you need to force the rtsp-use-tcp option generally something is |> broken on the server/firewall since normally rtsp streams fine over UDP. |> |> Kevin | | Kevin, thanks for the quick response. | | This might not be the right place to ask, but yes, I'm having problems | with RTSP over UDP. It works fine on the local network, but from | outside, it doesn't work (just a gray rectangle). The firewall has the | RTSP ports (both TCP and UDP) forwarded. | | When I run mplayer from the command line, it looks like it tries to open | a couple additional random ports: | | Initiated "video/MP4V-ES" RTP subsession on port 37110 | Initiated "audio/PCMU" RTP subsession on port 37112 | | That's where it stops. The port numbers are different every time. Do I | need to forward these ports too? This will be problematic since I have | several video servers behind the firewall, not just one. | | Note that in most cases, the client will also be behind a firewall, so | if the video server is attempting to connect back to the client, that | will be impossible. | | Thanks again, | Mike | Mike, Yeah, I really don't know the solution to your problem but it appears that your firewall surrounding your video servers might be the cause. The way a normal TCP/IP session works is that the client connects to a standard port and then that connection is handed off to a thread/process that may or may not run on a separate port for that session. So your firewall will need to handle that hand off the new connection. So make sure the firewall is working with UDP and TCP data packets. I also believe that you can either compile out or disable UDP transmission on most video servers so you might take a look at that. Kevin - -- Get my public GnuPG key from http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7D0BD5D1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFIvbFh6w2kMH0L1dERAo4KAJsGn+AZHNjSr1rBP2kdfYz8ydM7nACeM2rH gbCRyIo+fSxFVu4OShx9co8= =m4fO -----END PGP SIGNATURE----- |