5.36.3.3.2. Digit Analysis and Node Definitions 
Before we come to the configuration of digit analysis and node definitions,
a few explanations are needed on the relationships between the AMOs WABE
and KNDEF:
Outgoing dialing is performed with the station's DPLN (AMO SBCSU).
When DAR OWNNODE is reached, dialing with the DPLN of
the destination node (AMO KNDEF) continues from this point.
Here is an example as an aid to understanding:
Let's consider station (95)1007 from virtual node 1-1-5 and station (98)10 from virtual
node
1-1-8.
Virtual node 1-1-5 uses four-digit numbering, such as 1007.
Virtual node 1-1-8 uses two-digit numbering, such as 10.
If station (95)1007 wants to call station (98)10, then the dial plan must be adjusted
to the
destination node after the node code is dialed.
Station number "10" does not produce a result in the DPLN of the station (95)1007.
The outcome is identical if station (98)10 calls station (95)1007.
Station number "10" produces a result in the DPLN associated with station (98)10,
but dialing
is incomplete in virtual node 1-1-5.
For this reason, subsequent dialing is evaluated with the DPLN of the destination
node when
DAR OWNNODE is reached.
The parameter ADPLN (permitted DPLN) defines which DPLN groups may be assigned to the
members of a virtual node.
If the parameter ADPLN associated with a virtual node is assigned multiple DPLN groups,
ensure
that the node-dependent station numbers (such as STN, ATNDDID, ATNDIND, ATND, etc.)
are
identically configured.
The DPLN is now configured following the generation sequence. The following should
be noted
here:
- The DAR OWNNODE should always be configured independently of the DPLN.
- In contrast to earlier versions, the DAR STN can now be configured dependent on the DPLN. In the case of a VNR system, we recommend generating the DAR=STN dependent on the DPLN to avoid problems with future expansions.
First the physical node code that is entered in the AMO ZAND as PNODECD
is configured as DAR=OWNNODE.
The physical node code must be unique network-wide, and should not
correspond to any virtual node code as virtual nodes can be distributed
over several physical nodes.
As the user does not select the physical node code, station numbers
are frequently entered with * to avoid limiting the numbering
scheme:
ADD-WABE:CD=95,DAR=OWNNODE,CHECK=N;
DAR=OWNNODE should also be configured for all account codes in the virtual nodes:
ADD-WABE:CD=95,DAR=OWNNODE,CHECK=N; ADD-WABE:CD=96,DAR=OWNNODE,CHECK=N; ADD-WABE:CD=97,DAR=OWNNODE,CHECK=N; ADD-WABE:CD=98,DAR=OWNNODE,CHECK=N;
The station numbers are now configured on the basis of DPLN groups. To avoid running
out of
memory in the AMO DIMSU, parameters DPLNGR/DPLNCD, entire station number blocks are
prepared
where possible:
ADD-WABE:CD=10&&29,DPLN=0,DAR=STN; ADD-WABE:CD=100&&299,DPLN=1,DAR=STN; ADD-WABE:CD=1000&&1999,DPLN=2,DAR=STN;
Next, the physical node number and node code are entered in the AMO ZAND:
CHANGE-ZAND:TYPE=ALLDATA,...,PNNO=10-1-5,PNODECD=**95;
The virtual nodes are now configured with the AMO KNDEF. This involves assigning the
unique
ISDN station number (E.164 station number) and the unique node code:
ADD-KNDEF:NNO=1-1-5,TYPE=OWN, ISDNCC=49,ISDNAC=89, ISDNLC=7221,ISDNSK=4, NODECD=95,NODECDSK=2,DPLN=2,ADPLN=2; ADD-KNDEF:NNO=1-1-6,TYPE=OWN, ISDNCC=49,ISDNAC=30, ISDNLC=38645,ISDNSK=5,NODECD=96,NODECDSK=2,DPLN=1,ADPLN=1; ADD-KNDEF:NNO=1-1-7,TYPE=OWN, ISDNCC=49,ISDNAC=631,ISDNLC=7974, ISDNSK=4, NODECD=97,NODECDSK=2,DPLN=1,ADPLN=1; ADD-KNDEF:NNO=1-1-8,TYPE=OWN, ISDNCC=49,ISDNAC=89,ISDNLC=636123, ISDNSK=6, NODECD=98,NODECDSK=2,DPLN=0,ADPLN=0;