H3C XE 200 IP, Руководство по эксплуатации

Страница: 175 / 514

Operation Manual – Location Server Configuration
H3C XE 200/2000 IP PBX
Chapter 4 XE IP PBX Troubleshooting
4-2
Solution 2 : On the gateway, use the gw-id command in GK-Client view to configure
the device identifier consistent with that on the LS.
Solution 3 : On the gateway use the undo ras-on command in GK-Client view to
disable the H.323 gateway, and then use the ras-on command to reactivate it.
5) Cause 5 : The state of the involved H.323 gateway on the LS is disabled.
Diagnosis : Use the display current-configuration command to check if the device
status in LS-GW view is disabled (the two correspond to each other by the gateway
device identifiers).
Solution : In LS-GW view, use the device-status command to set the device status to
forever-up or normal.
6) Cause 6 : The corresponding gateway on the LS has no corresponding call
numbers (the calling number or the called number).
Diagnosis : On the LS, use the display current-configuration command to check for
the corresponding call numbers in LS-GW view: whether the calling number and called
number are configured on the calling and called H.323 gateways respectively.
Solution : In LS-GW view, configure the calling number and called number on the
corresponding gateways.
III. The LS is unreachable from the gatekeeper
1) Cause 1 : No corresponding gatekeeper (corresponded by PS identifier) is
configured on the LS.
Diagnosis : On the LS use the display current-configuration command to check for
the corresponding gatekeeper (corresponded by PS identifier) in LS view.
Solution : On the LS add the corresponding gatekeeper in LS view and assign its PS
identifier.
2) Cause 2 : The configuration of the PS on the LS is not consistent with that on the
PS.
Diagnosis : Use the display current-configuration command to view the
configuration of the gatekeeper in LS view on the LS and in PS view on the PS
respectively, and check for the consistency of heartbeat passwords.
Solution 1 : On the LS, configure the heartbeat password in LS-PS view for the PS,
consistent with those configured on the gatekeeper.
Solution 2 : On the PS, configure the heartbeat password, consistent with those
configured in LS-PS view of the LS.
3) Cause 3 : A remote LS is configured on the gatekeeper, but its IP address or port
number may be incorrect.
Diagnosis : Use the display current-configuration command to view the IP address
and port number of the remote LS in PS view on the gatekeeper and in LS view on the
LS and check for their consistency.