Routing and translation features provide such capabilities as Public Numbering Plan compliance and routing that varies depending upon such factors as origin, traffic, and time of day.
Most of the configuration tasks for subscriber management are accomplished using the Assistant (e.g., configuring BGs (Business Groups), user information and status, connection types, SIP phones, etc.) However, a few tasks in this group can be done using the CLI (Command Line Interface). Mainly, though, the CLI can be used to display these settings once they have been configured.
Common Routing Concept - Mandatory Call Routing Rules
The minimum patchset level of a Lotus Sametime Unified Telephony legacy system to setup the call routing is PS15E07! Routing decisions always start on the PNP level and may pass further decisions to the GNP which is common to all BGs. The GNP has a predefined name: E164 NANP (which means E.164 North American Numbering Plan, but is not restricted to US numbering schemes).
Common Routing Concept - Open Numbering
In an Open Numbering scenario the subscribers are configured with full E.164 numbers. These E.164 numbers are unique for the complete switch, but the extensions are not unique!
Common Routing Concept - Closed Numbering
In an Closed Numbering scenario subscribers are configured with full E.164 numbers, The E.164 numbers as well as the extensions are unique! Within the same branch/location subscribers reach each other by dialing the extension.
for the complete switch!
Common Routing Concept - Tail End Hop Off
In an Tail End Hop Off scenario subscribers are configured with full E.164 numbers, extensions are unique
. Within the same branch/location subscribers reach each other by dialing the extension
A-Side Signaling-Based Routing
The A-side signaling-based routing feature provides for the selection of a route to a destination based on the signaling protocol of the originating party.
The alternate routing feature provides flexibility to support different routes. It provides for the delivery of traffic from a specific subscriber to the network specified by the Lotus Sametime Unified Voice administrator. It also provides the capability to specify a prioritized list of possible routes to reach the destination.
Alternate Routing with Overflow Among Route Types
The alternate routing and overflow among route types feature provides for calls to be routed to the same destination via alternate routes where a route can be a SIP-Q gateway or SIP server. The routes leading to a destination can be prioritized for routing purposes. Moreover, if one route (such as a SIP-Q gateway) is unavailable, the call can overflow to a different route even if it is of a different type (such as a SIP server).
Call Diversion for Invalid Destinations
After Lotus Sametime Unified Telephony processes incoming external calls arriving over a SIP or SIP-Q trunk interface, the call can be diverted to a valid preconfigured alternate destination if translation of the called party results in an invalid destination.
Lotus Sametime Unified Telephony provides the capability to configure call routing to gateway destinations in a manner such that calls use the least expensive path available to the enterprise network, while also ensuring acceptable voice quality. This capability was formerly known as LCR (Least Cost Routing) in legacy systems.
International Translation Support
The international translation support feature provides E.164 capabilities needed to address international requirements, such as the handling of hexadecimal digits in the prefix table and the E.164 routing tables.
Access Code Routing Concept
8k uses source-BG access codes (one per BG only) and destination access codes for terminating/tandeming incoming calls and routing outgoing calls via XLA. The 8k mechanism for this is called Access Code Routing.
Unified number Subscriber Identity
Unified number subscriber identity is the provisioned business group line identity where CSTA + unified number call services are provided.
Every Business Group needs to have a Default Office Code assigned to it. When creating a new Business Group or when changing the default office code of a BG, you need to specify or define a Default Office Code to be assigned to the BG, in addition to giving it a BG name and a Display number.
Directory Numbers are system resources that can be assigned to Subscribers, Endpoints, Services or Intercept Destinations across the Switch or be reserved for exclusive use within a specific Business Group.
Home Directory Numbers (Home DN)
This is the main number associated with the subscriber. The subscriber's Directory Number can be either a Public (E.164) or a Private (L2, L1, or L0) number.
Main Pilot DN
The administrator has the option to configure a subscriber that is an MLHG member to use the Name and Number of the Main Pilot DN as the subscriber's identity for Internal and/or External calls.
External Caller ID
The External Caller ID feature provides the subscriber with a second number which must be used for all external calls, incoming and outgoing.
BG Display Number
The BG Display Number is the default number that will be used to send to the public network in case Lotus Sametime Unified Telephony has no other public number available for a subscriber.
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 Destination Codes feature provides destination codes for basic telephone service. The destination code will be used for a call if the dialed or modified (in PAC) digits and the Nature of Address are matching. This field specifies the number configured for this Destination Code. A Destination Code Number is the leftmost digit string pattern identifying a group of Directory Numbers. Destination Codes can be of length 1-15.
Bulk Editing Destination / E.164 Codes
The Bulk Edit
feature allows the user to modify more than one data record of the same entity simultaneously via the GUI.
Time Destinations/Time-of-Day Routing
The Time-of-Day routing allows the routing of calls to the same E.164 Destination Code via different routes depending on the time of day and the day of the week.
Origin-Dependent Translation and Routing
The Lotus Sametime Unified Telephony provides origin dependent translation and routing for calls handled by multiple feature servers in a VoIP (Voice over IP) network.
A route connects the destination with an endpoint representing a gateway.
Lotus Sametime Unified Telephony supports dialing numbers for a subscriber that are shorter than the numbers provided by the public or the private numbering plans. These short numbers are called extensions and they must be the trailing part of either the subscriber number (public numbering plan) or the local number (private numbering plan.
A generic destination is a physical location in the telephone or IP network that contains a prioritized collection of routes that can be used to arrive at that destination. This is the starting point for finding a free trunk when allocating trunks for an outgoing call.
Bearer Capability-Based Routing
Bearer capability-based routing allows routing of calls to different TKGs (Trunk Groups) based on the originator's bearer capability.
Leading Digit and Most-Matched Digit Translation
The Leading Digit and Most-matched Digit Translation feature provides mechanisms to quickly and accurately route calls.
Source-Based IP Routing
For redundant configurations, enterprises have the possibility to define more than one default gateway for Lotus Sametime Unified Telephony to use when sending packets to the network from VLAN/subnet-separated networks—specifically, the management, signaling, and billing/CDR (Call Detail Recording) redundant connections from each node.
Subscriber Routing Options
Several logical database objects provide the capability to route calls in various manners. Common examples of these objects include the PAC (Prefix Access Code), DC (Destination Code), LC (Location Code), and extension tables.
Subscriber Routing Options - Extension Dialing via PNP (Private Numbering Plan)
Extension dialing via the PNP (Private Numbering Plan) allows extension-based dialing to be kept and controlled within the logical confines of the PNP in which the calling subscriber is defined.
Subscriber Routing Options - Extension Dialing via PNP (Private Numbering Plan) and GNP (Global Numbering Plan)
Extension dialing via the PNP (Private Numbering Plan) and extension to the GNP (Global Numbering Plan) tables allows extension based dialing to be routed to a globally usable set of entries for all BG (Business Groups) and PNPs, to include globally defined gateways/endpoints.
Subscriber Routing Options- Home DN (Directory Number) Dialing via PNP (Private Numbering Plan)
Home DN (Directory Number) dialing via the PNP (Private Numbering Plan) allows digit-based dialing between subscribers to be kept and controlled within the logical confines of the PNP in which the calling subscriber is defined.
Subscriber Routing Options - Home DN (Directory Number) Dialing via PNP (Private Numbering Plan) and GNP (Global Numbering Plan)
Home DN (Directory Number) dialing via the PNP (Private Numbering Plan) and extension to the GNP (Global Numbering Plan) tables allows digit-based dialing to be routed to a globally usable set of entries for all business groups and PNPs, to include globally defined gateways/endpoints.
Routing Area and Classes of Service Definition
Use of routing area (RA) and class of service (COS) definitions are optional. Both parameters are used in the call routing process, along with the dialed digits, and both are defined under Administration on the Telephony Control Server Assistant navigation bar. Routing areas are sometimes referred to as rate areas, a term commonly used in the public network.
A routing area is created in order to define the Office Codes associated with specific geographical locations within a specific area.
Classes of Service
CoS (Classes of Service) are used to control the access rights/permissions of E.164 Destination Codes.
Calling locations allow the subscriber to route emergency calls to the appropriate answering point.
A Traffic Type identifies the type of call, e.g. national, international, etc. Optional (defaults to UNDEFINED or NONE). This is used to set the callType value which is passed to UCE and Services component. Many services, e.g. toll restriction, Auth Code, and Call forwarding restriction make use of the callType returned by XLA. The emergency call type is used by UCE to allow the call even if the user is not authenticated or allowed to make any calls.
Classes of Restriction
The predefined Classes of Restriction are used to make a decision on whether to disallow the call or to request an authorization code before allowing the call to go through, request an Account Code before the call goes through(if system is set to post-dial Account Code) or to restrict Call Forwarding to pertinent targets.
Routing Calling Locations
Calling Locations can be assigned to a subscriber to indicate the geographic location of that subscriber. They are used when specific routing has to be done for these subscribers. They can be used to have specific geographic routing of an emergency service or a directory service number.
Display Number Modification
The display number modification feature provides administrators the capability to modify the display format of a number (for example, from international to national format) or to add or remove the PNAC (Public/Private Network Address Code) and prefixes to or from the number before it is presented to a user.
DNM Prefixes Table
This table specifies the network access codes and prefixes that are defined for a specific numbering plan, a specific business group or system wide. The display number prefixes table allows an administrator to enter the prefixes for the public and the private numbering plan.
DNM Definitions Table
The DNM Definitions table specifies the definitions of numbering schemes that exist within a numbering plan, business group or even system wide. It allows Lotus Sametime Unified Telephony to decompose a number from the public or private numbering scheme into the code components.
Display Number Modifications Table
This table defines how an input number is modified from its original form, depending on originating info (BG, NP), terminating info (BG, NP and optionally endpoint). The output type of number may also be specified set for optimization, if desired.
Display Number Normalizations Table
This table specifies the entries to normalize any type of input number to a fully qualified public (international) or private (L2, L1 or L0) number. The administrator can specify endpoint specific, numbering plan specific, business group wide and even system wide entries.
Display Number Conversions Table
This table specifies the number conversion entries that can be created to convert a public normalized number to a private normalized number or a private normalized number to a public normalized number. A special Auto-Reverse parameter allows the administrator to request an automatic creation of the reverse entry; i.e. if a public to private conversion is specified then setting the auto-reverse option will trigger the system to automatically create the private to public number conversion.
Display Number Local Toll Table
This table specifies a list of exchange codes that are local given a specified country, area and local exchange code. The area code and exchange code are known as the 'Home Area Code' (aka Home NPA) and 'Home Local Exchange Code' (aka Home LOC). A dial pattern needs to be specified that indicates how numbers are dialed within the Home Area Code if the Local Exchange Code of the number is NOT
specified in any of the exchange code lists for the specified local toll table.
Display Number Modification Use Cases - General Assumptions
This section describes various use cases that will show the provisioning needed to make each use case work.
Display Number Modification - Normalization for CSTA
On the CSTA interface device identifiers must be in either GNF (including the '+') or in Fully Qualified Private Number format. This has for consequence that when receiving calls from SIP endpoints or subscribers, normalization of the incoming calling party number may be required. The number normalization tables must be set up to allow this normalization.
Display Number Modification - Normalization for SOAP
Normalization for SOAP is the same as normalization for CSTA, except that instead of the number received from the endpoint or subscriber, the result from translation is used. The SOAP interface allows an application to request the normalized number for a dialed string given the context of the Home Directory Number of a subscriber on Lotus Sametime Unified Telephony.
This comprehensive Lotus Sametime Unified Telephony management solution permits for unified administration of networks made up of Lotus Sametime Unified Telephony real-time IP systems, applications, and industry-standard third-party products.
Endpoints and Endpoint Management
Endpoints are external devices, e.g. Gateways, Proxies or SIP Trunks and also SIP endpoints, like SIP telephones and analog endpoints.
Bulk Editing Endpoints
The Bulk Edit
feature allows the user to modify more than one data record of the same entity simultaneously via the GUI.
Once you have determined the Endpoints within the Zones for the Lotus Sametime Unified Telephony system, you can create Aliases and, at the same time, associate these Aliases with the Endpoints. The Endpoint Alias function lists the Endpoint Aliases registered with an endpoint. For SIP endpoints, up to five aliases are allowed. All Aliases created within Lotus Sametime Unified Telephony must be unique. This is because these Aliases are used to determine where a received SIP request originated.
Attributes for a SIP Endpoint
The SIP Endpoint Attributes affect how Lotus Sametime Unified Telephony handles the SIP header fields.
EPP (Endpoint Profiles)
The Telephony Control Server Assistant EPP (Endpoint Profile) feature enables the administrator to create and manage an EPP for SIP network servers.
EP (Endpoint) Template
EP (Endpoint) Templates contain a preconfigured set of EP (Endpoint) Attributes and thus allow for easier EP administration.