HTTP Live streaming to CDN and not forcing a new session ID

[Rob_Long]

Hi

We’ve seen with Wowza 2 that Wowza forces the player to use a wowzasession id. If this id is missing then wowza as the origin forces a new session id on the player by way of a new (and therefore different manifest file). So the player needs to always send a wowzasession id to the origin otherwise we have multiple manifest variants on the CDN caches. This can lead to stream drops as the player just plays the chunks it has in buffer and then stops when the manifests don’t match.

Does Wowza 3 have better “support” for live streaming to avoid this issue or can we remove the sessionid requirement altogether to ensure that there’s only one manifest?

Thanks for your help

[Charlie_Good]

No, this has not changed. Wowza Server is not setup to be a caching origin. It is a feature we hope to add in a future version of the software.

Charlie

[Richard_Lanham]

It is not supported at present. A future version of Wowza might have an HLS origin feature.

Richard

[Jean-Francois_Maeyhi]

Hi,

I’m wondering about the behaviour of Wowza Session ID too.

I’m using Wowza 3 to produce HLS and HDS in Live Streaming.

I understand that Wowza needs different session ID but I wonder if the producted manifest files and chuncks could be the same inside ?