we show an example
1. Create RMX entry queue (see Fig.1) with the number of 0000000008 (or any other number)
2. Create the CMA service "gateway" with the prefix 0000000008 (see Fig.2)
3. Create a Dial Rules with routing action": route to a GW service, where we write up service 0000000008
4. So the result is: subscribers when dialing 7000004хххх will create conference rooms xxxx.
In fact, in the given example - 7000004хххх is a prefix which brings with calls from AVAYA. Subscribers AVAYA just trying xxxx, just spelled out of 100 rooms (1100-1199)to gather audio conference. For video conferences spelled out other prefixes, but the technology is the same.
another simple way just create enterry que and check enable adhoc option in entry queau and set that default entery queau of RMX whenever some one dial to RMX alias or signalling ip RMX prompt for confrence id just put what the numeric id and you will lands on your self created meeting room.
default entry queue is easier. But here we are limited to one profile conference.
Often required for different connections to prescribe different profiles. For example, part of subscribers to be connected with CIF resolution. In this case, for they provide the connection through entry queue with the same profile conference.
Another example: cascade connection. It is necessary to neighboring bridges connected to the conference a "slave". Redirect incoming calls from them through the cascade entry queue. And so on, examples can be many.
i guess it depend of type of confrence profille whether its SVC confrence profille or AVC confrence profille