Joshua C. Colp

The contributor license agreement has not been signed. Until that is done this PR can not be reviewed.

Additionally, a PR should contain a [single commit](https://wiki.asterisk.org/wiki/display/AST/Code+Contribution) and our commit messages have a [defined format](https://wiki.asterisk.org/wiki/display/AST/Commit+Messages).

This sounds like a major rearchitecture. Such things should really be discussed ahead of time, for example this would need to be backwards compatible to go into any current branches...

With the place to discuss such things being https://groups.io/g/asterisk-dev

We could, but things should still happen or be recorded in a location where others can participate over a period of time and where it can be referenced for historical...

As well, the way that AEAP handles this is it registers multiple engines each with a unique name, so I don't see why this needs to be that aware of...

@nshmyrev That is what grammar was originally for in older engines so would make sense.

Personally as a user, I would not want that. I would want to just be able to specify multiple grammars and have the engine provide the results back to me...

Okay, I think this really needs a set of non implementation specific requirements and user stories.

The install_prereq script is not used, the failing tests can be ignored for this PR.