Managing StarLeaf platform and traffic routingLast updated April 7, 2021
When you have a meeting with three or more endpoints, this is known as multipoint conferencing.
In this topic:
- Multipoint conferences between endpoints in the same organization
- Multipoint conferences between endpoints in different organizations
- Multipoint conferences including third-party endpoints
In a point-to-point call in the same organization, StarLeaf endpoints have a direct IP route to each other. However in a multipoint conference, all the media must be transcoded by the StarLeaf platform. Each endpoint sends and receives its signaling and media through the StarLeaf border controller. The endpoint accesses the call control and media engines that are needed to make the multipoint conference work through the border controller.
The figure below shows a multipoint conference between StarLeaf endpoints in a single organization:
This situation leads to a higher load on the organization’s Internet connection. Because the video contributed from each endpoint in the conference is shown at a much lower resolution than it would be on a point-to-point call, the bit rate at which each endpoint transmits media is much lower than on a point-to-point call, typically 0.5 mb/s instead of 1.5 mb/s.
When endpoints outside the host’s organization join a meeting, their signaling and media are routed through the other organization’s StarLeaf border controller (in the case of external StarLeaf endpoints), or through standard H.323 or SIP calls across the Internet to the destination endpoint.
The figure below shows a conference including external StarLeaf endpoints:
In the following diagram the meeting includes a third-party endpoint outside the organization that has a public IP address: