- Joined
- Dec 14, 2017
- Messages
- 1
- Reaction score
- 0
Hi
I have been using the PhoneSystem's notification event handlers inserted, updated and deleted events to track call history across multiple 3cx servers. All these servers run 3cx V15.5 on windows server operating systems.
Recently one of these servers started behaving strangely after having run out of disk space on the C:/ drive.
Out of the below 3 events the first two do not trigger at all with the EntityName arg = "CONNECTION". The last one of the 3 events triggers but contains a blank ConfObject arg.
I have tested the code on other 3cx servers running on the same operation system and 3cx version with no issues and this worked perfectly on the broken server prior to the disk space issue.
Does anyone have an idea what could be causing this strange behavior?
I have been using the PhoneSystem's notification event handlers inserted, updated and deleted events to track call history across multiple 3cx servers. All these servers run 3cx V15.5 on windows server operating systems.
Recently one of these servers started behaving strangely after having run out of disk space on the C:/ drive.
Out of the below 3 events the first two do not trigger at all with the EntityName arg = "CONNECTION". The last one of the 3 events triggers but contains a blank ConfObject arg.
- PhoneSystem.Root.Inserted
- PhoneSystem.Root.Updated
- PhoneSystem.Root.Deleted
I have tested the code on other 3cx servers running on the same operation system and 3cx version with no issues and this worked perfectly on the broken server prior to the disk space issue.
Does anyone have an idea what could be causing this strange behavior?