I received a flurry of 5 to 6 CSA105 errors for my CallPilot link 17. During this 30 seconds of interruption my operators received calls destined for CallPilot. As quick as they came they stopped and service continued. Callpilot event log showed no errors. We do have CCMS and CCMA 6.0 along with our CallPilot. Is this something I should be concerned with?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CSA105 17
- Thread starter voip64
- Start date
Firebird Scrambler
Systems Engineer
Will any of these answers help and provide a clue?
CSA 104/CSA 105/CSA 106/CSA 107 MESSAGES FROM CCR AND CCR APPEARS TO BE INTERMITTENTLY DISASSOCIATING FROM THE CDN'S IT CONTROLS. THIS CAN BE CAUSED BY HAVING TOO MANY CALL REGISTERS CONFIGURED ON THE MERIDIAN.
ONE SITE HAD 20000 CONFIGURED. THIS CAUSED THE CCR TO TRY AND ALLOCATE A SIMILAR AMOUNT OF MEMORY WHICH CAUSED A MEMORY AREA CALLED TSMAIN TO GROW TO A LEVEL WHERE CCR STRUGGLED TO FUNCTION.
##############################################################
event browser on symposium & meridian history file shown that the elan had gone down & restarted automaticaly
meridian hist file gave the following
CSA105 16, 17:58:37 15/01/2004
CSA002 16 17:58:37 15/01/2004 6
ELAN007 ELAN 16 host IP=220.0.0.101 disabled, read from socket
fail due to far end disconnect or Ethernet problems
ELAN014 ELAN 16 host IP=220.0.0.101 is enabled
CSA003 16 17:58:41 15/01/2004
CSA105 16, 17:58:41 15/01/2004
CSA104 16, 17:59:03 15/01/2004
after checking the services on the symposium the windows timer server service was set inccorectly to started automatic. reseting the windows time service to stopped manual cured the problem.
This problem can also be a result of any third party time synchronisation software that has been installed on the server. I have recently come across an application called TARDIS which causes the same issue so be aware !
All the best
Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK
If it's working, then leave it alone!.
CSA 104/CSA 105/CSA 106/CSA 107 MESSAGES FROM CCR AND CCR APPEARS TO BE INTERMITTENTLY DISASSOCIATING FROM THE CDN'S IT CONTROLS. THIS CAN BE CAUSED BY HAVING TOO MANY CALL REGISTERS CONFIGURED ON THE MERIDIAN.
ONE SITE HAD 20000 CONFIGURED. THIS CAUSED THE CCR TO TRY AND ALLOCATE A SIMILAR AMOUNT OF MEMORY WHICH CAUSED A MEMORY AREA CALLED TSMAIN TO GROW TO A LEVEL WHERE CCR STRUGGLED TO FUNCTION.
##############################################################
event browser on symposium & meridian history file shown that the elan had gone down & restarted automaticaly
meridian hist file gave the following
CSA105 16, 17:58:37 15/01/2004
CSA002 16 17:58:37 15/01/2004 6
ELAN007 ELAN 16 host IP=220.0.0.101 disabled, read from socket
fail due to far end disconnect or Ethernet problems
ELAN014 ELAN 16 host IP=220.0.0.101 is enabled
CSA003 16 17:58:41 15/01/2004
CSA105 16, 17:58:41 15/01/2004
CSA104 16, 17:59:03 15/01/2004
after checking the services on the symposium the windows timer server service was set inccorectly to started automatic. reseting the windows time service to stopped manual cured the problem.
This problem can also be a result of any third party time synchronisation software that has been installed on the server. I have recently come across an application called TARDIS which causes the same issue so be aware !
All the best
Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK
If it's working, then leave it alone!.
- Status
Similar threads
- Locked
- Question
- Locked
- Question