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).
Using Business Groups
Use one business group per customer, because of feature restrictions (group features, name displays, callback...) between business groups. Multiple BGs should only be used in case of a hosted scenario, where independent cus-tomers are hosted at the same Lotus Sametime Unified Telephony system.
In Lotus Sametime Unified Telephony 8.0 Rx, a second BG has to be used for native SIP gateways (does not apply to SIPQ gateways) in case a distinction between internal and external calls (calls from the PSTN) has to be realized. With Lotus Sametime Unified Telephony V 4.0 this behavior has changed. A new endpoint attribute has been introduced (Public/Off-net Traffic) that provides the same effect like the "external BG" in previous versions for incoming and outgoing PSTN calls from this endpoint. This attribute obso-letes the need for an "external" BG.
In case a native SIP gateway is connected to a PBX, where internal and external calls are received, a decision has to be made (with V3.1Rx and legacy system) depending on the requirements from the customer, if the gateway has to be treated as internal or external gateway.
Independent of which number format is used between Lotus Sametime Unified Telephony and gateways, only normalized numbers have to config-ured within the destination code table, so that the Lotus Sametime Unified Telephony knows what it is dealing with.
The official way to implement call restrictions is via the Toll and Call Restriction Service (based on traffic types).
Independent of which number format is used between Lotus Sametime Unified Telephony and gateways, only normalized numbers have to config-ured within the destination code table, so that the Lotus Sametime Unified Telephony knows what it is dealing with. Current "best practice", in case the display number modification feature from the Lotus Sametime Unified Telephony is used, is to send calling and called party in international for-mat from the Lotus Sametime Unified Telephony to gateways and vice versa. If the called party can not be send as international, it can be custom-ized at the route of the destination object. The calling party can be adjusted with the display number modification fea-ture for native SIP if needed. However, for incoming calls it is recommended to adjust the calling party information in the native SIP gateway so it is also in effect for survivability mode.
Provisioning of the '+' sign
When a native SIP gateway sends a "+" sign (NOA = International) in front of the called party in the SIP request line of an incoming invite, the Lotus Sametime Unified Telephony checks first the PAC table for call routing translations.
When a SIPQ gateway sends the called party within a incoming setup message in a explicit format (Nature Of Address defined) the Lotus Sametime Unified Telephony will skip the PAC table for call routing translations.
In this case, translation of the called party will start directly within the destination code table of the numbering plan assigned to the gateway.
Using Numbering Plans
The Private Numbering plan (aka PNP) is used to set up routing rules that are local to the subscriber.
The Global Numbering Plan (aka GNP) is used to set up routing rules that are common to all business groups.
Parent topic: Routing and Translation