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

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

Operation Manual – Location Server Configuration
H3C XE 200/2000 IP PBX
Chapter 4 XE IP PBX Troubleshooting
4-4
2) Cause 2 : The LS is not started.
Diagnosis : On the LS use the display current-configuration command to check if
the LS is started in LS view.
Solution : On the LS, run the start command in LS view.
3) Cause 3 : No corresponding UA is configured on the LS.
Diagnosis : On the LS use the display current-configuration command to check if
the corresponding UA exists in LS view (the two correspond to each other by the
gateway device identifiers).
Solution : In LS view, add the corresponding UA, and configure the corresponding call
numbers.
4) Cause 4 : The device status of the UA on the LS is disabled.
Diagnosis : On the LS 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.
5) Cause 5 : The device status of the corresponding UA on the LS is normal, but the
registration status is offline.
Diagnosis : On the LS use the display location-server gateway all command to
check if the registration status of the corresponding gateway (specified by the device
identifier) is offline.
Solution : Configure correctly on the UA to start the dynamic registration of the gateway,
making the registration status of the corresponding gateway online.
6) Cause 6 : The corresponding UA on the LS has no corresponding call numbers
(calling number and 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 corresponding calling
number and called number are configured on the calling and called UAs, respectively.
Solution : In LS-GW view, configure the corresponding calling number and called
number.
IV. LS is unreachable from the proxy server
1) Cause 1 : No corresponding proxy server is configured on the LS (corresponded
by device identifiers).
Diagnosis : On the LS, use the display current-configuration command to check for
the corresponding proxy server in LS view (the two correspond to each other by device
identifiers).