Troubleshoot Lucent FS 5000 provisioning problems
		GO

Purpose

This topic describes errors that can occur during provisioning using the Lucent CM Explorer administration client. Errors are provided to the administrator via pop up windows that inform the administrator an operation failed.

Possible causes of errors

Possible causes of provisioning errors are:

Fault in DBGW or WPIF interface to the Lucent FS 5000 (network connectivity)

Incorrect FS 5000 host name, port, account name, or password

DNS resolution issues for WPIF FQDNs

Incorrect dialing package (outgoing dialing rules)

Incorrect feature package feature access code values (inconsistency with FS 5000 feature access code values)

Attempting to use a feature that is not assigned to the Lucent CM user

General troubleshooting steps

Whenever an error displays, the first step is to check the status for the connections.

At the Lucent CM Explorer tree view:

Select the call server (Lucent CM System → Services → Call Server → <call server ID>

Click Details.

If the status does not display CONNECTED, a problem exists. For more information on problem causes, refer to Troubleshoot Lucent FS 5000 connection problems.

If there are no status errors, view the trace log files to get more detailed information about errors.

		GO
© Lucent Technologies