Parameters are passed to BBB either as core parameters, meta parameters or custom parameters. These are:

• Core parameters. We don't changed, they are as is in BBB. And BBB is expecting a value already.
• Meta parameters. This is extra information that we want or need to persist after the meeting has finished. This means that meta parameter will be part of the recording.
• Custom parameters. These are extra parameters that can be passed as part of the request and they will be interpreted by BBB during the live session, or by analyzing logs. These are not persisted

We need to be able to pass meta parameters and custom parameters

Meta parameters follow the notation meta_KEY=VALUE

The KEY can be anything that can be a parameter in a standard URL

meta_name=TEST
meta_name_composed=TEST
meta_name-composed=TEST
These three are valid meta parameters, and we should support them

arbitraryparam=TEST
arbitrary_param=TEST
any-arbitrary-param=TEST
any_combined-arbitrary_param=TEST
sufix_parameter_name=TEST
AnyArbitraryParam=Test

All these are valid custom parameters and we need to support them

The KEY can also support numbers, letters, underscores and dashes.

As it is right now,  not all these cases are being covered

BUG:

[ ] passing a parameter such as one=TEST should be passed as custom parameter instead of meta_one=TEST

[] parameters set with a prefix_ are ignored. Eg. prefix_one=TEST, should be passed as is.

[] parameters set an underscore in the name are ignored. E.g. name_of_the_parameter=TEST should be passed as is.

[] meta_ should be optional for the user who sets the key/pair. Right now always adds meta. 

[ ] when adding a new parameter, it always assigns the first predefined value in the list by default. activity.info.iconurl