- Joined
- Apr 12, 2019
- Messages
- 35
- Reaction score
- 5
I have questions about how the 3CX server handles the registration and re-registration of the Session Border Controllers:
1) what is this process supposed to look like
2) how fast is it supposed to happen?
3) is this a thing that should be happening when there are active calls? if so how does it handle renegotiating the calls (as it appears to disconnect the SBC from the server for a short time)?
I ask these because I've been dealing with a lot of dropped calls after accidentally upgrading to the beta of SBC 16.0.152 then rolling my 6 SBCs back to 16.0.390.
I caught one in the happen and it looks like an ongoing call (via an SBC connected device) gets pretty much orphaned wen the SBC CONN EVENT / SBC DELETE EVENT storm happens in my log file. The call never gets a SIP BYE or termination, it just hangs out.. but the other end is long gone. It gets resolved when the user hangs up their next call, but not before that generally.
Tonight I took the time to uninstall the SBC software on each SBC device, delete the SBC's from 3CX server (16.0.5.619), and I'm praying that this will quell the drops because I'm tired of the CEO texting me and my bosses.
1) what is this process supposed to look like
2) how fast is it supposed to happen?
3) is this a thing that should be happening when there are active calls? if so how does it handle renegotiating the calls (as it appears to disconnect the SBC from the server for a short time)?
I ask these because I've been dealing with a lot of dropped calls after accidentally upgrading to the beta of SBC 16.0.152 then rolling my 6 SBCs back to 16.0.390.
I caught one in the happen and it looks like an ongoing call (via an SBC connected device) gets pretty much orphaned wen the SBC CONN EVENT / SBC DELETE EVENT storm happens in my log file. The call never gets a SIP BYE or termination, it just hangs out.. but the other end is long gone. It gets resolved when the user hangs up their next call, but not before that generally.
Tonight I took the time to uninstall the SBC software on each SBC device, delete the SBC's from 3CX server (16.0.5.619), and I'm praying that this will quell the drops because I'm tired of the CEO texting me and my bosses.
