02-18-2015 02:21 PM
We're trying to integrate a new Nuance Vocalizer deployment with CVP 10.0(1) using VXML applications built in CVP Call Studio... the MRCP request is getting to Nuance, but it's throwing an error when it tries to parse the SSML:
Feb 18 13:33:12.02|TUCPU=78|TKCPU=15|TID=3380|2|6011|SID=6D35FEA1-B6D311E4-BCAD9A16-F89E5FCE@10.3.12.41|CRSAPIUserDataState::cbTtsLogError|Vocalizer SEVERE error 1440, SSMLPARSER\|SSML parse error. message\=There is no Grammar for uri: ., line\=1, column\=77.
Feb 18 13:33:12.04|TUCPU=78|TKCPU=15|TID=3380|2|6011|SID=6D35FEA1-B6D311E4-BCAD9A16-F89E5FCE@10.3.12.41|CRSAPIUserDataState::cbTtsLogError|Vocalizer SEVERE error 1458, SSMLPARSER\|SSML parse error: element 'speak' is not recognized, the 'xmlns' attribute is probably missing or incorrect. line\=1, column\=77
As far as I can tell, it's looking for xmlns, which is not present in the request coming from CVP:
Feb 18 13:33:12.02|TUCPU=0|TKCPU=0|TID=2480|0|2001|CBaseConnection::processConnection|Received 269 bytes: Kill-On-Barge-In: false@#Speech-Language: en-US@#Logging-Tag: 4088873@#Content-Base: http://mediaserver:7000/CVP/@#Content-Type: application/ssml+xml@#Content-Length: 96@#@#<?xml version\="1.0" encoding\="UTF-8"?><speak version\="1.0" xml:lang\="en-US"> Hello World</speak>
How do you set xmlns? I cannot find any references anywhere.
From Nuance's test harness, I'm expecting something like:
<speak version="1.0" xml:lang="en-US" xmlns="http://www.w3.org/2001/10/synthesis">
Thanks,
Michael.
02-24-2015 07:47 AM
CVP Usually generates the VXML Pages which will have TTS string mentioned in call studio audio element with in the VXML Prompt Element as given below.
<prompt>
Hello World
</prompt>
VXML Browser which in our case is VXML Gateway, extract out the text and create the SSML and offer the same to Nuance for processing. VXML Browser to create the SSML as
<speak version="1.0" xml:lang="en-US" xmlns="http://www.w3.org/2001/10/synthesis">
Hello World
</speak>
The Browser creates it based on its knowledge about the targeted Media server, I think the xmlns is mandatory in the Nuance configurations and Browser is not generating the same. You have following options.
02-24-2015 08:07 AM
Thanks. According to Nuance support, the SSML needs to be fixed--even with SSML parsing set to "WARN" instead of "STRICT"--so it's over to Cisco TAC.
Michael.
02-24-2015 08:19 AM
Can you follow up and let us know once there's an ES and let us know the
fix number?
For my notes, what version of Nuance TTS and CVP are you using?
02-24-2015 08:53 AM
Will do, Janine.
I will confirm the specific Nuance versions when we get the answer back from Cisco; I need to get them from my infrastructure specialist. It's supposed to be the latest compatible NR10 point release, per Nuance.
The CVP version is 10.0(1), IOS 15.2(4)M7 on 3925s (Co-resident Ingress/VXML) for the gateways.
Cheers,
Michael.
03-13-2015 01:20 PM
Just to close this out... we ended up having to set the SSML validation to "none" in Nuance, instead of "warn", which was specified in the Cisco documentation.
Michael.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: