Page 1 of 1

TTS Nuance RealSpeak 4.0 dis not read ph no in proper format

Posted: Wed Dec 02, 2009 1:21 pm
by amitkhosla
Hi ,
I see that there is some inconsistency in TTS Engine: Nuance RealSpeak 4.0 , few days back , to be specific on 25-11-2009 , the phone number that was entered was read as interger number , like 123,456,789,.. even though my code has

Code: Select all

<say-as type="number:digits"> 1234567890</say-as>
.
this code was developed and well tested , and it always read properly , and today when i tested, it again read properly and not as integer number but as one two three...
Is this due to any maitenance work that was going on or should i make any changes, please guide.

Thanks for the excellent support.

Regards,
Amit

timestamp needed for when IVR issue occured

Posted: Wed Dec 02, 2009 1:58 pm
by support
Hi,

Could you give us a timestamp of when you were experiencing this IVR issue? This would help us in better tracking down the IVR issue that may have caused this IVR problem.

Regards,
Plum Support

Posted: Wed Dec 02, 2009 2:03 pm
by amitkhosla
This is the exact timestamp
Timestamp: 11/26/2009 - 05:45:12am EST

thanks,
Amit

IVR example code for handling digits alternatively

Posted: Wed Dec 02, 2009 2:59 pm
by support
Hi,

For that day, we didn't notice any unusual behavior coming from our IVR servers that may have caused this IVR issue for you.

If you experience this issue again, please let us know so that we may further investigate this issue.

As a possible IVR code suggestion, the expression written in the IVR tag, <value> is what you would use in inserting commas into your variable that contains the 10 digits as this IVR code works consistently across all 3 TTS engines (AT&T, Cepstral, and Realspeak).


digitsappendcomma.php:

Code: Select all

<?php
header("Content-type: text/xml");
echo("<?xml version=\"1.0\"?>\n");
?>

<vxml version="2.0">

<var name="phonenumber" expr="1234567890"/>

<form>
<block>
<prompt>
<value expr="phonenumber.toString().replace(/(.)/g, '$1, ')"/>
</prompt>
</block>
</form>
</vxml>
Hope this helps.

Regards,
Plum Support