Destinations are used to route a call to an endpoint representing a gateway. The subscriber creates Destinations to define sets of Routes to E.164 Codes. Destinations can also be Media Servers. While creating a Destination the subscriber has to specify whether this Destination is a Media Server or not.
The Lotus Sametime Unified Telephony enables the subscriber to reach a Destination via Routes of different signaling types and of different bearer capabilities.
When the subscriber creates a Route to a Destination, he/she specifies the Route's originating signaling type and originating bearer capability, enabling the subscriber to perform protocol and bearer capability-based routing.
Moreover, once the subscriber has created multiple Routes with the same originating signaling type and bearer capability to the same Destination (a "Route List"), the subscriber can configure the Lotus Sametime Unified Telephony to prioritize Route selection within each Route List, if desired.
Once the subscriber has created Destinations, he/she can assign these Destinations to E.164 Codes to specify the E.164 Code with which to associate each Destination.
Defining a DestinationParent topic: Routing and Translation
To create a destination, the administrator must go to the Destinations table that is either in the numbering plan of the user making the outbound call, or in the user’s business group’s common numbering plan, or in the global numbering plan, depending on how the prefix access codes and destination/E164 codes tables have been set up in the numbering plan of the user.
How to Add/Edit a Destination
This procedure describes how to create/edit destinations at the system wide or subscriber level.The administrator creates Destinations to define sets of Routes to E.164 DN Codes.
How to Delete Destinations