Author Topic: Duration Correction  (Read 11150 times)

vimeni

  • Newbie
  • *
  • Offline Offline
  • Posts: 1
    • View Profile
Duration Correction
« on: December 09, 2004, 04:14:50 PM »
Please could you help me with filtering calls (within a report) which are of duration of more than 10 seconds.

I have imported the back data (SMDRs) using import facility. In the import screen there is a field called "Duration correction". Do I have to fillin 10 in this field (instead of the default 0) in order to import calls of more than 10 seconds. The reason being that there are a lot of junk calls, where a user has dialled first few digits and then hung up.

Though this is not relevant to this topic, I have another issue, where your help would be great. I am in the UK. In the regions the NDD codes are for USA only. If I have to insert the UK NDD codes, can I import an ASCII file with the required codes. On the GUI, I cannot find an import facility. But if I can change the directory file with regional codes of UK, it would also help. Entering over 200 codes does not seem practical, and without the UK codes, the software is not suitable for reporting. Any help will be well appreciated.

Many thanks,
vimeni
« Last Edit: December 10, 2004, 05:36:45 AM by vimeni »

sergey

  • Moderator
  • Sr. Member
  • *****
  • Offline Offline
  • Posts: 48
    • View Profile
Re: Duration Correction
« Reply #1 on: December 10, 2004, 11:42:06 AM »
It is possible to filter out junk calls using report customization technique desribed in How to customize report generation topic (http://www.callaccounting.ws/forum/index.php?topic=42.0).

"Duration correction" field on 'Import SMDR' pand and Driver tab of PBX Communcation page is used to define value that will be subtracted from every call duration so it is not possible to use it for calls filtering.

For data export/import CAM uses primarily 2 formats: SQL and XML scripts; for some data tables (e.g. users table) CSV is also used. You may send us sample of data that needs to be imported into CAM and we'll either put support for that format in next CAM release or translate the data to SQL/XML script that you can import in your copy of CAM.