A series of questions and answers to help you debug responses from Stream H2B API and chose the best parameter values.
I'm having an error with the WebSocket API
First things first, update your SDK to the latest version if you are using one, and check the API Changelog. It might resolve your issue. If not, please check other entries of this page, or contact us with details about your issue.
Why do I get a
No match with a result matching my parameters?
For example, I request
digits?length=1, I say
One, and I get a
Oneas output of ASR.
First things first, please check the response header
Completion-Reason, where the server explains its result.
In the described case, the message is most certainly "confidence too low". Confidence threshold by default is equal to
0.5, and you can modify it. If response confidence is below this threshold, a
no-match will be returned, even if as human we see that the result was in fact correct.
In case your scenario is asking the user to answer by a single word, we highly recommend to lower confidence threshold to 0.35 or 0.4. When providing only one word, the ASR has not that much of data to be as certain as with a full sentence.
I'm streaming audio fine but I still get a
- Check that you aren't actually streaming silence;
- Check that you specified the right codec on join (for WebSocket);
- Check that your code is properly listening to the events returned by the API.