in Wowza version 3.6 we use the stream name alias on the origin Wowza server with the following content in the alias.stream.txt file (streaming)
We have a custom delimiter '!' in the config. So this line will instruct Wowza 3.6 to get the stream from source1 when a viewer requests the stream. If source1 goes down, Wowza can try source2. This is all done on the Wowza server that is configured as origin. This works like a charm in Wowza 3.6
With Wowza 4, this is broken! I say that it is broken, because this is a hugh issue, where we cannot guarantee redundancy anymore for remote pulling. Why has this been removed from Wowza 4? Also working with a .stream file with multiple sources in the 'uri' parameter, does not work. Wowza reports the following error:
And yesh, the url is not a valid url because of the '|' sign. But this has always been working. And this does work on a server that is an edge/repeater server. So in the edge/repeater server you can specify a stream name with multiple sources. Why is this not possible with an origin server anymore?
RTPSessionDescriptionDataProviderBasicRTSPWorker.doConnect: convert : java.net.URISyntaxException: Illegal character in query at index 93: rtsp://viewer:email@example.com:554/axis-media/media.amp?videocodec=h264&streamprofile=Wowza|rtsp://viewer:firstname.lastname@example.org:554/axis-media/media.amp?videocodec=h264&streamprofile=Wowza|at java.net.URI$Parser.fail(URI.java:2848)|at java.net.URI$Parser.checkChars(URI.java:3021)|at java.net.URI$Parser.parseHierarchical(URI.java:3111)|at java.net.URI$Parser.parse(URI.java:3053)|at java.net.URI.<init>(URI.java:588)|