Hello,
We are trying to send some vendor specific parameters to Sestek Recognizer server via CVP 10.5. We are adding those vendor specific parameters to form element on Call Studio and try to send them via MRCP v2 protocol. We couldn’t see the parameters that we send when we checked RECOGNIZE body on MRCP SR Server logs.
After that, we checked VoiceXML debug log. We found that log on debug log.
Sep 1 13:52:18.801: //-1//VXML:/vxml_tree_lock:
vxmlp=C2C28578 usage_cnt=0
Sep 1 13:52:18.801: //0/559690A88090/VXML:/vxml_property_build:
at line 3: : <property name=com.sestek.UseCallSteering> UNKNOWN, ignored
Sep 1 13:52:18.805: //0/559690A88090/VXML:/vxml_parse:
After that, we tried nuance vendor-specific paramters instead of sestek vendor-specific parameters. But result didn't change.
Sep 1 15:16:51.737: //0/25FF3AF48097/VXML:/vxml_property_build:
http://10.0.0.1:7000/CVP/Server?_dnis=2641&application=IVR_SESTEKEntegration&callid=25FF3AF44FDA11E58097588D09BAE670&_ani=888881744
at line 3: : <property name=com.sestek.UseCallSteering> UNKNOWN, ignored
Sep 1 15:16:51.737: //0/25FF3AF48097/VXML:/vxml_property_build:
http://10.0.0.1:7000/CVP/Server?_dnis=2641&application=IVR_SESTEKEntegration&callid=25FF3AF44FDA11E58097588D09BAE670&_ani=888881744
at line 8: : <property name=com.nuance.client.MinPreSpeechSilenceSecs> UNKNOWN, ignored
Voice XML Server block those parameters.
Then i checked some cisco documents and i found that;
“The VoiceXML property names and values are simply entered in the VoiceXML property table exactly as they are to look in the resulting VoiceXML (Unified CVP does no validation or modification of the data)”
If Unified CVP does no validate our parameters, why block them on run time? Are we missing something on VoiceXML gateway configuration?
Thank you for your help in this matter.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Comments
0 comments
Please sign in to leave a comment.