Unified CCX stops working after Unified CME is rebuilt after crash

From DocWiki

Revision as of 15:21, 9 April 2010 by Cchetty (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Unified CCX stops working after Unified CME is rebuilt after crash

Problem Summary *You have integrated Unified CME with Unified CCX.
  • You have created the Session Server, Voice Register DN, Voice Register Pool while integrating Unified CCX with Unified CME and everything is up and running.
  • Unified CME crashes for some reason and you bring up Unified CME fresh and perform all necessary configurations.

Note: Unified CCX is intact and has all original configurations (such as triggers/RP, Applications, etc.) retained.

  • In this case, the new Unified CME will not have the Session Server, Voice Register DN, Voice Register Pool configurations and there will be orphan data in Unified CCX.
  • Now when you log in to Unified CCX and try to create a new outbound trigger DN, Outbound Trigger DN creation fails because Unified CCX already has some triggers registered to some device pool and that device pool is not present on the freshly configured Unified CME.
  • It is a problem since any necessary information will neither be available on the Unified CCX Administration page nor it can be found in any logs.
Error Message None.
Possible Cause Unknown.
Recommended Action

In order to create a new Outbound Trigger DN, user has to delete all the Orphan entries [like Triggers/RP] from Unified CCX manually and then the creation of Outbound Trigger DN will happen successfully.

Release Release 7.0(1)
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools