Hello Sylvain,
The voice can be specified from the MRCP client by means of the header field Voice-Name. See section 5.4 in the
Usage Guide.
This may not be under your control, though, since the VoiceXML platform that you use sets the name as an attribute to <speak> in SSML, which Google Text-To-Speech API does not seem to observe.
If you do not have any means to set the corresponding MRCP header field, then in next version of the plugin, we can add a global configuration parameter in umsgss.xml allowing to specify the default voice name. Alternatively, this issue can be addressed by rewriting the content of <speak> element to make it in compliance with the Text-To-Speech service, which would be harder to achieve but is somewhat already implemented in the BingSS plugin.