Hi Joe,

First of all, check out these documentations to find useful information for your data archive.

https://developers.ringcentral.com/guide/voice/call-log/archival

https://developers.ringcentral.com/guide/voice/call-log/sync

The best way to archive is to use the call log sync API though.

Back to your questions/problems, the ids should be unique. Can you post a few records which have the same ids (remember to erase sensitive info such as phone number, name etc.)

So the call log archival is what we are using. The issue is a best practice to retrieve call logs every 5 minutes. We have it working but we do not want to duplicate call logs on our side, so we filter out any existing ids. The issue is that the duration may not be correct as it appears Ring Central will update that id on their end through the life of the call. So my reference to duplicates earlier may not be the case, but an update. So we have a hard time to pull the updated call log without having to delete all records from a portion of time back and re-bring that data in.

I like and wanted to use the fSync/iSync method, but having trouble understanding the 250 limit. We have over 200 users so it is very possible to have more than 250 each sync,.

I am lacking an example for the data at the moment as we removed it to bring in the correct record, but here is an example of what we are seeing.

id: xyz --- startTime : 1/1/2019 17:00:148 --- duration: 4 --- session id: 1234

id: xyz --- startTime: 1/1/2019 17:00:133 --- duration: 75 --- sessionid:1234

The times will be different, the id and session id will be the same. Only one ever exits on the Ring Central Side, thus why we think it gets updated in the life of the call.

So, again, we are searching for best way to handle. Sounds like deleting all records for a period of time and bringing them all back in.