Results 1 to 4 of 4

Thread: httpRandomizeMediaName parameter

  1. #1
    Join Date
    Jan 2016

    Default httpRandomizeMediaName parameter


    Is the httpRandomizeMediaName parameter True by default ?
    What is the best way to set it to False ?


  2. #2


    Hi Philippe.

    If your running an HTTPOrigin application, then yes, httpRandomizeMediaName is set to "true" by default.

    Here is a bit more detail about this property, and how to edit it:


    Set this property to true to help to ensure that the chunks in live streams are unique if the encoder is restarted.

    Wowza Streaming Engine Manager configuration

    In Wowza Streaming Engine Manager, click the Applications tab, and then click the name of your HTTP origin application in the contents panel.

    On the HTTP origin application page Properties tab, click Custom in the Quick Links bar.

    Note: Access to the Properties tab is limited to administrators with advanced permissions. For more information, see Manage credentials.
    In the Custom area, click Edit.

    Click Add Custom Property, specify the following settings in the Add Custom Property dialog box, and then click Add:

    Path - Select /Root/Application/LiveStreamPacketizer.

    Name - Enter httpRandomizeMediaName.

    Type - Select Boolean.

    Value - Enter true.

    Click Save, and then restart the application to apply the changes.

    XML configuration

    Use a text editor to open the [install-dir]/conf/[application]/Application.xml file for your HTTP origin application and add the following property to the <LiveStreamPacketizer>/<Properties> container. Be sure to add the property to the correct <Properties> container in Application.xml as there are several such containers in the file.
    Restart the Wowza media server software to apply the changes.

    ]Note: If you want to use Wowza nDVR as an HTTP caching origin, you must also add this property to the Root/Application/DVR path (<DVR>/Properties container) to your live application that has Wowza nDVR enabled.



  3. #3
    Join Date
    Jan 2016


    We have 2 Wowza servers (1 Origin and 1 edge) but not using HTTP Origin
    When 2 users watch the same HLS Live, they get different names for the same chunk
    i.e. media_w722651843_b800000_368.ts and media_w165004100_b800000_368.ts
    Is there a way to change that and get the same name ?

  4. #4
    Join Date
    Sep 2011


    That's the Session Id (w722651843) which is unique to each client. You can remove the Session Id by using a HTTP origin application but this will have other effects such as stopping the use of session based communication and logging connection counts which are outlined in the article for HTTP origin applications. If you're using Wowza Streaming Engine as an origin and Wowza Streaming Engine as the edge, then it's not required to remove the Session Id. Removing the Session Id is for when you're not using Wowza Streaming Engine as the edge(s) and so you're wanting to cache the HTTP chunks.


Similar Threads

  1. Replies: 2
    Last Post: 07-29-2015, 04:00 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts