Solved SIP Registration

[TBlaine2782]

I have 2 3CX servers, 1 is hosted with 3CX and one is hosted with Vultr.

I am able to register phones to the 3CX server hosted at Vultr no problem

When I attempt to register some phones with the 3CX hosted one, the green circle next to the username goes green for a minute, then red and I get URL dialing not available on the phone. But some phones register no problem.

I do not have a double NAT
I have disabled SIP ALG
Nothing in blacklist

I have no idea what's going on

 

[mixig]

I have 2 3CX servers, 1 is hosted with 3CX and one is hosted with Vultr.

I am able to register phones to the 3CX server hosted at Vultr no problem

When I attempt to register some phones with the 3CX hosted one, the green circle next to the username goes green for a minute, then red and I get URL dialing not available on the phone. But some phones register no problem.

I do not have a double NAT
I have disabled SIP ALG
Nothing in blacklist

I have no idea what's going on

Are you using STUN or 3CX SBC?
Firewall checker passes all ports?

 

[Alphabetic]

Are you using 2 different licenses or the same one at two locations?

 

[TBlaine2782]

Are you using 2 different licenses or the same one at two locations?

2 different licenses.

 

[TBlaine2782]

Are you using STUN or 3CX SBC?
Firewall checker passes all ports?

FIrewall checker passed on all ports, no issues there.

I just deployed the SBC in a Virtual Machine, and the phones I was having an issue with registered via SBC without any issue...... VERY strange.

 

[ChrisC_3CX]

Did you use an SBC before as well or were they provisioned via STUN? If they were then that would probably explain it as STUN provisioning required some configuration prep

That said, we always recommend using the 3CX SBC over STUN as it's:

1. Much easier to set up and IP Phone provisioning can be done via PnP
2. Adds a layer of security due to the 3CX Tunnel
3. Ensures smooth functionality
4. Does not require remote firewall configuration

The only downside is that you need something to host it and run 24/7

 

[TBlaine2782]

Did you use an SBC before as well or were they provisioned via STUN? If they were then that would probably explain it as STUN provisioning required some configuration prep

That said, we always recommend using the 3CX SBC over STUN as it's:

1. Much easier to set up and IP Phone provisioning can be done via PnP
2. Adds a layer of security due to the 3CX Tunnel
3. Ensures smooth functionality
4. Does not require remote firewall configuration

The only downside is that you need something to host it and run 24/7

This office had 3 phones existing, registered by STUN and had no issues for the past 6 months. It's when I went to add new phones yesterday I uncovered this issue, but the SBC is handling everything perfectly now.

We have VMware ESX servers, so standing up the SBC in a VM was no problem at all.

SBC is soooooo easy!!!!

 

[ChrisC_3CX]

SBC is soooooo easy!!!!

You can say that again!!

Glad to see you got this sorted! I'll be marking this as solved so let us know if anything else comes up!