The first point-to-point scenario between organizations is between StarLeaf endpoints. A StarLeaf user in one company calls a StarLeaf user in another company. The call can be dialed either by email address or directly by StarLeaf video address.

The figure below shows point-to-point call between StarLeaf organizations:

  • When dialed by email address, the StarLeaf call control engine performs a lookup within the StarLeaf Portal to check if that email address corresponds to a StarLeaf user and, if so, where within the StarLeaf Cloud that user is hosted
  • When dialed by video address (URI), no such lookup is necessary because the destination information (the far side’s StarLeaf border controller) is contained in the URI. The format of a StarLeaf URI is:
    8XXXX2YYY@othercompany.call.sl
    …where 8XXXX is the unique identifier of the ‘othercompany’ organization, 2YYY is the called user’s extension, and othercompany.call.sl resolves to the public IP address of the destination company’s StarLeaf border controller. The unique StarLeaf video address or URI of each user is in the ‘Welcome’ email sent by the StarLeaf Cloud to that user when they were first provisioned, and can be found and re-sent to them via the Portal web interface. This video address can also be found in the settings of the StarLeaf touchscreen controller or Breeze
  • The StarLeaf call control engine attached to the calling company organization receives the call setup signaling from the calling endpoint. The call control engine sends a setup message to the destination organization
  • The destination organization’s call control engine signals the destination endpoint(s) to ring, via its established tunnel connections to those endpoints
  • Signaling is exchanged back and forth along this route in order to connect the call.
  • When the call is connected, media negotiation takes place and media channels are established along the same route that the signaling took

The second point-to-point scenario between organizations is between a StarLeaf endpoint in one organization and an H.323 endpoint in another organization.

In the figure below, a StarLeaf endpoint calls a publicly-accessible H.323 endpoint which is not registered to the StarLeaf Cloud.

StarLeaf endpoint will be unable to call an H.323 endpoint which is connected only on a private IP address with no provision made for public connectivity. For example, if a Polycom endpoint is on a customer LAN and has the private IP address 192.168.0.25, dialing 192.168.0.25 from a StarLeaf endpoint, even on the same LAN, will not work, because 192.168.0.25 is not routable from mycompany.call.sl (which is on the public Internet).

When a StarLeaf endpoint calls an H.323 endpoint which is registered to the same organization, that H.323 endpoint is registered to the organization’s StarLeaf border controller (which has the ability to behave as an H.323 gatekeeper). Registering an H.323 endpoint with a StarLeaf organization allows its H.460 capabilities to be used for firewall traversal.