Normalized numbers are created for CSTA and also for requests that come in on the SOAP interface. An administrator can force sending normalized numbers on the SIP network interface by setting the Send Uri in Telephone Subscriber Format
attribute on the SIP endpoint representing the gateway or media server to which normalized numbers need to be sent.
Creating a Normalized Number - General
CSTA always tries to send GNF numbers or fully qualified private numbers to the CSTA applications. A GNF number is a '+' followed by a fully qualified public number.
There are mutilple steps to creating a normalized number:
- First the Type of Number of the number to be normalized is determined.
- If the Type of Number remains unknown, the normalized form of the number cannot be obtained.
- If the Type of Number is International or L2, the number is successfully normalized.
- If the Type of Number is National or Subscriber, the Definitions table entry that matches the number is used to normalize the number to an International number. If no Definitions table entry is found or the entry cannot be used to create an International number, the normalized form of the number cannot be obtained.
- If the Type of Number is L1 or L0, the Definitions table entry that matches the number is used to normalize the number to an L2, L1 or L0 number. If no Definitions table entry is found, the number is assumed to have the normalized form.
- The GNF number is then obtained by pre-pending a '+' in front of an international (public) number.
Creating a Normalized Number - for SOAP
SOAP may also be used to request the normalized number of a dialed string. This interface is used by Telephony Application Server when one creates a preferred device on the Lotus Sametime Desktop Client, but it is also used in some other Lotus Sametime UC related applications such as the voice portal.
In order to do a successful number normalization of a dialed string, the SOAP interface needs to provide all input information. As this interface is mainly used by the Lotus Sametime UC, it was chosen to use the subscriber number (Home Directory Number) of the requesting party to find the private numbering plan in which the dialed string needs to be translated.
In the case of creating a preferred device for the Lotus Sametime Desktop Client, this is the subscriber number of the Lotus Sametime Desktop Client.
Creating the normalized number for SOAP involves 3 basic steps:
Parent topic: Display Number Modification
- Obtain the private numbering plan of the requesting party. The requesting party must be a subscriber on Lotus Sametime Unified Telephony to which the SOAP request for dialed number normalization is made. The subscriber is looked up and the subscriber's numbering plan is obtained. A normalized number can only be returned if the requestor is a subscriber configured on Lotus Sametime Unified Telephony.
- Ensure that the dialed string is a 'dialable number' by translating the dialed string. A normalized number can only be returned if translation of the dialed string is successful and leads to another subscriber or an endpoint (gateway, media server, etc.). If the translation result leads to a subscriber, the subscriber's number will be used. The type of number will be one of:
If the translation result leads to an endpoint, the number and type of number used for the normalization depend on the provisioned translation tables (Destination Codes and Routes table) as shown in the following table:
Table 1. Obtain Number and Type of Number for endpoints
|Translation Result||1) Modified digits and Nature of Address as input to the destination codes table||2) Modified digits and Nature of Address after the Routes table (only provided if there are insertions or deletions)||Use|
|Subscriber||International / National / L2 / L1 / L0||N/A||1)|
|ENDPOINT||UNKNOWN||UNKNOWN / Undefined||1)|
|International / National / Subscriber / L2 / L1 / L0 / PNP Extension||2)|
|International / National / Subscriber / L2 / L1 / L0 / PNP Extension||Don't care||1)|
- Normalize the number using the translation result. For this normalization, the private numbering plan of the translation result is used rather than the private numbering plan of the requesting party.
If the translation result is PNP Extension, step 3 is skipped and the extension is returned as the normalized number.