We're using adaptive bitrate streaming with JWPlayer. We have it setup to use HDS first, then fallback to HLS, then fallback to progressive download. Everything is working great, but I noticed that even though our ULR for HDS streaming is like this:
The actual request for the media file is using rtmp, like this and is going over port 1935:
I want all the traffic going over port 80, so I went in to vhost.xml and removed port 1935 from the list and left only port 80. Now, videos take like 20 seconds to start whereas before they would start in under 2 seconds. Once they're playing everything works great, but that start time is unacceptable. I don't see anything weird in the logs.
Why is it doing this? Can I force HDS to go over port 80 and get the same performance as port 1935? (not sure why the port would matter).
Little more info:
I just looked at the resulting smil file that is served back to the player from wowza and here's what it looks like (I replaced the actual URL with dummy data):
<video src="mp4:2013/1358-lawrence_solo/1358_lawrence_1024.LG.mp4" system-bitrate="1956000"/>
<video src="mp4:2013/1358-lawrence_solo/1358_lawrence_1280.HD.mp4" system-bitrate="2285000"/>
<video src="mp4:2013/1358-lawrence_solo/1358_lawrence_320.SM.mp4" system-bitrate="751000"/>
<video src="mp4:2013/1358-lawrence_solo/1358_lawrence_640.MD.mp4" system-bitrate="1451000"/>
Could the problem be caused by that meta base entry not specifying a port of 80?