Troubleshoot Lucent FS 3000 connection problems
		GO

Purpose

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

Invalid FS 3000 host name

If the primary or secondary Call Server host names are incorrect, or if the names are not being properly resolved on the Lucent CM application servers, then both the provisioning interface or the call control interface connections to each affected application server is disconnected.

Incorrect call control interface provisioning on the FS 3000

The host name of each Lucent CM application server must be correctly provisioned in the Lucent FS 3000. The Lucent CM host names provisioned on the Lucent FS 3000 must be resolvable on the Lucent FS 3000.

If this provisioning is incorrect, then the call control (OCI-P or CAP) connection to each affected application server is disconnected.

Connections blocked by firewall

The Lucent CM server connects to the Lucent FS 3000 using the following ports

Port 2220 for OCI-P

Port 2206 for OCI-C

Port 1050 for OSS

Port 2206 for CAP

If a firewall blocks these ports, then the corresponding connections are disconnected.

Call Server Disabled

The Lucent CM Explorer provisioning allows an FS 3000 Call Service to be disabled.

If the FS 3000 Call Service is disabled, both the provisioning interface and the call control interface 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 provisioning interface (OCI-P or OSS) connection to Lucent FS 3000.

If either of these values are incorrect, the provisioning interface is disconnected to all application Servers.

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

		GO
© Lucent Technologies