Trouble getting SIP to register

[mcannon]

I have recently install 3CX V16 trial edition but I can t get the SIP trunk to register. PLEASE HELP!!!

NexVortex has many users that are successfully using 3CX v16 and NexVortex SIP trucks setup in Generic settings.

3CX Server

• Windows 10 with all patches
• 3CX V 16 trial edition
• Internal IP: 10.10.10.25 (NATd via firewall and all ports forwarded)
• DNS: 8.8.8.8
• xxxxxxxxx.tx.3cx.us - FQDN in Network settings

Firewall

• Untangle V 14.1.2
• Static Public IP on Ext interface (207.70.X.X)
• Public IP (207.70.x.x) NATd to private IP (10.10.10.25)
• All Ports (5060,5090, 5000,5001, etc) for public IP forwarded to internal IP (10.10.10.25)

SIP Provider

• NexVortex (Set as Generic in 3CX configuration)
• SIP provider can ping by 3CX server (via public IP address 207.70.x.x)
• Provider is not seeing any traffic from my external IP address

3CX Firewall tests - 100% good
Test from Firewall:

• DNS lookup of nexvortec,com (Gateway/Registrar Hostname) - GOOD
• Tracert over UDP 5060 (nexVortex.com) - GOOD

ERROR:

SIP Server/Call Manager ID: 12293

Registration at nexVortex has failed. Destination (sip:[email protected]:5060) is not reachable, DNS error resolving FQDN, or service is not available.

 

[AWS2P]

On dashboard you have a blacklisted IP, have you check to see if it's not your sip provider.

According to what is in your post your install is well done.

 

[AWS2P]

try to enter IP adress instead of domain name for your sip Provider in trunk set 104.219.163.75 remove nexvortex.com
after validation , refresh trunk register , Is this doing best result?

 

[mcannon]

On dashboard you have a blacklisted IP, have you check to see if it's not your sip provider.

According to what is in your post your install is well done.

Thanks AWS2P!

THe Blacklisted IP was for a Grandstream phone I ad connected. I removed the phone and unplugged it.

 

[mcannon]

try to enter IP adress instead of domain name for your sip Provider in trunk set 104.219.163.75 remove nexvortex.com
after validation , refresh trunk register , Is this doing best result?

Thanks AWS2P!!! I really appreciate the help!

I tried the IP address of 104.219.163.75 for the provider host name. I also did an NSLOOKUP for nexvortex.com and got an IP address of 52.52.238.137. I tried it also. Neither worked.

Any other suggestions would be GREATLY appreciated!!!

 

[leejor]

You might have to resort to using Wireshark, after 3CX (and perhaps any firewall), to see exactly what destination the registration/Invite is being sent to. Incorrect IP, or port, would be my first assumption.

 

[cobaltit]

Or stop using Nexvortex and use a supported SIP trunking provider .

 

[eddv123]

I tried the IP address of 104.219.163.75 for the provider host name. I also did an NSLOOKUP for nexvortex.com and got an IP address of 52.52.238.137.

Sounds like (and please confirm) that you are going to be sending your Register messages to the wrong IP address (or have been provided the wrong IP address), as @leejor says a Wireshark maybe necessary - run a trace from 3CX and see where the Register messages are being sent - this can be done from the 3CX interface: https://www.3cx.com/docs/capture-network-traffic/

Check the : Registrar/Server/Gateway Hostname or IP and Proxy server settings within the trunk and ensure they are accurate to what the provider has sent you.

Note: When you have got the trunk registered I would suggest enabling: "Force Invites to be send to IP of Registrar"

This setting is used If there is some sore of mismatch between Provider and PBX. This can be caused when there is a DNS Record with multiple addresses the same weight/priority, it could happen that 3CX registers to IP A, but when making and outbound call, the INVITE is sent to IP B.

If this is not supported by the SIP Trunk provider, enable this in the “Options” tab in the SIP Trunk settings, to always send INVITE messages to the IP that 3CX resolved to send the REGISTER message.

 

[YiannisH_3CX]

Hello @mcannon

First of all pleas be careful with the information you post on public forums. Generally public ips, FQDNs and Auth IDs should be avoided.
Regarding your issue try removing the registrar address from the outbound proxy address and leave only the registrar field populated. See if that helps.
If not then as suggested you will need to sue wireshark to determine what is being sent by the PBX to the provider.