cls 8.9 safe table is full 2

[nohuhu]

can't find solution myself. customer has 8.9 system with avaya integration, after cls restarts and some time is passed the integration log window starts showing these records:

15/11/2007 16:40:43:203 - Unnamed SafeTab.Put:Table is full.
15/11/2007 16:40:43:203 - CLucentTranslator::AddTransferCallID - Failed adding call ID to safe table

i dimly remember that safe table size is determined by some registry key but can't remember which one exactly. anybody did that already?

 

[nicetechie]

sounds like an issue on ayaya side but you could shut down nice cls. delete all saf files from c:\nicexti\integration the cls will recreate them when it restarts.

 

[nohuhu]

nicetechie,

does it? i tried deleting saf file but it didn't help. i think the problem is within integration module, perhaps because call traffic increased. is it possible to increase safe table size somehow?

 

[richardhr]

Hi

confirm the following entries within the Registry
(back it up prior to making any changes)
[HKEY_LOCAL_MACHINE\SOFTWARE\NICECTI\SYSTEM\CALLSRVR]

ItemTableMaxEntries
LoginTableMaxEntries
SegmentTablesMaxEntries

 

[nohuhu]

richardhr,

all the above keys were set to 2000. i've increased them to 10000, let's see what happens. this problem never appears right after restart but rather over some time. i'll wait.

 

[biglebowski]

Is this on an 8.7 or 8.8 system if so this is a known bug and there is a fix for it. Can't quite remember what it is though as it's been 3.5 years since I worked for NICE, I think it was increasing the RAM in the CLS and fixing the amount of RAM used by SQL (2GB max). It has something to do with the callsvr queue getting overloaded during busy times, used to see it a lot in the city when connected to dealerboard systems (UBS had major problems with this issue)

When I was born I was so suprised I didn't talk for 18 months

 

[nohuhu]

biglebowski,

that is 8.9 system with all the latest service packs applied. as for fixing amount of ram used by mssql, now that's an idea. i remember last time i was trying to find what's going on i've seen that there were too little physical memory available, seemed like something ate it up. maybe it was sql server, i will make sure to fix its appetite.

 

[nohuhu]

richardhr,

increasing these three values to 10000 (from 2000) didn't help. same errors. also i fixed ms sql ram usage to 256 mb max, it also doesn't help.

 

[biglebowski]

I think you have to physically increase the RAM as the saf files are essentially real time calls that use the db and ram to store call info until the call is closed. Increase in call traffic = increase in RAM.

When I was born I was so suprised I didn't talk for 18 months

 

[nohuhu]

biglebowski,

thanks, i understand. do you have any information on amount of ram required?

 

[nohuhu]

biglebowski,

after a little though i've decided not to upgrade existing server because an upgrade to perform is coming and there will be new server with 4 gig of ram. thanks for help anyway.

 

[biglebowski]

wasn't a great deal of help, was looking for my old nice techy bibles but looks like they have been lost in a house move.

When I was born I was so suprised I didn't talk for 18 months