PeeBeeEx
Trainee Partner
- Joined
- Aug 31, 2018
- Messages
- 33
- Reaction score
- 2
I have 3CX setup with two different SIP Trunks from two different providers.
Each is SIP Trunk is setup as a Generic VOIP Provider within 3CX.
When viewing them from the SIP Trunks page they always show a green dot and appear to be ok, although I've noticed it doesn't seem to refresh registration very often - i.e. Registration Sent/OK can show many hours in the past. (Doesn't seem to show Failed Register very often either)
I've recently noticed that 1 of the providers starts failing to receive incoming calls about 5 minutes after registration.
If I simply refresh registration, it will start receiving incoming calls again immediately and work fine for another 5 minutes, after which it fails to receive any incoming calls again.
Outbound calls from this same SIP Trunk seem to always work fine, even several hours after registration.
What's even more strange, is that if I wait 5 minutes for incoming calls to start failing and then place an outgoing call from the trunk, incoming calls immediately start working again for 5 minutes and then fail.
Initially I thought that when you make an outbound call it probably just immediately sends a re-registration request, but when I check the SIP Trunks page after making an outbound call it doesn't change the registration Sent/OK values.
Is there anything in particular I could try looking at to troubleshoot the issue? If I look at Call Logs / Activity logs while the incoming calls aren't being received I don't see any activity.
I'm not sure if I should try experimenting/re configuring anything in the advanced options for the SIP trunk config? I've tried reducing re-register from 600 to 300 seconds, but again - neither of my trunks seem to follow this setting and go many hours without appearing to send a registration:
Our other trunk appears to always work fine, both incoming/outgoing calls, regardless of how long ago registration has been sent, so it definitely seems to be something to do with this particular provider.
For what it's worth: I don't think we were having these issues up until recently - so not sure if this has only started happening with the Beta 6 update - might try reinstalling an older version and see what happens.
Each is SIP Trunk is setup as a Generic VOIP Provider within 3CX.
When viewing them from the SIP Trunks page they always show a green dot and appear to be ok, although I've noticed it doesn't seem to refresh registration very often - i.e. Registration Sent/OK can show many hours in the past. (Doesn't seem to show Failed Register very often either)
I've recently noticed that 1 of the providers starts failing to receive incoming calls about 5 minutes after registration.
If I simply refresh registration, it will start receiving incoming calls again immediately and work fine for another 5 minutes, after which it fails to receive any incoming calls again.
Outbound calls from this same SIP Trunk seem to always work fine, even several hours after registration.
What's even more strange, is that if I wait 5 minutes for incoming calls to start failing and then place an outgoing call from the trunk, incoming calls immediately start working again for 5 minutes and then fail.
Initially I thought that when you make an outbound call it probably just immediately sends a re-registration request, but when I check the SIP Trunks page after making an outbound call it doesn't change the registration Sent/OK values.
Is there anything in particular I could try looking at to troubleshoot the issue? If I look at Call Logs / Activity logs while the incoming calls aren't being received I don't see any activity.
I'm not sure if I should try experimenting/re configuring anything in the advanced options for the SIP trunk config? I've tried reducing re-register from 600 to 300 seconds, but again - neither of my trunks seem to follow this setting and go many hours without appearing to send a registration:
Our other trunk appears to always work fine, both incoming/outgoing calls, regardless of how long ago registration has been sent, so it definitely seems to be something to do with this particular provider.
For what it's worth: I don't think we were having these issues up until recently - so not sure if this has only started happening with the Beta 6 update - might try reinstalling an older version and see what happens.
Last edited: