When the Meet-me Conf field is enabled, the collect vector step collects the next six digits. The vector step then uses those digits as the access code for a Meet-me Conference call. See vector steps 1 and 3 in the example in Call Vector screen Page 1.

The goto vector step has three conditions:

The meet-me-idle condition routes the first caller who accesses a Meet-me Conference to the conference call. An announcement step that tells the caller that he is the first party to join the conference can be played. See vector steps 6 and 11 in the example in Call Vector screen Page 1.

The meet-me-full condition is used when the Meet-me Conference already has the maximum of six parties on the call. See vector steps 7 and 14 in the example in Call Vector screen Page 2.

If the 12–party Conferences field is enabled in the Feature-Related System Parameters screen, the meet-me-full condition is used when the Meet-me Conference already has the maximum of twelve parties on the call.

The meet-me access condition ensures that the access code is valid. If the access code that the caller dials is the same as the access code that is administered for the VDN, vector processing continues. See vector steps 2 and 4 in the example in Call Vector screen Page 1.

The route-to vector step has one condition:

This condition adds the caller to the Meet-me Conference call, and all parties on the call hear an entry tone. The meetme condition is valid when the caller enters the correct access code, and the number of parties who are on the call already is less than six. See vector steps 9 and 12 in the example in Call Vector screen Page 2.

If the route-to meetme step fails, vector processing stops, and the caller hears a busy tone.