| Troubleshoot Lucent FS 3000 provisioning problems | |||
|
| GO | |
|
This topic describes errors that may 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.
Common causes of provisioning errors are:
Fault in the provisioning interface or the call control interface to the Lucent FS 3000
Incorrect domain package information
Incorrect dialing package (outgoing dialing rules)
Attempting to add or modify a service that is not authorized for a group
Attempting to add or modify a service that is not assigned to the Lucent CM user
Internal FS 3000 call server fault.
User services are assigned to users by the Lucent CM system. The only responsibility at the Lucent FS 3000 is to make sure that ALL user services are available to be assigned.
If auto provisioning of the Lucent FS 3000 is enabled, all user provisioning and service manipulation must be performed using the Lucent CM Explorer administration client.
If user services are modified directly at the Lucent FS 3000, a mismatch between the Lucent CM call server feature packages and FS 3000 data can occur. A mismatch can result in undesirable results.
Whenever an error displays, the first step is to check the status for the provisioning interface and the call control interface to the call server.
At the Lucent CM Explorer tree view:
Select the call server (Lucent CM System → Services → Call Server → <call server ID>
Click Details on the FS 3000 tab
If the OCI-C Status and OCI-P Status or CAP Status and OSS Status does not display CONNECTED, a problem exists. For more information on problem causes, refer to Troubleshoot Lucent FS 3000 connection problems.
If there are no errors for the provisioning interface or the call control interface, view the trace log files to get more detailed information about errors.
|
|
GO | |
|
| © Lucent Technologies | |||