Cisco Automated Administrator (AAS) for Symposium: AAS - Error reports that SEIEventService does not start

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
 

Latest revision as of 23:53, 12 March 2010

AAS - Error reports that SEIEventService does not start

Problem Summary Error reports that SEIEventService does not start.
Error Message None
Possible Cause Incorrect configuration.
Recommended Action Ensure that the user name and password for the Symposium installation in the Windows registry are correct. (Default is “nortel” and “nortel” for SEI.)

Base: HKEY_LOCAL_MACHINE/SOFTWARE/Cisco Systems, Inc./ICM/<ICM instance>/PG<XX>/PG/CurrentVersion/AASS/aas<X>/AASData/Config

Note: PG<XX> represents the PG name. aas<X> represents the AAS name.

Values: AASSEIUserName, AASSEIUserPassword

Also, verify that the Symposium server can be accessed through the IP and port in the Windows registry: Base: HKEY_LOCAL_MACHINE/SOFTWARE/Cisco Systems, Inc./ICM/<ICM instance>/PG<XX>/PG/CurrentVersion/AASS/aas<X>/AASData/Config.

Note: PG<XX> represents the PG name. aas<X> represents the AAS name.

You can accomplish this by:

  • Pinging the IP address/host of the Symposium server.
  • Telneting to the IP address/host and Symposium port to see if you can connect.
  • Values: AASSEINamingServiceIP, AASSEINamingServicePort

If you are unable to telnet to the IP address/host and the Naming Service Port, on the Symposium server:

  1. Check if the TAO Naming Service is running on the Symposium
  2. Run NamingViewer in the folder: d:/Nortel/TAO13/bin
  • “Default” displays.
  • Click Root > NortelNetworks > SymposiumCallCenterServer.
  • A list displays, where two of the items are SEI and your Site Name for Symposium.
  • Click your Site Name to see another list that also includes SEI.
  • Double-click SEI (under the Site Name) and some information displays that contains the CORBA IOR and the IP address and port of the SEI service.
  • If you do not see the IOR in the NamingViewer, make the following change, restart the Symposium Services, and try running the NamingViewer:
    On the Symposium server, add an entry to the hosts file for the Symposium host with the CLAN IP address before the entry for the Symposium host with the 127.0.0.1 IP address.
    For example, here is the original file:
    127.0.0.1 localhost #
    127.0.0.1 MYMACHINENAME # Map computer name to local host
    Here is the file after adding an example CLAN IP address:
    127.0.0.1 localhost #
    192.168.252.40 MYMACHINENAME # New Entry
    127.0.0.1 MYMACHINENAME # Map computer name to local host
Release Release 7.5(1) and 8.0
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools