Solved Sip Trunk not registering?

[branden003]

Hello.

Can someone maybe help me with my 3CX, it seems it is not working correctly. my sip trunks are not registering and I'm not sure why. I did contact mt telecommunications company and from their side all is fine and working, but 3CX can not register the link?

 

[KyriacosS_3CX]

Please anonymise your connection details before posting.

 

[branden003]

Sorry about that, Was not aware of any confidential information

 

[bdse]

We are currently experiencing an issue with four of our Free 3CX SMB servers, which are unable to register with the ZA VOX servers. This does not appear to be a VOX-related issue, as we have multiple 3CX servers hosted on Google Cloud that are functioning without any problems.

Unfortunately, 3CX support has responded by stating that there is no support available for Free SMB versions. This response is unacceptable, especially considering that the issue seems to be network-related and specific to 3CX. We believe this warrants further investigation and support from 3CX, regardless of the licensing tier.

 

[branden003]

I been using this system for years now and there is no resolution.

 

[bdse]

Please anonymise your connection details before posting.

Could we please focus on the core issue at hand? The question relates to a clear registration problem affecting multiple Free 3CX SMB servers SIP Trunks. This is not an isolated incident, and it's evident that some 3CX servers are experiencing connectivity issues, despite other instances working fine under similar conditions.

Responses that dismiss the concern without offering technical insight or troubleshooting steps do not add value to the discussion. Whether or not support is officially provided for Free SMB versions, it's important to acknowledge and investigate potential platform-level issues that could affect broader deployments.

Constructive feedback or guidance on how to further diagnose or escalate this issue would be appreciated.

 

[branden003]

Could we please focus on the core issue at hand? The question relates to a clear registration problem affecting multiple Free 3CX SMB servers SIP Trunks. This is not an isolated incident, and it's evident that some 3CX servers are experiencing connectivity issues, despite other instances working fine under similar conditions.

Responses that dismiss the concern without offering technical insight or troubleshooting steps do not add value to the discussion. Whether or not support is officially provided for Free SMB versions, it's important to acknowledge and investigate potential platform-level issues that could affect broader deployments.

Constructive feedback or guidance on how to further diagnose or escalate this issue would be appreciated.

I agree, I can get a response from not posting correctly but when a business relies on a system and it stops working, reaching out is the right way around it? but instead I get ignored an no assistance is given

 

[Charles_3CX]

I agree, I can get a response from not posting correctly but when a business relies on a system and it stops working, reaching out is the right way around it? but instead I get ignored an no assistance is given

Regarding your question and issue mentioned, have you contacted the SIP trunk provider to check this on their end and have them whitelist the IP address of the 3CX system as per the configuration requirements?

 

[branden003]

Regarding your question and issue mentioned, have you contacted the SIP trunk provider to check this on their end and have them whitelist the IP address of the 3CX system as per the configuration requirements?

Good day, yes I have contacted my SIP Trunk provider and they confirm all is in order on there side, we even connected to a different platform and it does work, only when connecting to 3CX it does not register.

 

[Charles_3CX]

I suggest you re-check with them, as the system will send the registration to the provider's side. However, if they don't respond with the '407 Proxy Authentication Required' challenge request, then there is nothing that can be done from our side.

 

[branden003]

Apparently, according to them, it doesn't even show anything registered on their side. They can't pick up anything

 

[Charles_3CX]

I suggest that you insist on them directly, as the registration attempts would have definitely been sent from our side.

I can also suggest deteting the trunks and adding them back in to ensure the configuration is correct.

 

[KyriacosS_3CX]

Could we please focus on the core issue at hand? The question relates to a clear registration problem affecting multiple Free 3CX SMB servers SIP Trunks. This is not an isolated incident, and it's evident that some 3CX servers are experiencing connectivity issues, despite other instances working fine under similar conditions.

Responses that dismiss the concern without offering technical insight or troubleshooting steps do not add value to the discussion. Whether or not support is officially provided for Free SMB versions, it's important to acknowledge and investigate potential platform-level issues that could affect broader deployments.

Constructive feedback or guidance on how to further diagnose or escalate this issue would be appreciated.

@branden003 had uploaded a screenshot including his FULL trunk credentials in clear text. I believe advising to anonymise screenshots is Very constructive feedback and guidance, and takes precedent over any other response.

As mentioned above, have they confirmed that the IP of the PBX has been whitelisted?

 

[branden003]

It was a vox related issue, they denied it at first but came back to me about my number was blacklisted in India but it is fixed now

 

[Charles_3CX]

I would also suggest deleting the trunks and re

It was a vox related issue, they denied it at first but came back to me about my number was blacklisted in India but it is fixed now

There you go, glad you resolved the issue. For future reference, always check with the provider's side for connectivity issues.