Last updated: August 30, 2019
A Conference represents a connection between two or more Calls and must be created explicitly. You logically cannot add a participant to a conference that does not exist. A conference is created either through the CreateConference PerCL command or through the REST API by posting to the /Conferences endpoint. Learn more about conferences created through the REST API in the Conferences section of the API reference.
When the CreateConference PerCL command is used by the application, the actionUrl also is invoked upon the conference being created. The application can respond to the actionUrl with a PerCL script that updates the conference — for example, to add a participant to the conference.
The start of a conference (status = inProgress) occurs when at least one participant is a start-moderator. A start-moderator is one who has the startConfOnEnter flag set. In FreeClimb, there can be any number of start-moderators. Recording of a conference also starts when a conference starts. Note that the conference recording option must be enabled at the time of creation of the conference.
A conference ends and returns to the empty status when the last participant leaves the conference. If recording of the conference active, the recording ends when the conference ends. The application may choose to terminate the Conference resource or to leave it empty for reuse.
It is possible to repopulate an empty conference with participants. Such reuse is possible up until the time the conference is terminated using theTerminateConference PerCL command. When terminated, a conference is first emptied of its participants and is then archived to the FreeClimb database. The ID of an archived conference will not be reused by FreeClimb when creating another conference. Note that terminating a conference doesn't delete the Conference resource from the account that owns it.
