Configure Conference v2 Endpoint
In this guide, you will learn how to configure a Conference v2 endpoint. The Conference endpoint is used to make meetings rooms, where two or more people can speak to each other. These meeting rooms have customizable access codes and can be reused.
I. Create Endpoint
In this section, we will go over creating a Conference endpoint through the portal. Then we will associate a phone number with that endpoint.
To set up a Conference endpoint, log into your CarrierX account. On the left-side menu, locate and click the Configure menu. Click Endpoints.
Click Add New Endpoint.
Enter a name for the new endpoint. This is a friendly name that is used for internal reference.
Check Provision Trunk Group to create a trunk group alongside the endpoint. A trunk group determines where a call should be routed. Trunks route calls to the appropriate endpoint by identifying the DID, or phone number, dialed and matching it to the trunk group that the DID is assigned to.
Choose Conference v2 from the Select Endpoint Type dropdown menu.
Click Create Endpoint.
II. Assign Phone Number
To assign a phone number to the new trunk group created alongside the Conference endpoint, navigate back to the Configure menu and click Phone Numbers. This phone number will be associated with this endpoint only, but multiple phone numbers can be associated with the same endpoint. Participants can dial any phone number associated with an endpoint.
Click a phone number that you would like to associate with the endpoint trunk group. In this example, we are selecting a phone number with no trunk group assigned to it already. You can select a phone number with an assigned trunk group and reassign it.
Once an available phone number is selected, scroll down and click Edit.
Select the trunk group of the newly-created endpoint from the dropdown list.
Navigate back to Endpoints under the Configure menu to locate API credentials that can be used to programmatically communicate with the API. Select the newly-created endpoint and scroll down to see the API Base URL, API Login, and API Password.
Now we have set up a Conference endpoint and associated a phone number with it. We will move on to configuring a meeting room.
III. Configure Meeting Room
In this section, we will configure a meeting room through the portal. A meeting room is a virtual meeting space that participants call into. These meeting rooms persist until they are deleted, so they can be reused. We will also create a container and assign it to the conference endpoint. This container will store any recordings made during meetings.
Navigate to the Configure menu and click Endpoints. Select the endpoint you want to configure a meeting room for. Click the Application: Conference tab. Then click Create new meeting room.
A Create New Meeting Room modal will pop up. Enter a friendly meeting room name.
There are three different access levels: host, participant, and listener. A host has full control over the meeting, a participant is able to listen and speak, and a listener is able to only listen. At least one access code must be set, either by typing in custom integers or clicking Generate.
In this example, we entered a custom access code for the host.
When you are finished entering or generating the desired access codes, click Create Meeting Room.
Once the meeting room has been created, it will be listed under Meeting Rooms. Multiple meeting rooms can be created under a single Conference endpoint. Meeting rooms persist until they are deleted.
Click a meeting room to see its details.
Click Edit to modify the meeting room.
Make your changes and then click Update.
Now that we have created a meeting room, we can test it by calling into the meeting room. Where you are, click the Assigned Phone Numbers tab beside the Application: Conference tab. This is the phone number to dial. Call it and type in an access code for the meeting room when prompted.
Meeting rooms can also be created and configured programmatically. Refer to the Create Meeting Room section in the Conference API Reference for more information.
IV. Set Up Container
To use the recording features of the bridge, it is necessary to assign a container to the endpoint. In this section, we will create a container and add it to the Conference endpoint. This container will be used for all of the meeting rooms and will store files of any recordings taken during meetings.
On the left-side menu, locate and click the Storage menu. Click Containers.
Click Add New Container.
An Add New Container modal will pop up. Enter a friendly container name.
Enter integer values for both Quota Bytes and Quota Files.
When finished, click Add Container.
Navigate to the Configure menu and click Endpoints.
Click the newly created conference endpoint and scroll down. Click Application: Conference tab. Then click Edit.
Select the newly created container from the container_sid dropdown menu.
Now that we have assigned a container to the endpoint we are working with, we can test to see if files will properly be saved. Start by calling into the meeting room we made earlier. Enter your access code. Once you are in the meeting, press *9 followed by 1 to confirm that you would like to start recording.
Speak to provide auditory input for the recording for at least several seconds and then hang up. Next, we will access the recording.
V. Access Recordings
In this section, we will access a recording through the portal. It is best to have created a recording at this point by following the steps above.
On the left-side menu, locate and click the Storage menu. Click Files.
If your container was properly configured, your meeting recording will show up on the list of files.
Click a file to view details. To listen to the recording online, click Publish URI.
Alternatively, refer to the Conference Playback quick start guide to configure a DID that can be called to listen to conference recordings.
VI. Next Steps
For more information, refer to the Conference v2 API Reference.
If you need to review some of the steps to configure a Conference endpoint, see our Configure a Conference Endpoint video.