Anssi,
This is still not working for me.
I spent an hour on the phone with Akamai, and they told me that there is an authorization string that must be passed with the url. They gave me instructions on how to form the string, but when I do it, the player breaks. There is no debug info, and the controls are not present.
Here is what I had at first, according to your instructions:
clip:{
netConnectionUrl: 'rtmp://xxxxxx.live.edgefcs.net/live',
url: 'yyy@zzzzzz',
live: true,
provider: 'rtmp'
},
They say that it must be like this:
clip:{
netConnectionUrl: 'rtmp://xxxxxxx.live.edgefcs.net/live/yyy@zzzzz?auth=daEb3d.b1a_d.bdaQaCbKcaamanbgc0aJaC-bkL9DB-eS-GFComvuzrzDxqrCo&aifp=0001',
url: 'yyy@zzzzzz',
live: true,
provider: 'rtmp'
},
When I do this, the player breaks.
If I remove the last part: "&aifp=0001" , it doesn't break, but still does not stream.
Although it is possible to get Akamai to turn off the need for the auth parameter, we cannot do this, because we would run the risk of others pulling our streams, and costing us huge amounts of money due to the extra bandwidth.
So, we must have this authorization string in place in order to access our live streams.
Can you modify the player to be able to accept this information?
If you need actual working data, let me know, and I can email you the link to our xml files, so you can pull the auth token out in real-time. The auth token is only good for 5 minutes.
Kenny