- Joined
- Feb 19, 2021
- Messages
- 8
- Reaction score
- 1
Good day.
I have some concerns about call data that seems to be/go missing.
I am using the 3CX Configuration and Call Control API v3.0.0.0 (v16) documentation and the OMSamples source to "play" with to try and figure out how things work.
I used the Samples.CallStateMonitor implementation to monitor new calls.
The default delay between snapshot calls was 5000 milliseconds.
I also changed this to 1000 milliseconds and then to 100 milliseconds to test the effects.
Does the delay between snapshots have any bearing on what data is collected?
I used the call log data to match with the data of the snapshot output and was able to follow the blind transfers up to a point and then it went silent.
The data for the rest of the call went missing. I could also not find attended transfer data for that extension or external number but seriously doubt that it was an attended transfer because it was a transfer from a queue.
I also made a call to an external number which was answered and the call was 30 seconds long but this data never appeared in the snapshot data...
Does the Phonesystem.WaitForConnect have any bearing on the frequency of call snapshot entries?
The reason for this question is that it seemed like the "RoutingTo" entries for the Queue gets trimmed every 30 seconds and then added again with new ID's.
Co-incidentally the Phonesystem.WaitForConnect was set to 30 seconds.
Is it better to subscribe to PBX events for accurate call data?
I'm asking this question in advance since I am pressed for time with this integration.
I am now going to test data with the PhoneSystem.Inserted/Updated/Deleted events.
Also, I am asking if the PhoneSystem.WaitForConnect would have any bearing on the frequency at which the data will be collected since the subscription to these events will happen during the "BootStrap".
Thank you in advance!
I have some concerns about call data that seems to be/go missing.
I am using the 3CX Configuration and Call Control API v3.0.0.0 (v16) documentation and the OMSamples source to "play" with to try and figure out how things work.
I used the Samples.CallStateMonitor implementation to monitor new calls.
The default delay between snapshot calls was 5000 milliseconds.
I also changed this to 1000 milliseconds and then to 100 milliseconds to test the effects.
Does the delay between snapshots have any bearing on what data is collected?
I used the call log data to match with the data of the snapshot output and was able to follow the blind transfers up to a point and then it went silent.
The data for the rest of the call went missing. I could also not find attended transfer data for that extension or external number but seriously doubt that it was an attended transfer because it was a transfer from a queue.
I also made a call to an external number which was answered and the call was 30 seconds long but this data never appeared in the snapshot data...
Does the Phonesystem.WaitForConnect have any bearing on the frequency of call snapshot entries?
The reason for this question is that it seemed like the "RoutingTo" entries for the Queue gets trimmed every 30 seconds and then added again with new ID's.
Co-incidentally the Phonesystem.WaitForConnect was set to 30 seconds.
Is it better to subscribe to PBX events for accurate call data?
I'm asking this question in advance since I am pressed for time with this integration.
I am now going to test data with the PhoneSystem.Inserted/Updated/Deleted events.
Also, I am asking if the PhoneSystem.WaitForConnect would have any bearing on the frequency at which the data will be collected since the subscription to these events will happen during the "BootStrap".
Thank you in advance!
