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.
The basic access code routing concept is used for Call Pickup network routing and operations. The cPickInfo operation received at the calling party switch triggers PR in order to optimize signalling and/or media paths through the network.
The former concept of "Node ID" routing in 8k has been referred to as "access code routing" using source-BG access code
Routing outgoing calls
For outgoing calls, Destination Access codes (unique network-wide) are used for routing a CPU call (call-related call pickup or non-call-related CISCs) to the appropriate network entity/node.
This type of access code routing via Translation (i.e., local digit analysis) facilitates an optimal routing mechanism for the network-wide CPU group service (and optionally PR). Access codes are transmitted in the CorNet-NQ Group CPU operations and must be provisioned by the craft in the appropriate XLA table(s) in the BG.
Routing an outgoing call via this mechanism requires the called number to be a Destination Access codes (unique network-wide).
Routing incoming calls
Tandeming or terminating an incoming call via this mechanism requires treating the called number as a Source-BG ("own") access code (unique network-wide).
This routing is called "Node ID routing" in terms. Each source-BG access code appears in remote switch's translation table(s) as Destination Access codes for routing purposes.
For incoming calls, a (one) Source-BG ("own") access code (unique network-wide) value is assignable to each BG.
The above routing mechanism is facilitated by sending/receiving a CPU-related message/method with a:
The above applies to CPU CISCs (Call Independent Signalling Connection) and the CPU picking up call to a remote called member. It does not apply to the calling party to the called group member call.
The only two services to employ this routing mechanism are:
SIPQ Network-wide call pickup
SIPQ Network-wide call pickup
Since release 4.0R1 of Lotus Sametime Unified Telephony it is possible to configure Call Pickup Groups whose members are located at different Lotus Sametime Unified Telephony and nodes, i.e. a CPG (Call Pickup Group) may span across the SIP-Q network.
Each local call pickup group is capable of adding a list of associated remote CPGs located elsewhere in and/or Lotus Sametime Unified Telephony private SIP-Q network.
The network-wide CPG feature relies on a feature activation and routing mechanism that is based on network-wide unique Access Codes being assigned to the involved Lotus Sametime Unified Telephony Business Groups and nodes. For a this Access Code corresponds to its Node ID.
Path Replacement access code routing
PR supports the access code routing mechanism after a transfer when the system parameter "PR-node-ID-routing" is set "on".
The PRpropose rerouting field is be the source-BG access code assigned to this BG. An incoming called party number is matched to the source-BG access code in order to identify whether the call setup for PR treatment should terminate here or be tandemed. LM2853-2 PR shall default to access code routing mechanism after a CPU PR trigger is received.
Since 4k is the only PINX known to use node ID routing, an EP attribute indicates whether PR access code routing is applicable to this end point.
When the attribute is set on, PR employs the following source-BG access code mechanism:
The PR service supports the capability to perform PR based on access code routing (following transfer or pickup) based on the PR-access-code -routing parameter value for on:
Parent topic: Routing and Translation
When PR service is started to propose PR for a call, it shall send this BG's assigned source-BG access code as the reroutingNumber (in QSIG prPropose) instead of sending the private network number. This results in the Called Party Number of the new replacement path SETUP message to be an access code for routing to this switch. The CallIdentity shall be the only way to identify the proper old path with the new replacement path.
When the PR service is started on receipt of an incoming Uce_Setup message for the replacement call, when the called party number was a match with this BG's source-BG access code in XLA. Then retrieve the associated data for this PR (based on the CallIdentity match) and process as usual.If the called party number (i.e., access code) does not match the source-BG access code, then this switch is a tandem switch, so UCE shall route this call according to the assigned route.
XLA (digit translation and routing) tables
Source-BG Access Code
The "own" access code for a particular BG. Used for routing and interworks with 4k "node Ids". Unique network-wide.
How to Create the Source-BG Access Code (PAC) for Access Code Routing
A source-BG access code must be added at the BG-level with other BG-related parameters. The value allows Access Code Routing to a particular 8k and BG. The value must be unique network-wide (but not verified network-wide).
How to Assign a BG Access Code to a BG (Business Group)