Collapse AllExpand All

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

Configure the modification table with the AMO GEFE.

Configuration Examples:

  1. Cut off the digits 201 for the CALLING party with node number 1-1-99; seven digits must remain
    CHANGE-GEFE:NMOD,1-1-99,,201,7,CALLING;
    
  2. Cut off the digits 201 for all three parties with node number 1-1-601; five digits must remain. Add the digits 4711 at the front for all three parties with node number 1-1-601.
    CHANGE-GEFE:NMOD,1-1-601,4711,201,5,PAYING&CALLING&CONNECTED;
    
  3. Add the digits 333 at the front for the connected party with node number 1-1-401.
    CHANGE-GEFE:NMOD,1-1-401,333,,5,CONNECTED;
    
  4. Delete the add-on pattern 444 for node number 1-401.
    DEL-GEFE:NMOD,1-1-401,333;
    
  5. Delete the cutoff pattern 333 for node number 1-401.
    DEL-GEFE:NMOD,1-1-401,333;
    
  6. Delete the add-on pattern 4711 and the cutoff pattern 201 for node number 1-401.
    DEL-GEFE:NMOD,1-1-601,4711,201;
    

Messages

  • Error messages from the modification part (patch):
    CDR-NM: NO MEMORY! 
    
    No memory for storing the configuration that was read in.
    CDR-NM: FILE :CGD:NUMBER-MOD-TAB NOT FOUND
    
    No modification table (file) found.
    CDR-NM: GENERAL ERROR!
    
    General error
  • Error messages from AMO GEFE:
    F02: NODE NUMBER MAY NOT BE 0
     F03: LEVEL@ THE NODE NUMBER MAY NOT EXCEED THE VALUE @@@
     F04: LEVEL1 OF NODE NUMBER MAY NOT BE 0
     F05: ???Problems accessing hard disk (e.g., A1H1F or A1H6F)
     F06: The desired entry already exists.
     F07: It is not possible to add more entries because the table 
    is full.
     F08: ONLY ONE DADD IS POSSIBLE FOR SAME NODE NUMBER.
     F09: DREM PATTERN ALREADY DEFINED FOR THIS NODE.
     F10: THE ENTRY CANNOT BE DELETED.
     F11: NO ENTRY FOUND.
     H03: ENRTY HAS DELETED SUCCESFULLY.