- Joined
- Nov 17, 2017
- Messages
- 912
- Reaction score
- 586
So all of the sudden on our v16 in-house 3CX Server, the mobile apps are performing oddly with the handling of voicemail.
Example:
Extension 206 on an iPhone 10 shows 6 voicemails, however attempting to listen to them yields "file not found", Attempting to delete them, does nothing, and they do not disappear...
Restarting services caused the list on the App to update, however the issue remains, when i try to delete another voicemail, it remains on the app.
Interesting detail, if i watch the voicemails folder via SSH, when i attempt to delete a voicemail on the App, the file(WAV and XML) is deleted from the server, however the app still shows it in existence, even after closing the app, re-opening, and even uninstalling and reinstalling on a separate device.... Its as if the system that manages the indexing of voicemails to the Apps, is glitching out and not removing them from the index except when a new VM is created, or the services restart...
We have reproduced this on both an iPhone 10, and a Android 8.0 device, the issue is the same, which tells me it is server side.
Example:
Extension 206 on an iPhone 10 shows 6 voicemails, however attempting to listen to them yields "file not found", Attempting to delete them, does nothing, and they do not disappear...
Restarting services caused the list on the App to update, however the issue remains, when i try to delete another voicemail, it remains on the app.
Interesting detail, if i watch the voicemails folder via SSH, when i attempt to delete a voicemail on the App, the file(WAV and XML) is deleted from the server, however the app still shows it in existence, even after closing the app, re-opening, and even uninstalling and reinstalling on a separate device.... Its as if the system that manages the indexing of voicemails to the Apps, is glitching out and not removing them from the index except when a new VM is created, or the services restart...
We have reproduced this on both an iPhone 10, and a Android 8.0 device, the issue is the same, which tells me it is server side.