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.
Figure 1. Normalization for SOAP
To support the normalization for SOAP (required in case of adding a preferred device to ODC or supporting the OSC Voice Portal), translation tables and number modification tables need to be set up.
Translation tables can be set up as follows:
Table 1. Prefix Access Codes Table
Table 2. Destination Codes Table
|Numb. Plan ||PAC|| Min || Max ||Digit Position||Insert Digits||Prefix Type||NOA||Destination|
Table 3. Destinations Table
|Numb. Plan||Digits||NOA||Destination Name|
|Numb. Plan||Destination Name||Route||Endpoint||Delete Digits||Insert Digits||NOA|
For the calling party number, the NDAL tables are consulted for creating the calling party number (originating context) for a call to the called party (terminating context).
The input to the number modification tables would then be:
INT/15619231234 (normalized by inserting '+')
SUB/5551111 (requires number definition)
NAT/4085552222 (requires number definition)
INT/554132533333 (normalized by inserting '+')
The number definition rules above will apply as well to normalize national and subscriber numbers to international:
Table 4. Number definition table::
The rules for which number to pass to the number modification's normalization function are to use the input from the destination codes table unless the nature of address is unknown at the destination codes table and is not unknown at the route table. In the above example, the nature of address was International, National or Subscriber at the destination codes table and therefore these numbers were used.
SOAP Normalization Exception
As can be seen from the previous, the normalization for SOAP is handled as soon as the number modification rules are entered correctly throughout the system, with the following exception:
Call to a SIP-Q endpoint where translation returned a nature of address EXTENSION. The extension will be sent back as the normalized number.
Parent topic: Routing and Translation