5.6.4. Feature Characteristics 
- Changes in the configuration data made by AMO LWPAR and AMO TDCSU will become only effective on the board after switching off/on the concerned unit. This will cause loading the new configuration data to the board:
- Switch off/on circuits with AMO DSSU: Concerned Parameters in AMO LWPAR are signed as 'C' ('Circuit').
- Switch off/on board with AMO BSSU: Concerned Parameters in AMO LWPAR are signed as 'R' ('Restart the board') or 'B' ('Board'). Also the parameters which can only be changed by AMO TDCSU are listed here within the LWPAR block]
- A maximum of 50 loadware parameter blocks (LWPAR blocks) are available for PBXXX These data can be changed by AMO LWPAR per block.
B-channel negotiation:
- B Channel negotiation is set on the board. The PBXXX will use the channel requested by the OpenScape 4000 or DPNSS/DASS circuit involved. If this is not available due to collision or faults then the call setup is rejected with the appropriate cause .On the DPNSS side the channels are configured as X or Y. The Y channell will back off in the case of call collision.The distant end must have the B channel set to the opposite value as is normall for DPNSS. To the OpenScape 4000 the PBXXX in the case of call collision sends a message with "required circuit not available", the OpenScape 4000 then can select another B channel or not.Please pay attention to the COT parameter BCNE and TDCSU parameter CCHDL for the OpenScape 4000 trunk as these affect the way OpenScape 4000 handles B channel negotiation.
- In this way trunk groups and sub equipped configurations will function correctly on both sides of the PBXXX.The restriction here is that the same channels must be configured on either side e.g. if only DPNSS channels 1-10 are configured for use then OpenScape 4000 (Cornet N/NQ ) channels 1-10 only must be configured.
Reference clock:
- 'Partial-integration-RG' solution: The OpenScape 4000 switch gets the reference clock over the backplane from the separate DIUS2 board and not directly from the board. The separate DIUS2 circuit therefore must not be configured as 'connected with PBXXX'.
- 'Partial-integration-DIUS2' solution: The OpenScape 4000 switch gets the reference clock over the backplane directly from the PBXXX board.
- 'Full-integration'solution: The OpenScape 4000 switch gets the reference clock over the backplane directly from the PBXXX board. In this situation the PBXXX circuit must be configured (via the CDGM tool) to retrieve the clock from the external DPNSS/DASS2 circuit.
- Command interface AMO LWCMD: With the 'Full-integration'
solution the new AMO LWCMD (LoadWare CoMmanD) is available which supports
a command interface between OpenScape 4000 service terminal and PBXXX
board.
With AMO LWCMD service personnel are able to send ASCII-command strings to the PBXXX board loadware and to receive ASCII-strings on the service terminal display. This command interface is developed for PBXXX system specialists (e.g. for debugging , for detailed fault diagnosis and for statistics). It is not service relevant. The AMO LWCMD therefore gets the AMO password class 3 (product specialist).
- AMO LWPAR has a branch, TYPE=CDG this allows the feature of the PBXXX to be configured in the fully integrated solution.
- The CDGM tool is to be used for the partialy integrated solutions.It is also used for upgrading the extender and loadware for partial integration solutions or just the extender software in the fully integrated solution. In all cases it can be used to monitor configuration data and other items such as link status.