How to call between H.323 / SIP and StarLeaf endpoints
Using H.323 endpoints
Last updated November 20, 2020
This article describes calling from a third-party H.323 or SIP endpoint that is not registered to StarLeaf. Refer to How to make a call from StarLeaf-registered H.323 endpoints for calling StarLeaf endpoints from a registered H.323 or SIP endpoint.
Calls between a third-party H.323 or SIP endpoint that is not registered to StarLeaf and any other endpoint via the StarLeaf platform can only take place if firewall traversal is correctly configured for the H.323 endpoint. For more information, refer to Firewall configuration for calling from H.323 endpoints to StarLeaf.
Guest invite
The easiest way to tell someone how to call you (on your StarLeaf endpoint or app) is to invite them to a StarLeaf meeting. The meeting invite provides information on:- How to call you from a non-registered third-party H.323 or SIP endpoint (for example, Lifesize, Poly, Cisco)
- How to call you from their browser
- How to download and activate StarLeaf app
Sending a meeting invite
Schedule a StarLeaf meeting and include the guest email addresses in the participant list. When you send the invite, all dialing information for how to join the meeting is provided to the guest. This means that a guest can dial from their own video conferencing equipment or use the StarLeaf app. The external video address of a StarLeaf room system is displayed on the touchscreen controller in Settings > About (double tap the home button to access Settings). People outside your organization who do not use StarLeaf must dial your external video address or use the information in the tables below.Dialing format reference tables
The tables below show you how to dial into a StarLeaf conference from a third-party H.323 or SIP endpoint that is not registered to StarLeaf and also how to dial a StarLeaf user from a third-party H.323 or SIP endpoint that is not registered to StarLeaf.The destination border controller IP address is different between different organizations and even within an organization with different locations. The destination border controller IP address is dependent on which data center is used for the organization or user who you are trying to contact.
Conference dialing formats
| Endpoint provider | Dialing format: conference | Conference example |
|---|---|---|
| Tandberg | <7-digit conference code>@<subdomain>.call.sl | [email protected] |
| Cisco | <7-digit conference code>@<subdomain>.call.sl | [email protected] |
| Poly | <destination StarLeaf border controller IP>##<7-digit conference code> | 89.202.39.72##7930892 |
| Lifesize | <user’s StarLeaf border controller IP address>##<7-digit conference code> | 89.202.39.72##7930892 |
| Sony | <user’s StarLeaf border controller IP address>#<7-digit conference code> | 89.202.39.72#7930892 |
| Radvision | <user’s StarLeaf border controller IP address>##<7-digit conference code> | 89.202.39.72##7930892 |
| Avaya | <user’s StarLeaf border controller IP address>##<7-digit conference code> | 89.202.39.72##7930892 |
| SIP endpoint | <7-digit conference code>@<subdomain>.call.sl | [email protected] |
| Vidyo | <Vidyo Gateway service prefix><StarLeaf border controller IP address>,<StarLeaf organization prefix><7-digit conference code> | 0472.28.120.46,899657930892 |
| Codian bridge | <the .call.sl address of the organization>!<StarLeaf organization prefix><7-digit conference code> | example.call.sl!805497930892 |
Endpoint dialing formats
| Endpoint provider | Dialing format: endpoint or app | Endpoint example |
|---|---|---|
| Tandberg | <username>@<subdomain>.call.sl | [email protected] |
| Cisco | <username>@<subdomain>.call.sl | [email protected] |
| Poly | <destination StarLeaf border controller IP address>##<organization prefix><StarLeaf 4-digit extension number> | 89.202.39.72##899651138 |
| Lifesize | <user’s StarLeaf border controller IP address>##<organization prefix><StarLeaf 4-digit extension number> | 89.202.39.72##899651138 |
| Sony | <user’s StarLeaf border controller IP address>#<organization prefix><StarLeaf 4-digit extension number> | 89.202.39.72#899651138 |
| Radvision | <user’s StarLeaf border controller IP address>##<organization prefix><StarLeaf 4-digit extension number> | 89.202.39.72##899651138 |
| Avaya | <user’s StarLeaf border controller IP address>##<organization prefix><StarLeaf 4-digit extension number> | 89.202.39.72##899651138 |
| SIP endpoint | <username>@<subdomain>.call.sl | [email protected] |
| Vidyo | <Vidyo Gateway service prefix><StarLeaf border controller IP address>,<StarLeaf organization prefix><StarLeaf 4-digit extension number> | 0472.28.120.46,899651138 |
| Codian bridge | <the .call.sl address of the organization>!<StarLeaf organization prefix><StarLeaf 4-digit extension number > | example.call.sl!805491138 |
Vidyo users wanting to dial StarLeaf need to have a Vidyo Gateway on their network with Internet access. This example assumes that the default services configured on the Vidyo gateway have not been altered or deleted. The Vidyo user needs to discover the IP address of the StarLeaf border controller used by the destination StarLeaf user – this is obtained by pinging their call.sl hostname.
For example, say that mycompany.call.sl resolves to the IP address 72.28.120.46. Given a destination StarLeaf org ID of 89965 and extension 5014, the Vidyo user would dial 0472.28.120.46,899655014 to connect to the StarLeaf endpoint. 04 is the Vidyo Gateway’s default service prefix for HD video and , (comma) is its TCS-4 delimiter.Codian bridge administrators can initiate a call to a StarLeaf endpoint or conference from the Codian web interface.