If I can solve this I will be a hero (or something).

Monday Morning
Tuesday Morning
Thursday Afternoon

The same problem occured. When a leader tried to change the skillsets for their agent (either adding, removing or prioritizing) they get the error "Can not change skillset". There seems to be no catalyst to this and no solution. By the time I truly start investigating or escalating it seems to fix itself and they can adjust skillsets again. It lasts anywhere from 45minutes to 2-3 hours. Everything else still works fine*.

Our vendor informed us it could be "noise" on the line but I find that highly dubious.

*On Monday there were a couple more symptoms, agents were not able to log into Agent Desktop Display and agents already logged into ADD were getting "SKILLSET CONTROL O" popups. Those symptoms did not occur on the other days.

Anyone experience anything like this or can anyone offer me any insight into what could be causing this? I am at a loss.

This is starting to happen daily, nearly hourly and we still have no idea of the solution.

I've also noticed we can't access the "configuration" screen in Symposium when this is happening.

Very bad indeed.

This has all the symptoms of the Symposium Server cutting out services to protect the core call processing.

When the processor gets busy it is programmed to cut non essential tasks to protect the core process of serving calls.

Ultimately this leads to the intelligent call routing failing in favour of default routing and finally the server gives up and falls over.

When these problems are occuring you need to look at or ask your Nortel support to look at the processor utilisation to see how high it is and what else is going on at those times.

You've not introduced any new software recently have you, something that may be interrogating the server?

Good luck

Appreciate any insight you can offer, there were some patches late last year, but the System worked fine for several weeks after that with no issues. I'll get Nortel to look into what you mentioned.

Justin,

Check where it's writing it's log files.

Also. Is it caching them and not overwriting?

That *might* account for the gradual
degradation in service over time as the disk fills up.

HTH

DaveA

Well we couldn't figure out what was causing the problem so we rebooted the SCCS server and it fixed itself.

Aaah - the main tool in any good IT professional's toolkit - Shutdown and Restart.

Did you remove the plug as well LOL.