In my application, whenever I call sayText with one of the traditional voices all works fine. Now, I have a platinum plan and I linked my google cloud api key. All voices work when I test them inside SitePal. However, when I try to call those voices from sayText in localhost:5000, I get the following chain of errors:

sitepal:1 Access to XMLHttpRequest at 'http://cache-a.oddcast.com/tts/genC.php?EID=91&LID=2&VID=11&TXT=Hello%20Alice%2C%20it%27s%20great%20to%20have%20you%20here.&EXT=mp3&FNAME=&ACC=8688641&SceneID=2756818&HTTP_ERR=' from origin 'http://localhost:5000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

VHSSEngine_R.js:24 GET http://cache-a.oddcast.com/tts/genC.php?EID=91&LID=2&VID=11&TXT=Hello%20Alice%2C%20it%27s%20great%20to%20have%20you%20here.&EXT=mp3&FNAME=&ACC=8688641&SceneID=2756818&HTTP_ERR= net::ERR_FAILED 503 (The server is temporarily unable to fulfill the request. OK to re-resubmit.)
load @ VHSSEngine_R.js:24
cf @ VHSSEngine_R.js:28
Aa @ VHSSEngine_R.js:28
FU @ VHSSEngine_R.js:2
cN @ VHSSEngine_R.js:2
sayUrlWithID3 @ VHSSEngine_R.js:7
sayUrl @ VHSSEngine_R.js:7
_playAudio @ sitepalPlayer_v1.js:1
playAudio @ sitepalPlayer_v1.js:1
(anonymous) @ sitepalPlayer_v1.js:1
setInterval
vhsshtml5_callAudiotoPlay @ sitepalPlayer_v1.js:1
handleProcessAudioRequestsCall @ sitepalPlayer_v1.js:1
vhssHTML_handleProcessAudioRequests @ sitepalPlayer_v1.js:1
sayText @ sitepalPlayer_v1.js:1
chatResponse @ sitepal.js:717
(anonymous) @ sitepal.js:656
Promise.then
startSystem @ sitepal.js:644
vh_sceneLoaded @ sitepal.js:743
vhssHTML5_loadedCallback @ sitepalPlayer_v1.js:1
(anonymous) @ sitepalPlayer_v1.js:1
(anonymous) @ sitepalPlayer_v1.js:1
Promise.then
checkUserInteraction @ sitepalPlayer_v1.js:1
characterFullyLoaded @ sitepalPlayer_v1.js:1
(anonymous) @ VM817 VHSSEngine_R.js:7
(anonymous) @ VM817 VHSSEngine_R.js:8
(anonymous) @ VM817 VHSSEngine_R.js:14
eH @ VM817 VHSSEngine_R.js:20
(anonymous) @ VM817 VHSSEngine_R.js:14
F9.req.onload @ VM817 VHSSEngine_R.js:7
XMLHttpRequest.send
F9 @ VM817 VHSSEngine_R.js:7
(anonymous) @ VM817 VHSSEngine_R.js:14
(anonymous) @ VM817 VHSSEngine_R.js:7
L5.load.image.onload @ VM817 VHSSEngine_R.js:13

sitepal:1 Access to XMLHttpRequest at 'http://cache-a.oddcast.com/tts/genC.php?EID=91&LID=2&VID=11&TXT=I%20understand%20you%20might%20be%20concerned%20due%20to%20the%20recent%20discovery%20of%20BRCA1%20gene%20mutation.%20In%20order%20to%20guide%20you%20appropriately%2C%20can%20you%20share%20with%20me%20whether%20you%20have%20had%20any%20breast%20screening%20tests%20such%20as%20a%...' from origin 'http://localhost:5000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

VHSSEngine_R.js:24 GET http://cache-a.oddcast.com/tts/genC.php?EID=91&LID=2&VID=11&TXT=I%20understand%20you%20might%20be%20concerned%20due%20to%20the%20recent%20discovery%20of%20BRCA1%20gene%20mutation.%20In%20order%20to%20guide%20you%20appropriately%2C%20can%20you%20share%20with%20me%20whether%20you%20have%20had%20any%20breast%20screening%20tests%20such%20as%20a%... net::ERR_FAILED 503 (The server is temporarily unable to fulfill the request. OK to re-resubmit.)

In the case of TTS it just doesn't let me see the avatar, making it impossible for me to let the voice pronounce what I wrote. In the second case, it loads and loads until it says: "500 Origin Error"

When SSML is included in the text, TTS functionality will ocassionally fail.

A simple way to replicate this is to use the TTS demo at ttsdemo.com with the following text:

Shop opening times in Tokyo vary, but most department stores and malls open around <say-as interpret-as="time" format="hms24">10:00</say-as> or <say-as interpret-as="time" format="hms24">11:00</say-as> and close by <say-as interpret-as="time" format="hms24">20:00</say-as> or <say-as interpret-as="time" format="hms24">21:00</say-as>. Smaller shops and shopping streets may have different hours. Is there a specific shop or area youre interested in?

I believe it's due to the SDK chunking text into 2 separate chunks, which I saw in the API requests being made
Here are the two API requests made below. If you look closely, the first one gets cut off at <say-as interpret-as="time" format=, and the next request continues from where it was cut off ("hms24").
 

The API documentation for the sayText() function mentions that two streams would be used for 900 characters, but this is well below the 900 character limit as can be seen. Even if it exceeds 900 characters, we would like it to seamlessly be able to use SSML since it's an important part of our application.

Thank you in advance for any help you can provide.

i am using the sitepal in mobile browser but some time avatar is not visible but speaking is working. why?

for your knowledge i am using ReactJS at frontend side.

i am also getting issue when using dynamic resize, below the attached snapshot.

I'm working with an avatar component in a React.js application, and I want to know if there's a programmatic way to detect issues during various stages, such as:

• Loading the avatar

• Triggering the avatar to speak

• Stopping the avatar

Are there any callback functions, events, or listeners that notify us when something goes wrong?

For example, I want to handle situations like:

• Subscription/plan has expired

• Streaming limit has been reached

• The service is temporarily unavailable

• Network connectivity issues

Is there any built-in error handling mechanism or event hook that can notify us when such issues occur?