The purpose of this article is to group common challenges application developers might encounter when using Edgecast (formerly known as Verizon Media) as the back-end.
1/ When you tokenize a URL, you are also specifying an expiration date. It is possible that your expiration date has passed when you initiate the casting session. Your stream will no longer be valid when this is the case, and result in unsuccesful casting.
The solution? Use an expiration date that is valid for a longer time.
2/ An Edgecast token will be attached to one IP address when it's invoked for the first time (i.e. request to the Preplay URL with the token as a query parameter). This could cause problems when either your sender device (i.e. iOS app, Android app, browser) or reciever device (i.e. Chromecast device) uses an iPv6 address, because those addresses are unique. (Meaning: the token could be invalid for your IPv6 receiver device because it was already attached to your different IPv4 sender device.)
pp2ip=0to your token (and Preplay parameters).
If you notice that THEOplayer doesn't expose all your Edgecast MPEG-DASH video qualities,
then the likely culprit is not aggregating the different
AdaptationSets as part of Edgecast's multi-key approach.
singlevideolicense=1 to your Preplay parameters and/or token.
Doing so will group all qualities to one
AdaptationSet with one key.
Refer to Preplay - tokenization.