Akamai DASH Publishing URL

[Julie_Klevcova]

Hi Community,

We use Akamai CDN (MSL4) and I would like to start using DASH publishing there introduced in Wowza 4.6.0.03 (we have .04 update).

1. Does Wowza have Akamai certification of DASH publishing? It is not listed here - https://control.akamai.com/dl/customers/LIVEHD/AkamaiHD_EncoderGuidelines.pdf nor in its on-line version.

2. While article https://www.wowza.com/docs/how-to-stream-to-akamai correctly lists format of Playback URLs. Current version of Akamai MSL has different publishing URL. Ours ends with akamaientrypoint.net. However when engine takes all text snippets from Akamai Stream Target configuration, the publishing URL is created as http://post.$cp_code$.$domain$.r.akamaihd.net/dash/$cp_code$/DASH_TEST2/t588oqlq/media_video_1720kbps-15686.m4s

3. When testing this with Elemental encoders (they have Akamai DASH ingest certification), publishing URL is generated as expected -

http://post.$cp_code$.$domain$.r.akamaientrypoint.net/dash/$cp_code$/dash_test/dash.mpd

and chunk/segment is posted as http://post.$cp_code$.$domain$.r.akamaientrypoint.net/dash/$cp_code$/dash_test/dash_vidaud_5000k-1491467671.mp4

• Did I missed something?

• Is there a way how to override domain?

• We do not separate audio and video. It is one representation. Again, reference encoder works as expected.

Thank you for any hints and suggestions.

[Jermaine_Hemby]

Hello,

Thanks for contacting the Wowza Community!

Here is a article on DASH and Wowza. I’d suggest reading up on this and see how Wowza works with DASH.

DASH

Regarding Akamai, Wowza and DASH, Wowza may not be listed on the Akamai approved encoders, but it works.

You can add custom properties to override the hostname. Here is a link to another community post about this and lists the property to add:

https://www.wowza.com/community/questions/140/custom-mpd-redirect.html

If any further questions, feel free to contact us.

regards,

Jermaine

[Julie_Klevcova]

Hi Jermaine,

Thank you for hints on manifest redirection. However I was able to solve the problem by setting up properly Destination Host of Akamai target. While your proposed solution would definitely work, I wanted to keep application set up consistent as it will be controlled by API and it is simpler to use same way of configuring application outputs.

To answer my questions 2 and 3. Indeed, I missed something.

Regarding question 1, certification. Akamai Support can refuse to deal with problem if stream does not come from certified encoder. We used DVEO encoders - they have overtaken Helix server of Real Networks. DVEO continues in development and they did not renew certification since 2014. When we had problem with publishing to Akamai, Akamai refused to deal with this. To honor DVEO, they started the certification process after my complain.

Again thank you for hints not to stop searching.

Have a nice day!