Collapse AllExpand All

5.5.4. Generation (Example) Previous topic Parent topic Child topic Next topic

  • Check that sufficient memory is configured for the partner table and adjust it if necessary. This can be done via the EXEC command, which configures the standard value on a system-specific basis, or via an ADD command:
    DIS-DIMSU:TYPE=ALL, PARAM=PARTNODE;
    
    EXEC-DIMSU:FEASET=DEFAULT;
    
    ADD-DIMSU:PARTNODE=100;
    
  • Configure own and partner node access codes in the digit analysis.
    Closed numbering scheme:
    ADD-WABE:CD=808902, DAR=NETW, CHECK=NO;
    
    ADD-WABE:CD=808903, DAR=NETW, CHECK=NO;
    
    ADD-WABE:CD=808904, DAR=NETW, CHECK=NO;
    
    Or open numbering scheme:
    ADD-WABE:CD=808901, DAR=OWNNODE;
    
    ADD-WABE:CD=808902, DAR=TIE, CHECK=NO; 
    
    ADD-WABE:CD=808903, DAR=TIE, CHECK=NO; 
    
    ADD-WABE:CD=808904, DAR=TIE, CHECK=NO;
    
    Configure own physical node number and node access code in the central system data:
    CHA-ZAND:TYPE=ALLDATA, PNNO=10-89-100, PNODECD=808901;
    
  • Check whether the feature is activated and, if necessary, adjust the polling times:
    DIS-ZAND:TYPE=ALLDATA3;
    
    CHA-ZAND:TYPE=ALLDATA3, NWTOPTIM=xx;
    
    (xx > 0, corresponds to polling time in seconds)
  • Configuring trunk groups, tie trunk circuits, LCR for open/closed numbering, etc. To this end, the corresponding FUEs, i.e. "Feature Usage Examples" (e.g. LCR, number modification...) must be taken into account. Use the default NWMUXTIM in AMO TDCSU whenever possible. However, in exceptional cases in which, for example, MUX functionality will never be required, use the following:
    CHA-TDCSU:PEN=1-2-25-1, DEV=S2CONN, BCGR=1, NWMUXTIM=0;
    
  • Configure LCR for the physical node access codes; the important factor here is that the dial pattern is entered in the LCR for every partner node access code (check whether it may already have been configured for the path optimization).
    Closed numbering scheme:
    ADD-RICHT:MODE=CD, LRTE=400, CD=40, CPS=0, SVC=SPVH, NAME=TO NODE 400,  
    TGRP1=40, DESTNO=40, DNNO=1-89-400, ROUTOPT=YES, PDNNO=10-89-400;
    
    ADD-LODR:ODR=1, CMD=NPI, NPI=UNKNOWN, TON=UNKNOWN;
    
    ADD-LODR:ODR=1, CMD=ECHO, FIELD=1;
    
    ADD-LODR:ODR=1, CMD=END;
    
    ADD-LODR:ODR=1, INFO="CLOSED NUMBERING UNKNOWN";
     
    ADD-LDAT:LROUTE=400, LSVC=VCE, LVAL=1, TGRP=40, ODR=1, LAUTH=1, 
    CARRIER=9, ZONE=EMPTY, LATTR=NONE;
    
    Or open numbering scheme:
    ADD-RICHT:MODE=LRTENEW, LRTE=40O, NAME=TO NODE 400, TGRP=40, 
    DNNO=1-89-400, ROUTOPT=YES, PDNNO=10-89-400;
     
    ADD-LODR:ODR=10, CMD=ECHO, FIELD=2;
    
    ADD-LODR:ODR=10, CMD=END;
    
    ADD-LODR:ODR=10, INFO="OPEN NUMBERING";
     
    ADD-LDAT:LROUTE=400, LSVC=ALL, LVAL=1, TGRP=40, ODR=10, LAUTH=1, 
    CARRIER=9,  ZONE=EMPTY, LATTR=NONE;
     
    ADD-LDPLN:LDP=808904-T, LROUTE=400, LAUTH=1;
    
  • Initiate manual entries (if necessary) in the partner table:
    ADD-KNTOP:PEN=1-2-25-1, BCGR=1, PTNAC=808904, PTNNO=10-89-400, 
    OVRD=MANONLY;
    
  • Querying the partner table, for example before the MANAUT entry is overwritten by an automatic entry. For partner node 1-2-200, an automatic entry has already been realized:
    DIS-KNTOP;
     
    Output: (Output mask (long format) of the AMO KNTOP
    +-------------------------------------|----------------------------------------+
    
    | OWN NODE                            | PARTNER NODE                           |
    
    +-------------------------------------|----------------------------------------+
    
    | NNO: 10- 89-100 NWTOPTIM:   20 SEC  |                                        |
    
    | NODECD: 808901                      |                                        |
    
    +-------------------------------------|----------------------------------------+
    
    | PEN: 1- 2- 25-  1    BCGR:  1     TGRP:  40                    NWMUXTIM:  10 |
    
    | OVRD:                AUT : X       --> NNO:  10- 89-400                      |
    
    |                                     |  NODECD: 808904                        |
    
    |                                     |  PEN: 1- 2- 79-  1          BCGR:      |
    
    +-------------------------------------|----------------------------------------+
    
    Output mask (long format) of the AMO KNTOP
  • In this example, the original MANAUT entry is overwritten by an automatic entry after a certain time (e.g. because the partner node was upgraded to OpenScape 4000). In this case, the output presented in Figure 15, Output mask of the AMO KNTOP with overwritten MANAUT entry is displayed (differences are highlighted):
    DIS-KNTOP;
     
    Output: (Output mask of the AMO KNTOP with overwritten MANAUT entry)
    +-------------------------------------|----------------------------------------+
    
    | OWN NODE                            | PARTNER NODE                           |
    
    +-------------------------------------|----------------------------------------+
    
    | NNO:  10- 89-100 NWTOPTIM:    20 SEC|                                        |
    
    | NODECD: 808901                      |                                        |
    
    +-------------------------------------|----------------------------------------+
    
    | PEN: 1- 2- 25-  1    BCGR:  1     TGRP:  40                    NWMUXTIM:  10 |
    
    | OVRD: MANONLY        AUT : -       --> NNO:  10- 89-400                      |
    
    |                                     |  NODECD: 808904                        |
    
    |                                     |  PEN: 1- 2- 79-  1           BCGR:     |
    
    | OVRD: MANAUT         AUT : X       --> NNO: 1-  2-300                        |
    
    |                                     |  NODECD: 7018                          |
    
    |                                     |  PEN: 1- 2-109-0            BCGR:      |
    
    +-------------------------------------|----------------------------------------+
    
    Output mask of the AMO KNTOP with overwritten MANAUT entry