Multiple Business Groups spanned across Telephony Control Server systems in a hosted environment realize the required SIP and/or SIP-Q Private Networking Endpoints for each Business Group via 'virtual endpoints'.
Telephony Control Server matches the alias provisioned on a SIP endpoint with the domain part of the URI in the Contact header field of the received SIP/SIP-Q request. A single alias can only lead to a single endpoint; therefore aliases configured on endpoints must be unique. Telephony Control Server is only capable of sending its IP address in the domain part of the URI in the Contact header field of an outgoing request to an endpoint. As IP addresses are unique, this can only lead to a single endpoint.
The introduction of the concept of 'virtual endpoints' allows the administrator to create multiple SIP and/or SIP-Q endpoints for the same Telephony Control Server system, each with a unique alias, so that the correct endpoint can be found for an incoming request. Before checking for a match on the alias of the domain part of the URI in the Contact header field, Telephony Control Server shall check whether there is a matching alias for the domain part of the Request URI of the incoming request.
As the request URI of a SIP request always points to the intended target Lotus Sametime Unified Telelphony Server system, this results in the following:
The Telephony Control Server that is sending the request must be set up to use FQDNs rather than IP addresses in the Primary Signaling field because this FQDN will be used by the target Telephony Control Server as an alias to find the Lotus Sametime Unified Telelphony Server system that sent the request.Parent topic: Networking
The Telephony Control Server that is receiving the request must configure the FQDN received in the domain part of the Request URI as an alias for the endpoint that represents the sending Telephony Control Server.