Wowza as client not working on redirect

Wowza Streaming Engine
1

Hi

I am currently testing Wowza server. We are trying to check functionality with Xtream Codes on mpegts and hls. Our situation is as follows:

A) Stream is on Xtream Codes main server, connects and plays without an issue

B) Changing the stream to a loadbalancer on the Xtream Codes, works on VLC, Flussonic, and other players. Wowza does not connect and stream remains in “Waiting for Stream” Status. We believe its because wowza as a client is not accepting the redirect being issued by the server. How can we solve this issue?

2

I need to ask two questions @Asad Manzur

  1. Can you please provide clarification on how you have Wowza set up as a Client? Is it with MediaCaster applehls?

  2. How is the load balancer sending out the redirect? Is it via a 302 http code?

3

@Asad Manzur We are experiencing a very simular issue. Our WSE implementation worked fine with Wowza Player, but we need a player that does not “call home”, so we switched to HTML5 / HLS.js on support’s recommendation. Now, we are getting a 302 http code from our F5 / LTM because it appears WSE is not putting the CORS header info in place, even though it configured to do so.

4

Thanks for this information @Rich Sokol. I am following your most recent support ticket on this.

5

While we do support 302 redirects, we do not support agent headers in the http request.

7

This 100% ended up being on our end, a learning curve coming from Flash and OSMF. Turns out adding a custom configuration object when creating the HLS player mitigated our issue. Specifically, the following: xhrSetup: function (xhr, url) { xhr.withCredentials = true;} in addition to others.

8

Thanks for the reply Rich. Our issue is when wowza is acting as a client to restream from a source. Can we set up the custom configuariton required when Wowza is acting as HLS/MPEGTS client?

I would appreciate if you could send the details of what all needs to be set up to achieve this.

Thanks