SBC after backup/restore to cloud

[american10]

Hello. I had an onsite 3cx install with a few phones (all on the same local network) and a SPA112 on a remote network through a SBC (running on pi 3). Everything was working fine, but I wanted to retire the server and move everything to the cloud.

I backed up and restored to a cloud instance, factory reset the phones, assigned them again using STUN and they worked fine. I will be moving to a SBC when another pi comes in, but the phones are working fine for now. My question is with the SBC and the ATA at the other location. The SBC was already configured with my FQDN, so I did not think I had to do anything to get it working after the restore to the cloud. My ATA still shows as registered in the SPA112 and the extension shows as green in 3cx. However, I get a dial tone and then a fast busy when I try to dial any number or extension.

What am I missing here? Is there something I need to do with the SBC or within 3CX related to the SBC after the restore to the cloud?

 

[cobaltit]

So what do the call logs say? And have you tried rebooting the SBC and/or the ATA?

 

[YiannisH_3CX]

Hello @american10

Make sure that the tunnel password is the same and check the configuration file of the SBC for any IPs that were used when the PBX was local. If the issue persists then check the activity log for any errors. Also not that the device you are using is not supported and ATA devices are not supported for remote use so there is no guarantee that this will work.

 

[american10]

Hello @american10

Make sure that the tunnel password is the same and check the configuration file of the SBC for any IPs that were used when the PBX was local. If the issue persists then check the activity log for any errors. Also not that the device you are using is not supported and ATA devices are not supported for remote use so there is no guarantee that this will work.

I uninstalled the SBC and reinstalled it using the current password (I'm not sure if the password was correct before). The ATA is set to point to the SBC for registration and it in turn shows up in 3CX as a phone. But still a fast busy signal.

Where would the log file be for the SBC under debian?

 

[YiannisH_3CX]

You will need to enable logging in the SBC through the config file of the SBC.
To access the 3CXSBC configuration file type the following command nano /etc/3cxsbc.conf
To enable logs go to nano /etc/3cxsbc.conf and set [Log] level to DEBUG
To open log file type this command tail -f /var/log/3cxsbc.log

 

[american10]

You will need to enable logging in the SBC through the config file of the SBC.
To access the 3CXSBC configuration file type the following command nano /etc/3cxsbc.conf
To enable logs go to nano /etc/3cxsbc.conf and set [Log] level to DEBUG
To open log file type this command tail -f /var/log/3cxsbc.log

I am going to enable debugging, but I'm not sure what exactly here is even failing. This was previously configured in the exact same way, just the server was at another location (not on site, still using the SBC for the SPA112 ATA).

The ATA points to the SBC. It shows as both registered in the ATA as well as the 3CX cloud instance. It shows green next to the extension in 3CX. I get a dial tone. Any incoming or outgoing call from the phone hooked up to the ATA gets a fast busy signal. This makes no sense to me as literally everything shows as okay except when actually trying to make a call.

 

[craigreilly]

do the 3cx logs show anything when you place the call? or a wireshark?

 

[american10]

I am about to collect the logs, but what's odd is that incoming calls are now working correctly. I can dial the DID from my cell phone and answer (with two way audio) from the phone connected to the ATA.

 

[craigreilly]

So this is not the case... incoming is ok?
---> "Any incoming or outgoing call from the phone hooked up to the ATA gets a fast busy signal."

 

[american10]

So this is not the case... incoming is ok?
---> "Any incoming or outgoing call from the phone hooked up to the ATA gets a fast busy signal."

Yes, this is no longer the case. Incoming is working fine. Outgoing gets a dial tone and then a fast busy after a number is dialed.

 

[american10]

When I make a call from the phone connected to the ATA this is what I see in the SBC log:

debug:3CXTunnel[855]::2018-08-30T23:40:59.464955+00:00: RESIP:TRANSPORT | 1996322608 | Transport.cxx:392 | incoming from: [ V4 192.168.1.249:5061 UDP flowKey=11 transportKey=1 ]

192.168.1.249 is the ATA.

 

[american10]

Another interesting thing about this. If I pick up the phone I get the tone sequence that alerts you that there is a voicemail on your extension. So it's communicating with the 3CX cloud through the SBC because I get a dial tone and also get the voicemail tone before the dial tone.

What am I missing here? It seems like the issue is on the PBX side.

 

[american10]

Where can I look on the 3CX side to see the route the calls are taking?