| Connectivity | |||
|
| GO | |
|
The Lucent FS 3000 and the Lucent CM are networked together over TCP/IP. All communication between the Lucent CM and the Lucent FS 3000 is from the Lucent CM Application Node, to one or both of the Lucent FS 3000 Application Server nodes. There should not be a firewall between these two systems since they need to communicate on different ports. The Lucent CM is trusted by the Lucent FS 3000 and should be in the same network.
The Lucent CM can communicate with multiple Lucent FS 3000 call servers. A Lucent FS 3000 call server is added to Lucent CM, by a system administrator using the Lucent CM Explorer client. Since the Lucent FS 3000 provides call services, it is added as a Call Server service.
The following information associated with the Lucent FS 3000 Call Server needs to be specified and is very important:
|
Field |
Description |
|
Call Server Enabled |
Must be checked (or the call server will not try to make connections). |
|
Primary Call Server |
Must be the IP address of the Lucent FS 3000 Primary Application Server. |
|
Secondary Call Server |
Must be the IP address of the Lucent FS 3000 Secondary Application Server. |
|
Call Server ID |
Any string that you find useful in identifying this call server from others. |
|
Account name |
Must be the same one used by the system administrator to logon to the Lucent FS 3000 web interface. |
|
Password Verify Password |
Must be the same one used by the system administrator to logon to the Lucent FS 3000 web interface. |
|
System Phone Domain |
Must be the domain entered when installing the Lucent FS 3000 application server. |
The Lucent CM needs to know the System Phone Domain so that it can create the correct ID for users within the Lucent FS 3000. User ids in the Lucent FS 3000 require a domain name if they are not in the system phone domain, and do not allow a domain if they are in the system phone domain.
When you add users in Lucent CM to a partition, the Lucent CM will compare the partition’s phone domain to this “system phone domain” to see if they are in that domain or not.
To get the system phone domain from a running Lucent FS 3000, enter the following on the FS 3000 Call Server command line interface:
>bwcli |
>login admin |
Password: ****** |
>system |
>domain |
>get |
The result will display the system phone domain. This value must be entered in EXACTLY on this screen.
The call control interface (OCI-C or CAP) is a TCP/IP connection between the Lucent FS 3000 and the Lucent CM to exchange call control and events information . The OCI-C or CAP Status indicates that the Lucent CM has successfully connected to the Lucent FS 3000. To successfully connect you must tell the Lucent FS 3000 that the Lucent CM node can connect to it without logon.
To configure the Lucent FS 3000 to allow Lucent CM to connect, you must enter the following on the Lucent FS 3000 command line interface:
>bwcli |
>login admin |
Password: ****** |
>system |
>networkaccesslist |
>cap |
>add <Lucent CM appl.server IP addr> <Lucent CM name> false |
The false must be entered at the end of the add command, otherwise Lucent CM will not be able to connect.
The provisioning interface (OCI-P or OSS) is a CORBA connection over TCP/IP that provides provisioning support from Lucent CM on behalf of Lucent CM users and administrators. The status is only updated upon issuing of commands (it is not a persistent interface).
If it is not connected, verify that the Account Name and Password parameters are filled out correctly.
|
|
GO | |
|
| © Lucent Technologies | |||