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.
Public SIP Subscribers
Lotus Sametime Unified Voice supports 2 types of public SIP subscribers (External DN flag is checked):
With country code: the SIP subscriber is already normalized and the GNF number is presented by inserting a '+' before the Home Directory Number. There are no display number modification rules required in this case.
Without country code: the SIP subscriber is normalized by looking up a match for the subscriber number in the number definition table. When found, a '+' and the country code are added in front of the Home Directory Number.
Private SIP Subscriber
Lotus Sametime Unified Telephony supports 3 types of private SIP subscribers:
With L2 code
With L1 code (without L2 code)
With L0 code (without L1 code or L0 code)
The SIP subscriber is normalized by looking up a match for the home directory number in the number definition table. When a match is found, the contents of the definition entry may be used to normalize the number if necessary (this would be very unusal).
Numbers received from SIP are first subjected to the Number Normalization table. Normally all normalization rules should be found there. However if the normalization rule is not found, normalization can still occur using the number prefixes table (if the received number format is unknown) and/or the number definition table:
Numbers received from SIP-Q endpoints should already be normalized. However, just like with numbers received from SIP endpoints, these numbers are subjected to the Number Normalization table and if necessary the Number Prefixes and/or the Number Definitions table.
Parent topic: Routing and Translation