Alcatel Unleashed

Hi there!

I've got a response from my local distributor that CCS only see five weeks back in time so I cannot get information about for example the 21st of may just the 22nd of may. Is it right? Is there any solution to break this window or using any other application to make reports beyond this window?

I've seen that /usr4/afe has a lot of older files with sta and cfg extension which might some statistics but I have no information its internal structure. Help on this would be great as well.

Thanks in advance!

You are changing time for report, not from 0:00 till midnight.
CCS use hour statistic in such case, but OXE keeps it only 5 weeks.
Don't change time, only days and You will get statistic up to 1 year old.
BTW, exist parameter insight OXE which manage 5 weeks, I guess its possible to change to some other value, but I didnt tested it, maybe some others tried it.

OXE_4400 wrote:You are changing time for report, not from 0:00 till midnight.
CCS use hour statistic in such case, but OXE keeps it only 5 weeks.
Don't change time, only days and You will get statistic up to 1 year old.
BTW, exist parameter insight OXE which manage 5 weeks, I guess its possible to change to some other value, but I didnt tested it, maybe some others tried it.

Thanks for your post!

Unfortunately I need hourly statistics so daily statistics is not good for me even it is exist for a year. Guy at distributor said that there is not enough resource for storing files longer. Actually my storage stat (dh -m) is:
I think it is very far from not enough resource as I have no disk free space below 787 megabytes.

I think some application clean up the /usr4/afe folder probably every night. I would like to know is that application has any parameters instead of using 5 weeks time window.

Hi. I recommend you to download statistics with CCS to a PC. Generates all the statistics you need automatically and save them. Regards.

tincho.rn wrote:Hi. I recommend you to download statistics with CCS to a PC. Generates all the statistics you need automatically and save them. Regards.

Thanks your hint!

I do not like how CCS save statistics. It is only saves the existing and predefined statistics and not the raw data. So if I ever need a new view of my records I cannot make any new Excel table for them. With access to raw data I am able to make any statistics later.

And for strange reason when I run CCS it says that I did not generate backup on the last three days and if I say yes CCS save only the last day not the last 3 or more days (since last backup). So I need rerun automatic backup on all days and I cannot save those fancy XLSs with a batch-like manner.

It's explained (well at least tries to be good explanation) in CCS help file.

but here as i do it:
every night i do automatic ftp all of afe files from oxe to external PC with (free FileZilla FTP server) crontab.

to use it you need to rename files to *.tmp, copy them to OXE and use CCS to do reports.

as for keeping stats for longer time: there is maximum software limit, and as i remember it was 5 weeks.

Good answer from vendor should be like: invest into CRI license and do customized and detailed stats.

Good reply from customer:
"So I expend like $300,000 on this solution and it can't give me a decent report? And now you ask me to buy more stuff? (/&$#"%&/%!!!"

Ah, my memory fails: file named parameters.cfg in DHS3dyn/afe

search for line staring with: period1
change 5 to 15
description: 1 .. 15 : Statistic counters are stored during 1 to 15 weeks

btw: you need full restart (not a bascul) to do it... and do it on both cpus.

krzysioD wrote:Ah, my memory fails: file named parameters.cfg in DHS3dyn/afe

search for line staring with: period1
change 5 to 15
description: 1 .. 15 : Statistic counters are stored during 1 to 15 weeks

btw: you need full restart (not a bascul) to do it... and do it on both cpus.

i try to search it and found parameters.cfg is in /usr3/afe , when i use "vi" command and see the list :

ACD VERSION
release : 8
quarters_stat_timing 1
weeks_period1 5
months_period2 12
batch-hour 1
histo-pilot 5 15 30 60
histo-team 10 30 60 120
talking_threshold 2
real_time_timing 3
csta_or_local_date 0
nb_max_kbytes_fstat 800000
nb_max_kbytes_tmp 100000
nb_max_kbytes_ftick 90000
QS_Level 80
QS_ResponseThreshold 10
TalkingDurationMax 120
TalkingDurationMin 3
WrapUpDuration 10
Efficiency 90
WaitingDuration 15
RingingDuration 15
NoResponseNb 10
WithdrawalDuration 30
PrivTalkDuration 10
PrivTalkDuration 10
BlockIvr 0
DecrWaitingTime 1
Audit_on 1
TempoPiTicketRedir 1800
TempoPiTicketBlocked 1800
IvrRefOrDirNumber 1
ExceptPrimCalendarOn 1
ExceptSecCalendarOn 1
kill_by_watch_dog 1
rcp_twincpu_mode 1
monitor_poste_agent 0
QS_level_is_global 0
POS_barom_duration 15
ETPaveragedOnPeriod 0
ETPincludeWithdraw 0
Apmin 0
max_memsize 5000
serv_ccs_on_dhs 1
TokenTimeOut 48
RealTim_MinAgent 3
WichPasswdForStats 0
asm_on_dhs 0
LogonStatLRUSize 7
asm_wants_rt_agent 0

other question is .... is it ok if we edit weeks_period1 more than 15 weeks?

cavagnaro wrote:Good reply from customer:
"So I expend like $300,000 on this solution and it can't give me a decent report? And now you ask me to buy more stuff? (/&$#"%&/%!!!"

i received good answer too.... " wiht avaya we can do.. bla..bla...bla....$#%^@$@#^#"