SBC stopped working after years

[grandbay1]

SBC just boom stopped working. Its red light on the SIP trunk SBC , on the server it says it cannot connect.
Tried to delete and reinstall the sbc 16 on the server. reinstalled the sbc under add sbc in the client. nothing works.
the New sbc isnt that complicated not many options so i am at a loss.
windows 10 on all machines. PBX web url and authentication key id are correct.

Its just got me baffled.

......More all of a sudden out of no where for no reason the sbc trunk started working and green.

still cant connect the remote phones.

 

[grandbay1]

Uninstalled SBC.....Rebooted SBC machine.....Redownloaded SBC from 3cx site, Updated console Reinstalled...... PORT 5060 is correct not port 5090 like someone said above.

Still same problem. I can see the phones under phones sbc (see pic)
But i cannot assign an extension.

 

[JohnS_3CX]

I don't see you current SBC version though, it should show 16.0.390 in the trunks section

 

[Evolute IT]

PORT 5060 is correct not port 5090 like someone said above

What you see is the SBC local SIP port.

The SBC Tunnel does use 5090. Not 5060.

 

[grandbay1]

I don't see you current SBC version though, it should show 16.0.390 in the trunks section

its version 16.1.152

 

[grandbay1]

What you see is the SBC local SIP port.

The SBC Tunnel does use 5090. Not 5060.

when you install the SBC it clears states it uses 5060, and to make sure the port is open. but whatever ive been using 5060 for past 2 years flawless.

 

[Evolute IT]

when you install the SBC it clears states it uses 5060, and to make sure the port is open. but whatever ive been using 5060 for past 2 years flawless.

LOCALLY the SBC DOES use 5060. That's where the local phones joins the SBC.

The SBC itself connects to the PBX using the Tunnel, which uses 5090.

3CX will confirm that.

 

[AWS2P]

16.1.152 is a Beta SBC but i' m using it everywhere without problems

 

[cobaltit]

LOCALLY the SBC DOES use 5060. That's where the local phones joins the SBC.

The SBC itself connects to the PBX using the Tunnel, which uses 5090.

3CX will confirm that.

This is correct. The phones connect to the SBC on port 5060 UDP just as they would to a local 3CX instance. The SBC then tunnels this traffic back to 3CX on 5090.

Forget about the phones for now. Is the SBC connecting back to 3CX ok (green in the trunk)? If you select the SBC in the trunks and click 'Push Config' does it go red and then green again? If so then you know communication is working between 3CX and the SBC as far as the provisioning goes.

 

[grandbay1]

Solved............. Ok by trial and error i got it...... Had to go into Yealink GUI manually and on server 1 changed the SBC ip address to local lan address (192.168.1.12) in my case. port 5060. Then instantly registered and works great again.

 

[JohnS_3CX]

@grandbay1

In message #17 I advised you not to update it so we can test the stable version, the update is currently a beta as can clearly be seen during the update process


Also changing the IP in the Yealink interface would indicate that the SBC machine's IP had recently changed, causing the phones to stop registering. In this case, if you factory reset a phone and reprovision it automatically it should come back up with no problems.

 

[grandbay1]

@grandbay1

In message #17 I advised you not to update it so we can test the stable version, the update is currently a beta as can clearly be seen during the update process

+++++++ It was already done, by the time message #17 was posted.........

View attachment 18648

Also changing the IP in the Yealink interface would indicate that the SBC machine's IP had recently changed, causing the phones to stop registering. In this case, if you factory reset a phone and reprovision it automatically it should come back up with no problems.

Now i did a factory reset. Put in my provisioning url...... and it connected very nice to someone elses PBX in PHOENIX.....now i certainly dont understand that one.

 

[grandbay1]

Solved............. Ok by trial and error i got it...... Had to go into Yealink GUI manually and on server 1 changed the SBC ip address to local lan address (192.168.1.12) in my case. port 5060. Then instantly registered and works great again.

TODAY not connected again. and local IP does not work anymore. lasted 1 day.

 

[Evolute IT]

TODAY not connected again. and local IP does not work anymore. lasted 1 day.

Did you reserve an IP for the SBC in the DHCP of the router? You have to use a DHCP reservation (or static IP, depending on network config).

This would explain why your phones keep disconnecting. Also, make sure you don't have IP conflicts (same IP twice on the network, which happens a lot with static IPs).

 

[AWS2P]

which happens a lot with static IPs

To prevent this problem of IP conflict i'm used to follow IPs in a XLS file and do logical range not overlaping for pc, printers, and for active devices as servers, switches, routers etc.....

 

[JohnS_3CX]

Now i did a factory reset. Put in my provisioning url...... and it connected very nice to someone elses PBX in PHOENIX.....now i certainly dont understand that one.

I'm thinking that your phones are registered in the Yealink RPS server, and they are auto provisioning themselves regardless of your SBC/PBX.

This would be entirely outside of the scope of 3CX, and you might need to contact Yealink to remove your MAC addresses from their database in this case so they stop auto-provisioning themselves on some 3rd party server.