I press 1 or 2 immediately after the content tts has finished playing.
I'm on Google Fi with a Motorola MotoG6 Android v. 8.0.0. I've used this phone/carrier for a year now when making calls and haven't noticed this behavior before.
We've Moved! Please visit our new and improved forum over at our new portal: https://portal.plumvoice.com/hc/en-us/community/topics
Search found 4 matches
- Fri Apr 19, 2019 10:15 am
- Forum: Plum DEV Q&A
- Topic: Collect digits with bargein errors to noinput
- Replies: 4
- Views: 12654
- Thu Apr 18, 2019 2:32 pm
- Forum: Plum DEV Q&A
- Topic: Collect digits with bargein errors to noinput
- Replies: 4
- Views: 12654
Collect digits with bargein errors to noinput
I'm having an issue with an existing feature when collecting a digit from user using the builtin:grammar/digits?. I put the below vxml into a scratchpad and verified the problem occurs when calling the scratchpad as well. <?xml version="1.0"?> <vxml version="2.1"> <catch event="connection.disconnect...
- Tue Jul 17, 2018 4:13 pm
- Forum: Plum DEV Q&A
- Topic: TTS Addresses
- Replies: 3
- Views: 5671
Re: TTS Addresses
I'm using ATT's Natural Voices.
It seems converting street names to lowercase and having commas between steet name, city, state will cause it to read 'st' as 'street'.
It seems converting street names to lowercase and having commas between steet name, city, state will cause it to read 'st' as 'street'.
- Fri Jul 13, 2018 11:11 am
- Forum: Plum DEV Q&A
- Topic: TTS Addresses
- Replies: 3
- Views: 5671
TTS Addresses
Is there any documentation on using the <say-as type="address"> tag? I'm having issues where if I capitalize part of the address it will read it literally. For example "111 elm st" reads correctly.But "111 ELM ST" or "111 Elm St" reads 'S' 'T' instead of street? Is there a convention on capitalizati...