fix: voip call history doesn't always log the correct call information#35006
fix: voip call history doesn't always log the correct call information#35006kodiakhq[bot] merged 30 commits intodevelopfrom
Conversation
|
Looks like this PR is not ready to merge, because of the following issues:
Please fix the issues and try again If you have any trouble, please check the PR guidelines |
🦋 Changeset detectedLatest commit: 846ee05 The changes in this PR will be included in the next version bump. This PR includes changesets to release 38 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #35006 +/- ##
===========================================
+ Coverage 64.79% 64.80% +0.01%
===========================================
Files 3153 3304 +151
Lines 104884 107875 +2991
Branches 19990 20295 +305
===========================================
+ Hits 67959 69911 +1952
- Misses 34237 35147 +910
- Partials 2688 2817 +129
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
ee72bde to
b7d0f1a
Compare
…ata to the profile of all legs
|
This PR currently has a merge conflict. Please resolve this and then re-add the |
Proposed changes (including videos or screenshots)
Issue(s)
Several problems with the data currently stored on the VoIP call history:
- It logs too many "empty" calls that didn't happen (Still unknown why freeswitch is sending the events that are causing those in the first place)- If the same freeswitch server is used elsewhere, it is logging all of its calls as if the rocket.chat workspace had been involved on them.- If the same freeswitch server is used in multiple workspaces, it will log every call in every workspace, each of them with their own users.VSTAB-36
Steps to test or reproduce
Further comments