Troubleshoot Lucent FS 5000 connection problems
		GO

Purpose

This topic describes common causes that create connection problems to the Lucent FS 5000 and provides hints on how to solve the connection problems. Each Call Server service requires to connections to each Lucent CM application server.

Invalid FS 5000 host name

If the host names of the Call Server are incorrect, or if the names are not being properly resolved on the Lucent CM application servers, then the connections to each affected application server disconnect.

Connections blocked by firewall

The Lucent CM server connects via WPIF to the Lucent FS 5000 on port 4060, the DB on port 7856.

If a firewall blocks the ports, the corresponding connections disconnect.

Call Server disabled

The Lucent CM Explorer provisioning allows an FS 5000 Call Server to be disabled.

If FS 5000 Call Server is disabled, both the connections to each Lucent CM application server are disconnected.

Invalid authentication credentials

The Lucent CM Explorer provisioning requires the specification of an Account Name and Password for the connection to Lucent FS 5000.

If either of these values are incorrect, the Lucent CM application servers are disconnected from the FS 5000.

To test the validity of these values, attempt to use them to log into the Command Line Interface at the Lucent FS 5000.

Incorrect FQDN resolving

DNS must be able to resolve the FS 5000 WPIF FQDNs for the WPIF connections to work. The Lucent CM reads the WPIF FQDNs from the FS5000 DBGW interface and then tries to connect to those FQDNs.

If DNS cannot resolve the FQDNs, the connection fails.

		GO
© Lucent Technologies