The problem is not that it cannot use parameters - it is that when parsing parameters in URLs embedded in SSML, it does not parse or separate parameters, as these days parsers parse them.
There are several potential solutions for this, depending on how you can format the URL.
RFC 1866 used for recommendation of use; instead of &, and some servers allow this. Unfortunately, Firebase Storage is not one of them.
In most cases, Firebase Storage does not require a final marker parameter, so in this case you can omit it, but this is not a general solution to the problem.
Finally, you can use SGML encoding and replace both as & (note the leading ampersand and the end semicolon). So your SSML will look something like this:
<speak> <audio src='https://firebasestorage.googleapis.com/v0/b/assisto-skill.appspot.com/o/TIP103_converted.mp3?alt=media&token=d0d08f9d-e340-478c-af00-657109683136'> </audio> </speak>
This latter method is probably best suited for general purposes.
source share