DCM start Failure

Hi,



I am using SPCI4 card with SP6.0 update 71.

I am starting septel and after i am trying to start DCM but i am getting start failure error .

I decoded the DlgcS7.log file and getting this error:



ERROR: Check if gctload is running! DkMsgDispatcher::Init() failed: Status = 3

Server::Init failed: 0x5007



system.cfg,config.cfg,gcss7.cfg and DlgcS7.txt are above..

Can you help me?:))

Which license button do u have. give me the details of MTP3 and ISUP modules licenses

We are using ISUP buttons.I dîd not understand what do you mean by details?

Hi,



In the gcss7.cfg file you have Service.GCTLOAD_Control = "No"



With this setting the DCM will not attempt to start GCTLOAD (signalling message environment) and GCTLOAD would be manually started.



DCM will only start GCTLOAD if Service.GCTLOAD_Control is set to “Yes” in the gcss7.cfg file.



Paul

Hi Paul,



Thank you for your help.But i am making gctload manually after that i am starting DCM and getting error.

After your message I made what you said to me and get error again.

New DlgcS7.txt file is attached below..

This time i am getting :



16:25 07.031 DkMsgDispatcher::Init()

16:25 07.031 DkMsgDispatcher::ThreadRun()

16:25 07.031 DkMsgDispatcher::ThreadRun() entering message loop

16:25 07.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 08.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 09.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 10.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 11.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 12.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 13.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 14.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 15.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 16.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 17.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 18.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 19.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 20.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 21.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 22.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 22.031 WARNING: DkRuntime::WaitForReady() timeout.

Hint: check septel\system.txt if there is something like FORK_PROCESS .\s7_mgt.exe -i0x4d

16:25 22.031 CardController::InitA()

16:25 22.031 CardController::ResetSWX(0)

16:25 22.031 --> hex t=7e00 id=0000 dst=10 s=00 e=0000 rr=2000 p:

16:25 22.812 ERROR: CardController::WaitForResponse() timeout

16:25 22.812 Server::Init failed: 0x500a

16:25 22.812 Server::Deinit()

16:25 22.812 ReleaseTimeSlotRange()

16:25 22.812 --> hex t=9cc9 id=0000 dst=4d s=00 p:

16:25 22.812 ERROR: DkSMsg::Send() GCT_send failed 1

16:25 23.031 ERROR: DkMsgDispatcher::ThreadRun() received NULL message

16:25 23.531 DkMsgDispatcher::ThreadRun() leaving message loop (2)

16:25 26.531 Server::Deinit() complete, shutdown the log

New DlcgS7 file is attached below..

My knowledge of GC is limited.



You may want to consider using the GC forum;



http://www.dialogic.com/forums/forums/forum-view.asp?fid=11



I notice in the system.txt that you do not have a Local process declared for GC (0x4d). This would prevent communication between GC and the signalling stack.



Paul

Use the following system.txt

If you configure GC/SS7 to take care of starting GCTLOAD automatically, then you need to start s7_mgt with a special command line parm in your system.txt:



FORK_PROCESS .\s7_mgt.exe -i0x4d



Hint: check septel\system.txt if there is something like FORK_PROCESS .\s7_mgt.exe -i0x4d

Hi

How was that problem fixed  , i am facing the same issue

 

Regards