CCD File Format

[skoom]

Hey Guys,

I was wondering if anyone had any information on pulling apart the CCD files? Sadim has spoke of creating an application to do this though I would like to create my own. I'm more a programmer then anything so I don't fully understand the PBX side of things, though I've learned that I need a few files to get stats out, and they are:

/DHS3dyn/afe/catalog.cfg
/usr2/descript/deliv_id
/DHS3data/afe/parameters.cfg
/DHS3dyn/afe/tc<sitedata>.sta
/DHS3dyn/afe/ev<yymmdd>.sta

If anyone could give me information or point me in a direction that would help me understand how to get data out of these files that would be great. My manager says he had a manual at one stage but is unsure where that has gone, so hopefully someone here is aware of something like that?

Thanks

[zanex]

/DHS3data/afe/parameters.cfg contains advanced parameters for the CCD such as timers, etc - i only have paper notes from the CCD ACSE that explain what they do but you need to know what you are doing as some are inter-depenent - you need to dhs3_init -R the afe after any changes also
/DHS3dyn/afe/catalog.cfg is for all the objects for CCS i have only ever played around with it to get offline CCS working
/usr2/descript/deliv_id is just the version that the PBX is not including patch level

*.sta are the statistics files and you need the ticket analyser or one of the other tools out there to look at them - useful for debugging complex issues or for custom reporting. I dont have the doc handy for the different times that the files are created compiled and deleted as if you want some details you will need to go into the system before midnight for the day in question.

[skoom]

What is the ticket analyser application you mentioned? Where could I get info about this (or other applications that can read these files)?

My aim is to automatically open, pull apart, and load into a database the data in these files.
Currently we import CCS data from 7 different computers, once a day with the most detail being a 15minute interval, and its my understanding you can get much more details right from these files, and if they are updated on a per call basis then much more frequent reporting.

I've asked the telephony team for a copy of these files (I have no access to the switch) so I am just looking for as much info I can get so I can start digging into these files.

How big is the paper documentation you have? I'm from Melbourne so if you have the ability to fax it that would be fantastic. Although I don't think ill need to change anything (just read the statistics) anything extra would be great to understand how everything works.

Thanks

[zanex]

its the alcatel ticket analyser it is a licensed application off the pbx or standalone license depending on how you use it, i dont think alcatel sell it anymore becuase as a customer product it was pretty bad, It provided an automated means to download the sta files but you could do the same with ftp scripting i think it also did some data manipulation but i am not sure as i have only used it for troubleshooting

You can get far more detailed reporting through pushing the files to a DB compared to the excel CCS reports i played with the concept but i never got around to building something decent, i think sadim has something like this working

[skoom]

Yeah he does.

My aim was to do what sadim has done but more specific to my company. Pull these files apart and put them into a MSSQL database. I asked him for information about the files and how to pull data out, though he said he has spent a lot of time on it and would not just hand over information, so I'm searching wherever I can to get anything I can about pulling apart these files.

We currently have a very good web based platform where all our clients can view reports, which we are currently moving towards 15 minute updates and more detailed data, though this is the one place that is restricting us, having Alcatel Pilot reports only updating once a day after we import the CCS files, having to manual add each pilot, and not being able to report on Agent's via switch data just due to the amount of new people we get in each week, it would be too much to maintain 7 switches with every agent and import an excel file for each of them.

I don't see this being an easy task, without having direct access to the switch and the files on it, and so far only coming up with a list of files after 2 weeks searching I've still got a long way to go, though I'm determined and very interested in getting this happening.

[OXE_4400]

Officiall ALU answer is to buy OXE licence CCD CRI interface ( the same use CC TA ) and also CC Ticket Extractor SW from ALU Proffesional Service. CCTE download detail CCD tickets 1 time per day on store through ODBC driver in SQL, Oracle,..
Exist option for few activities per day ( on special request ? ), its mentioned in docs.

[OXE_4400]

OXE keeps compressed day CCD tickets only if exist CRI licence, so its impossible simply to download by ftp without buying licence.

[krzysioD]

Keeps it for 7 days and well, it's documented (i remeber i've sent this docs to someone on this forum in last year, and he has done some import in Python or maybe Perl or Php).

So use google + search maybe it's done already.

[artifex]

Keeps it for 7 days and well, it's documented (i remeber i've sent this docs to someone on this forum in last year, and he has done some import in Python or maybe Perl or Php).

So use google + search maybe it's done already.

I did some google but no luck. If you still have docs for sta, cfg internal structure please send it.