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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CLIDs for Calls Abandoned

Status
Not open for further replies.

joynew68

Programmer
Feb 15, 2005
101
CZ
Does anybody know how to extract CLIDs for abandoned calls from call by call stats ?
I am trying to use Excel query or Crystal Reports, but just the event 43 LocalCallArrived gives me CLID, while for event 41 LocalCallAbandoned there are not event data.

Thanks for any tips,

joy

 
Hi,

you're right, the Clid is only in the event 43, and you have no other choice than to link two 'select' :
1/ to find the Callid for all the 41 you're looking for
2/ to link them to obtain the eventdata field from the 43 event
Beware : more than often, the callid is duplicated in the same day, so you'll have to use the timestamp (at least) to return the correct clid.

There was an other way, at least in France, for CCS 1.5->4 named SmartRoute, and which was enabling scripts on Hdx/Odbc, to read/write in tables. (ACVD company actually)
So i usually did use this to log the info in tables, with the ON EVENT part of the script. It was working fine.
I did read that this functionnality should be included in standard CCS 5.x (odbc on hdx).
I've only CCS 4.2 servers actually, so i can not give better answer.

Hope it will help :)

PG
 
Thanks for response PG,

You are right – also our calls have duplicated callIDs. Fortunately they wont just evenings ( about 2 hours) Calls Abandoned. So I think if there is no simple direct way then is necessary to extract events 41,42,43 and then to play a little bit with Excel.
And to wait for upgrade to rel. 5.
Thanks for your time,

joy
 
Hi,

For some customers, we had to make the process automatic, and we did it with Access: knowing the average and max delay before abandon, and the fact that the event 41 (abd) had to be happening after the 43 (call arrived) , we requested, that for each callid having a '41' event :
((timetamp of 41) - (timestamp of 43)) < 2 x max abandon delay (in our case, it was around 3 mn)

Quite simple solution (may be too simple in some cases), but we have less than 0,5% of error in a little more than a year, so it did the job :)

Regards,
PG
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top