7.3.5.1.3. Changing the HG 3500 Gateway Registration 
The OpenScape 4000 system does not support a direct change of the
gateway registration type from remote to internal gatekeeper, and vice
versa. Furthermore, the AMO ZANDE parameter GATEKPR must not be
changed while a gateway is configured. This may cause major disruptions
during operation!
Since the AMO CGWB has no DELETE branch, the AMO BCSU must be used
to delete the internal HG 3500 configuration data and the extended board
data.
- In a PBX with/without gatekeeper, the HG 3500 gateway(s) must
always be deleted first and then reconfigured. Please note that in such
a case all gateways will be registered either internally (PBX with gatekeeper)
or remotely (PBX without gatekeeper).
- Changing registration of gateway(s) from “internal“ to “remote“:
Delete gateway(s) with AMO GKREG and AMO BCSU, change the GATEKPR parameter to NO and reconfigure the gateway with AMO BFDAT, AMO BCSU and AMO CGWB.- Change registration of gateway(s) from “remote“ to “internal“:
Delete the gateway(s) with AMO GKREG and AMO BCSU, change the GATEKPR parameter to YES and reconfigure the gateway with AMO BFDAT, AMO BCSU, AMO CGWB and AMO GKREG. - In a PBX with gatekeeper, the registration of some special, local gateway(s) can be changed from internal to remote:
-
Delete the gateway data with AMO GKREG and then reconfigure the gateway with AMO CGWB (REGEXTGK=YES) !
- In a PBX with gatekeeper, an additional, local gateway can be configured for remote registration:
-
Configure the gateway with AMO BFDAT, AMO BCSU and AMO CGWB (REGEXTGK=YES)!