Generic SIP Provider - unable to connect

[Marcin_KFAM]

Hello everyone,

I'm quite new in this community, so excuse me for beeing sometimes unprecise or too general.
I've installed 3CX server on premise on my own dedicated server with public IP (esxi hosted).
The server has internet connectivity and resolves the DNS with nslookup correctly.
I've created a new Generic SIP Trunk, since my provider wasn't found, and configured it with my best knowledge. Unfortunately I receive two errors when the sertries to register the Sip Trunk:

Registration at Generic SIP Trunk has failed. Destination (sip:485663xxxxx%[email protected]:5060) is not reachable, DNS error resolving FQDN, or service is not available.

and shortly after:
Call or Registration to Generic SIP Trunk has failed. sip:485663xxxxx%[email protected]:5060 replied: 403 Forbidden; from IP:83.0.8.193:5060

I've checked and the server can't ping the neofon.tp.pl but it resolves the name correctly.

Can you check what can be the issue?
Why as a user name I have twice the domain name printed: %[email protected]?

 

[eddv123]

Firstly if registration is failing there is no point trying to make a call. Ensure (and based on your settings I can see you are using a registration based SIP provider) that the little circle goes green - since the error is registration related this should currently be red.

If you cannot ping not an issue as it is most likely hidden by a proxy or SBC but if you do a trace route where does the trace route stop ? it sounds to me like there is a DNS issue from your 3CX server so please also ensure that you have direct internet access (and since you can resolve the FQDN via nslookup I will assume you do) and that Windows firewall or local firewall is not blocking.

Also if you can resolve the FQDN of the provider you can also see its public IP, have you tried (as a test) using this instead ?

 

[YiannisH_3CX]

Hello @Marcin_KFAM

If you had provided the logs without the screenshots i would assumed that your Auth ID was [email protected] or something similar. Make sure that your Auth ID is only the number and press OK so that the PBX tries to re-connect. Also make sure that there are no spaces included in the Auth ID.