5.6.5.4. PBXXX Full Integration 
This product configuration is characterized by the following:
- The PBXXX takes power from the backplane.
- The PBXXX can receive a reference clock from the OpenScape 4000 backplane, or supply a reference clock to the OpenScape 4000 backplane.
- The PBXXX emulates the DIU-S2.
- The PBXXX loadware resides on the OpenScape 4000 and is loaded on to the card automatically on startup if loadware in the OpenScape 4000 is found to be different to that on the board
- Configuration for the PBXXX is done using AMOs on the OpenScape 4000. PBXXX configuration is stored on the OpenScape 4000 database.
- Limited PBXXX debugging can also be done by AMO.
- The option of using a separate CDGM tool for PBXXX debug/ tracing is still available.
- Administation and maintenance of the PBXXX can either be done by AMO or by using the CDGM tool. But can not be done by AMO and the CDGM tool in parallel or at the same time. Within the PBXXX loadware it is configurable (via execute commands sent with AMO or via CDGM) which internal errors are sent to the OpenScape 4000
In the fully integrated option, the PBXXX board will receive the configuration
data from OpenScape 4000 directly on start-up. During start-up, each
equipped circuit on the PBXXX will receive from OpenScape 4000 a message
containing a datablock with configuration parameters. These PBXXX specific
parameters are configured by OpenScape 4000 using different AMO commands
(AMO LWPAR/AMO TDCSU).
Changing configuration data on the PBXXX board via the V.24 interface
while the board is in the 'full integration configuration'
leads to inconsistent OpenScape 4000 Database for PBXXX. Therefore this
manipulation is not allowed in normal operation but only for diagnostics
purposes (executed by system specialists).
Features:
- PBXXX will always synchronise on the PCM clock from the OpenScape 4000 backplane. Additionally, the PBXXX will be able to provide OpenScape 4000 with the clock sources derived from the incoming data stream from the DPNSS1 or DASS links. These clock sources can be switched on and off under OpenScape 4000 control by means of DIU-S2 backplane messages.
- Between B channels on the Network side (DPNSS/DASS) a fixed relationship exists (see B channel negotiation). Timeslot connections are made on a per call basis, however no physical connection will be established until OpenScape 4000 assigns a timeslots on the backplane for the selected B-channel.
- Circuit 0 or 1 appear in the REFTA table as possible clock sources.