Some strange issues here, not sure if related to sp4 or siptrunk.com's newer template?
Both 3CX and siptrunk have reviewed logs and captures. They seem to agree that for some reason, when this happens, the siptrunk service is not receiving notification that the call was received, so it keeps sending it. Network gear has been blamed, but I have it configured the same as I have for dozens of other deployments. And if network config was at fault I would expect the problem to be reproducible and not so random.
I tried another sip provider on the same system and did not have trouble, but have not taken the time to make the same hundreds of test calls through that service yet.
Any similar experiences out there?
- 3CX server with dynamic public IP: when the server is booted it takes 20 minutes for siptrunk to register. If I manually run firewall checker it registers right away. In static IP mode this does not happen.
- Intermittent incoming call multiplication. A single call comes in and produces multiple duplicate call entries in the active call view to the point it maxes out the allowed licensed simultaneous calls. This can happen immediately after a system start or every 100 calls, completely random. I was thinking something to do with public DNS?
Both 3CX and siptrunk have reviewed logs and captures. They seem to agree that for some reason, when this happens, the siptrunk service is not receiving notification that the call was received, so it keeps sending it. Network gear has been blamed, but I have it configured the same as I have for dozens of other deployments. And if network config was at fault I would expect the problem to be reproducible and not so random.
I tried another sip provider on the same system and did not have trouble, but have not taken the time to make the same hundreds of test calls through that service yet.
Any similar experiences out there?
