Question
Port test
The video content loads very slow and playback is often
choppy.
We recently purchased a large library of videos from a content generation group and they are hosting the site and the video content on their web servers and FMS.
I was able to hack the rtmp string from the html code of the generated page and ran a series of tests.
Using that string I was able to conduct three tests using the port call on the rtmp string.
The first specified port 1935, the second 443 and the last one over port 80
1. rtmp://www.videohost.com:1935/videoname.flv
2. rtmp://www.videohost.com:443/videoname.flv
3. rtmp://www.videohost.com:80/videoname.flv
What I found was every time the streaming video would load on port 80 right away, 443 a couple of seconds later and 1935 about 8 seconds later.
This appears to me that port 1935 is closed and FMS is simply going through its natural progression to 443 and finally 80 only after timing out an attempts to connect.
Without deploying an app to the server (I don't have access to develop as I stated earlier this is a purchased package) can I perform some test to definitively state to our content provider that there is something wrong with their FMS and not our firewall (I've run several tests that have ruled out our firewall)?
Any recommendations would be appreciated.
John
We recently purchased a large library of videos from a content generation group and they are hosting the site and the video content on their web servers and FMS.
I was able to hack the rtmp string from the html code of the generated page and ran a series of tests.
Using that string I was able to conduct three tests using the port call on the rtmp string.
The first specified port 1935, the second 443 and the last one over port 80
1. rtmp://www.videohost.com:1935/videoname.flv
2. rtmp://www.videohost.com:443/videoname.flv
3. rtmp://www.videohost.com:80/videoname.flv
What I found was every time the streaming video would load on port 80 right away, 443 a couple of seconds later and 1935 about 8 seconds later.
This appears to me that port 1935 is closed and FMS is simply going through its natural progression to 443 and finally 80 only after timing out an attempts to connect.
Without deploying an app to the server (I don't have access to develop as I stated earlier this is a purchased package) can I perform some test to definitively state to our content provider that there is something wrong with their FMS and not our firewall (I've run several tests that have ruled out our firewall)?
Any recommendations would be appreciated.
John
AdChoices