# Redundand RTSP/RTMP/HTTP live stream pulling

**URL:** https://community.wowza.com/t/redundand-rtsp-rtmp-http-live-stream-pulling/365
**Category:** Wowza Streaming Engine
**Created:** [November 25, 2014, 1:53pm UTC](https://community.wowza.com/t/redundand-rtsp-rtmp-http-live-stream-pulling/365 "2014-11-25T13:53:59Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/system/32/447_2.png) [@system](https://community.wowza.com/u/system)
#### Post date: [November 25, 2014, 1:53pm UTC](https://community.wowza.com/t/redundand-rtsp-rtmp-http-live-stream-pulling/365/1 "2014-11-25T13:53:59Z")

</div>

Hi,

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)

```auto
[Play_out_stream_name]!rtsp://[SOURCE1]/[PATH]|rtsp://[SOURCE2]/[PATH]

```

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:

```auto
RTPSessionDescriptionDataProviderBasicRTSPWorker.doConnect: convert : java.net.URISyntaxException: Illegal character in query at index 93: rtsp://viewer:viewer@172.16.1.20:554/axis-media/media.amp?videocodec=h264&streamprofile=Wowza|rtsp://viewer:viewer@172.16.1.21: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)|

```

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?

---

<div class="post-metadata">

### Author: ![Joshua\_Rubingh](https://avatars.discourse-cdn.com/v4/letter/j/ba8739/32.png) [@Joshua\_Rubingh](https://community.wowza.com/u/Joshua_Rubingh)
#### Post date: [November 27, 2014, 1:59pm UTC](https://community.wowza.com/t/redundand-rtsp-rtmp-http-live-stream-pulling/365/2 "2014-11-27T13:59:38Z")

</div>

Is there anybody from Wowza than can clarify the above?

---

<div class="post-metadata">

### Author: ![Joshua\_Rubingh](https://avatars.discourse-cdn.com/v4/letter/j/ba8739/32.png) [@Joshua\_Rubingh](https://community.wowza.com/u/Joshua_Rubingh)
#### Post date: [December 2, 2014, 10:42am UTC](https://community.wowza.com/t/redundand-rtsp-rtmp-http-live-stream-pulling/365/3 "2014-12-02T10:42:21Z")

</div>

My bad. For RTSP and HTTP it is not possible.

Works only for RTMP.

Would be a nice feature to have for RTSP and HTTP (IceCast) sources.