Lucent CM in IMS
Previous pageGONext page

Purpose

This topic provides an overview of a Lucent CM in an IMS solution deployment.

Lucent CM management

Lucent CM can be provisioned through the Lucent CM Explorer Administration client or through an OMC-P.

When Lucent CM is deployed in a solution that also includes an OMC-P, Lucent CM services and subscriber related data on the Lucent CM must be provisioned through the OMC-P. By using the OMC-P, data relationships between the Lucent CP and Lucent CM systems are automatically synchronized.

Provisioning through the Lucent CM Explorer administration client is intended only for:

Lucent CM in IMS

Lucent CM can be deployed in an IMS solution. In an IMS solution, the Lucent CM works together with telephony application servers such as the Lucent Feature Server 5000 and Lucent Feature Server 3000, and application servers such as voice mail servers and Lucent Presence Solution servers.

Management systems

In an IMS solution, an OMC-P supports day-to-day provisioning for Lucent CM. The Lucent CM Explorer client is only used for initial provisioning, growth, and for troubleshooting.

By using the OMC-P, provisioning data in the Lucent CM and the Lucent Feature Server 5000 remains synchronized.

View the figure

Other application servers in IMS that interwork with or have interfaces to Lucent CM have their own management systems.

Lucent CM Admin API

Provisioning data is sent to the Lucent CM server via an Application Programming Interface (API).

Both the Lucent CM Explorer client and the OMC-P use the same Admin API.

References

The APIs are available as HTML documents on the Lucent CM server at http://<Lucent_CM_node_name>:8843/doc/ (recommended) or http://<Lucent_CM_node_name>:8888/doc/. Refer to:

Documentation references

For detailed information on Lucent CM provisioning using the OMC-P, refer to OMC-P for the Lucent Communication Manager User Guide, 255-400-421.

Previous page GO Next page
© Lucent Technologies