All three kinds of endpoints are used during the scheduling process to determine the resource capacity needed to host the meeting. However, each endpoint type is used in different scenarios. Which endpoint type you choose to supply usually depends on how much information you know about the endpoint and what additional features you need to support for that endpoint.

Provisioned endpoints should be used when you know exactly which endpoint will be attending the meeting, usually because a scheduler has specifically selected this endpoint, and that endpoint has been specifically configured on the system under the Endpoints tab. This is the best option to use if possible, because it allows the system to optimize the capacity reserved. For CTS endpoints, provisioned endpoints will also receive One Button To Push (OBTP) if they have been configured to do so. The organization associated with this endpoint will also have the supplied number of ports counted against it.

Unprovisioned endpoints should be used when you do not know which endpoint will be attending the meeting or do not have the endpoint provisioned in the Endpoints tab, but you do know which organization the endpoint will be coming from. This is likely to happen if your scheduling portal only asks the scheduler for the number of rooms that will be attending, rather than a specific list of rooms. Because the endpoint is unknown, the system will have to reserve the maximum amount of capacity possible to support any kind of endpoint. Additionally, OBTP cannot be supported because the system will not know which endpoint to send OBTP to. However, ports will be counted against the supplied organization. If you would like to have the system dial out to this endpoint when the meeting starts (instead of the endpoint dialing in) then you must specify the number and protocol of the endpoint to dial out to.

Remote endpoints should be used when absolutely no information is known about the endpoint that will be attending the meeting, including the organization it is owned by. The common use case for this would be an endpoint that is not managed by this system, such as an endpoint which is calling into the meeting from another service provider's network. No extra features, including capacity optimization, OBTP, or port management, are supported for this endpoint type. Unlike the other two kinds of endpoints, remote endpoints are always dial-in.