6.2.1. Intel® Dialogic SS7 Server Fails to Start
In Windows systems, view the system log using the NT Event Viewer. If there are several error events, locate the one that happened first in time, it is likely to be the one with the more precise description of the failure. Other error events are usually consequences of the first one. The following are some of the more common error events and a description of the action you can take to remedy the error:
- Service Specific Error 0x1001 (4097) - "Error in DataKinetics GCT system"
Check that GCTLOAD was running before you started the Intel® Dialogic system service.
- Service Specific Error 0x2003 (8195) - "No Application Module Ids defined"
Check that you have added the SS7 service(s). In Windows systems, SS7 services are added using the Intel® Dialogic Configuration Manager (DCM). Also, check that you have specified a valid list of comma delimited module IDs to be used by Global Call SS7 applications.
- Service Specific Error 0x2009 (8201) - "Group claims a time slot that is already in use"
Check in your config.txt file that no two circuit groups are defined on the same physical Intel® NetStructure SS7 board trunk (dkB1 or dkB2) or, if there are, that they have non-conflicting CICMask settings (a single time slot cannot be used for both groups.)
Table 7 lists all the errors that can be returned by the SS7 server.
Click here to contact Telecom Support Resources
Copyright 2003, Intel Corporation