Hi.

We have an app with a dynamic grammar. The grammar works well when the database has few entries (we tested it with 1800 records that each generated 3 entries on the grammar, so about 5400 entries), however, when the database grows (we are working with about 5000 records, 15000 entries, now) and we receive an error.unsupportedformat on the part of the voice browser. Is there a limit/recommendation for the maximum size of a grammar? Is there a maximum size for the generated grxml? If so, is it standard related? Can it be configured?

Thanks in advance

Please open a support request on the EP platform.

We have reduced the number of nodes in the grammar, and split it into two different grammars and we don't get that specific error anymore, however, the system does take a long time (>10secs) loading the grammars.

Right now they are dynamic grammars, would this process be faster if they were static?

We are not making expensive queries every time we need the grammars, just retrieving an object from the context and parsing through it to make the actual grammar rules. Should we use static grammars?

When using Nuance they have a "pre-precompiled" format. If this grammar does not change too often then you may want to try generating the grammar and pre-compiling using the nuance tools and then make it an external grammar. I suspect a plain static grammar would be about the same time as the dynamic. But it is worth trying the grammar as an external static. If that is still too slow then try the precompiled format.

It is a Loquendo. Does this still apply? If so, is this a Nuance/Loquendo setting, an EPMS setting or a OD setting?

Sorry I do not know. You owuld have to ask Loquendo.

As per your suggestion we brought it up with Loquendo and used satca (their tool) to create a builtin grammar, with that we created an external grammar.

Loquendo said that the URI was something like builtin:ro/anamehere, where anamehere is the name of the grammar we "compiled". However when we use it the system tries to obtain the build it grammar as a URL and of course returns a MalformedURL. How are we suppposed to write the URL?

Well for sure it will not work in html mode. Did you try on the platform?

What did the generated VXML look like?

Attached the generated vxml

So what happens when you run this on the real platform? External grammars will not work in simulation.

Attached the log information from the Experience Portal - errors from this application

It looks at the issue is with the voice grammar grmVozConsulta-srgssisr.grxml.

I am confused as to why the vxml looks like this:

<grammar mode="voice" xml:lang="es-co" maxage="0" weight="1.0" src="http://localhost:8080/Bcp/data/spanish/grammars/grmVozConsulta-srgs.grxml" type="application/srgs+xml"/>

and the Voice Browsser is fetching grmVozConsulta-srgssisr.grxml. However in an application we generate both the srgs and srgssisr grammars and it should be there. The errors to not seem to be related to :

<grammar mode="voice" xml:lang="es-co" maxage="0" weight="1.0" src="builtin:ro/ronombrepersonas" type="application/srgs+xml"/>


So at this point I am not sure if the Voice Browser errors match the VXML trace. Or some on deleted the srgssisr version.