3cx SBC not working PLEASE help

djboxny · Nov 14, 2016

i installed SBC on my remote sever to connect to my Office 3cx Free installed. I keep getting this error

ERR | 20161114-131250.328 | 3CXTunnel | TUNL | 4624 | TunnelTcp.cpp:295 | Bridge [3CXSBC15.0.56341] failure 'Connection is terminated by peer - while begin to read a packet from tunnel' on TCP connection: TunnelTcp:

rocess

I am pretty sure i set up my SBC correctly and its not being blocked by the IP Firewall on 3cx. Also i can connect a remote extension directly. Meaning straight thru without using the Session Border Control

leejor · Nov 14, 2016

If you run the Firewall Checker on the PBX, does it pass on all ports?

djboxny · Nov 14, 2016

IT Hamster · Nov 14, 2016

If you installed the SBC software on Windows make sure you have Windows Firewall turned off or set to allow traffic on the correct ports. Default ports are 5090 and 5060.

A tool i've used to check ports is https://technet.microsoft.com/en-us/sys ... pview.aspx

run that on both sides (sbc and pbx) and make sure you're seeing traffic between the hosts on the correct ports.

Check your firewall device(s) that sit between the SBC and PBX and make sure those ports are allowed.

Your PBX sounds fine, since it passed the firewall checker- so the port issue is possibly on the SBC side.

Also, you can try modifying your 3cx.config file on the SBC to use the public IP of your PbX instead of the FQDN to rule out a DNS related problem.

djboxny · Nov 14, 2016

i only see 3cxsbc.exe external local port 5060
i dont see 5090. also windows firewall is off. i ran a port check and that port is open 5090

deanril@yahoo.com · Nov 14, 2016

On the sbc machine the phone will connect to the sbc local lan on 5060 to the ip of sbc.

The sbc will use 5090 between it and the pbx. I would open tdp/udp 5090 and nat it to the pbx.

djboxny · Nov 15, 2016

It is open. Port 5090 is nated to the sbc machine. I checked it with a port scanner and can you see me web site.
Windows firewall is off too

pchiappisi · Nov 16, 2016

I have been attempting to deploy a 3CX SBC (v14) on a r-pi2 and have the same error in my log.

the interesting thing is that i've currently got the 3CX SBC running fine on a Windows server using the same settings in the 3CX SBC configuration as the r-pi2 that is failing. I have no special routes configured in my router for the existing 3CX SBC and it works fine, so there should be no reason to need one for this replacement installation. firewall ports 5060, 5090, and 5001 are open on the remote site with the r-pi2, and the 3CX Server must be fine port wise since the existing tunnel is connecting from the same public IP as the working SBC.

Not to hijack this thread, but can two SBC's connect to a single 3CX Server without conflict?
Should i change the tunnel ID in the config file on my second SBC if i have both running at once?

IT Hamster · Nov 23, 2016

Not to hijack this thread, but can two SBC's connect to a single 3CX Server without conflict?
Should i change the tunnel ID in the config file on my second SBC if i have both running at once?

Yes, in fact it is recommended that you use multiple SBCs in order to load balance larger environments.

SBC v14 is single threaded software and is supposed to support up to 25 Physical phones with 5 BLF buttons each.

I have a few deployments where the client has 60+ phones so I install 2 SBCs on site- same subnet as eachother same everything except for their hostnames and the SBC name in the config file (for logging purposes).

You just assign your phones to each SBC during provisioning phase. Sadly, it doesn't function as a "failover", but it does the trick for load balancing.

On the other hand, for clients with lots of remote offices- I put an SBC at every location to handle traffic at each site- One client has 5 of these setups.

Back to the original issue of your SBC not connecting: Are you using the FQDN of your PBX? Try inserting the Public IP of your PBX to rule out a DNS issue.

djboxny · Nov 23, 2016

I used the ip and it still did not work. I do not have a static ip but i should still be able to connect

IT Hamster · Nov 23, 2016

Can you enable Verbose Logging on your SBC and then restart the service then post the errors here for me to look at?

djboxny · Nov 23, 2016

How would i do that, enable verbose

djboxny · Nov 23, 2016

In the config file?

IT Hamster · Nov 23, 2016

Great question!

Here's how:

On Windows I presume?

Open up the program files folder for 3CX SBC.

inside that folder you should see a file call 3cxsbc.conf

You will need to open this file as "admin". I usually just launch notepad++ (or w/e your preferred text editor is) as an admin then I open the 3cxsbc.conf file.

Once in the file, you will see the following information:

[Bridge/123456]
Name=3CXSBC15.0.59172
TunnelAddr=%Your FQDN or PBX PUBLIC IP HERE%
#LocalSipPort=5060
ID=123456
#LocalSipAddr=0.0.0.0
Password=%TUNNEL_PASSWORD%
PbxSipIP=%PBX_FQDN_OR_PUBLIC_IP%
PbxSipPort=5060
SecurityMode=0
TunnelPort=5090
[General]
FailoverInterval=90
PrintStatsInterval=30
ReconnectInterval=30
[Log]
Type=file # cout, cerr, file, syslog
Level=ERR # "ERR", "NONE", "EMERG", "ALERT", "CRIT", "ERR", "WARNING", "NOTICE", "INFO", "DEBUG", "STACK", "ERR", "VERBOSE"
File=C:\ProgramData\3CXSBC\Logs\3cxsbc.log

The 3rd to bottom line is where you adjust verbosity. Warning! This will start taking up a LOT of storage if you let it run in a high volume environment. Just enable verbose, do your testing then set it back to ERR.

Here's how you change it. after "Level=ERR" put a ',' and add what you want.

Example:
Level=ERR,DEBUG

This will enable ERRORs and DEBUG. DEBUG is pretty much everything so your logs will be nice and verbose.

Once you change it, save the file, then restart your 3CX SBC service.

Additionally,

This file is also what you will modify if you're tweaking the Public IP the SBC is looking for- the thing I asked about earlier in the thread.

djboxny · Nov 23, 2016

NS | 5932 | AresDns.cxx:369 | DNS initialization: found 5 name servers
INFO | 20161123-005614.300 | 3CXTunnel | RESIP

NS | 5932 | AresDns.cxx:380 | name server: 8.8.8.8
INFO | 20161123-005614.300 | 3CXTunnel | RESIP

NS | 5932 | AresDns.cxx:380 | name server: 4.4.4.4
INFO | 20161123-005614.300 | 3CXTunnel | RESIP

NS | 5932 | AresDns.cxx:380 | name server: 192.168.13.1
INFO | 20161123-005614.300 | 3CXTunnel | RESIP

NS | 5932 | AresDns.cxx:380 | name server: 196.3.81.5
INFO | 20161123-005614.300 | 3CXTunnel | RESIP

NS | 5932 | AresDns.cxx:369 | DNS initialization: found 5 name servers
INFO | 20161123-005614.309 | 3CXTunnel | RESIP

NS | 5932 | AresDns.cxx:380 | name server: 8.8.8.8
INFO | 20161123-005614.309 | 3CXTunnel | RESIP

NS | 5932 | AresDns.cxx:380 | name server: 4.4.4.4
INFO | 20161123-005614.309 | 3CXTunnel | RESIP

NS | 5932 | AresDns.cxx:380 | name server: 192.168.13.1
INFO | 20161123-005614.309 | 3CXTunnel | RESIP

NS | 5932 | AresDns.cxx:380 | name server: 196.3.81.5
INFO | 20161123-005614.309 | 3CXTunnel | RESIP

NS | 5932 | DnsStub.cxx:67 | _3cxtunnel._tcp.fqdn.wan.3cx.us (SRV) --> p=10 w=0 fqdn.wan.3cx.us:5090
DEBUG | 20161123-005614.379 | 3CXTunnel | TUNL | 5932 | Dns.cpp:138 | [DNS] Got DNS SRV result for _3cxtunnel._tcp.fqdn.wan.3cx.us: status = 0
INFO | 20161123-005614.379 | 3CXTunnel | TUNL | 5932 | Dns.cpp:58 | [DNS} Got SRV record: target fqdn.wan.3cx.us:5090; priority=10, weight=0
INFO | 20161123-005614.379 | 3CXTunnel | TUNL | 5932 | Dns.cpp:89 | [DNS] Resolving IP address(es) for fqdn.wan.3cx.us
DEBUG | 20161123-005614.443 | 3CXTunnel | RESIP

NS | 6000 | DnsStub.cxx:67 | _3cxtunnel._tcp.fqdn.wan.3cx.us (SRV) --> p=10 w=0 fqdn.wan.3cx.us:5090
DEBUG | 20161123-005614.975 | 3CXTunnel | TUNL | 6000 | Dns.cpp:138 | [DNS] Got DNS SRV result for _3cxtunnel._tcp.fqdn.wan.3cx.us: status = 0
INFO | 20161123-005614.975 | 3CXTunnel | TUNL | 6000 | Dns.cpp:58 | [DNS} Got SRV record: target fqdn.wan.3cx.us:5090; priority=10, weight=0
INFO | 20161123-005614.975 | 3CXTunnel | TUNL | 6000 | Dns.cpp:89 | [DNS] Resolving IP address(es) for fqdn.wan.3cx.us
DEBUG | 20161123-005614.975 | 3CXTunnel | RESIP

deanril@yahoo.com · Nov 24, 2016

Here is my config:

[Bridge/123456]
Name=3CXSBC15.0.56341
TunnelAddr=xxx.3cx.us
#LocalSipPort=5060
ID=123456
#LocalSipAddr=0.0.0.0
Password="xxxxxxxx"
PbxSipIP=xxx.3cx.us
PbxSipPort=5060
SecurityMode=1
TunnelPort=5090
[General]
FailoverInterval=90
PrintStatsInterval=30
ReconnectInterval=30
[Log]
Type=file # cout, cerr, file, syslog
Level=ERR # "ERR", "NONE", "EMERG", "ALERT", "CRIT", "ERR", "WARNING", "NOTICE", "INFO", "DEBUG", "STACK", "ERR", "VERBOSE"
File=C:\ProgramData\3CXSBC\Logs\3cxsbc.log

Mine is working is V15

deanril@yahoo.com · Nov 24, 2016

What version 3cx PBX you running? And what version SBC you running? This could be your problem. As you have to run the same versions of SBC/PBX to get this going. Not sure if free allows SBC either...

djboxny · Nov 24, 2016

I thinks its that. Because its the free version. Can someone comfirm this please

YiannisH_3CX · Nov 24, 2016

Hello there,

Nothing to do with the the free version as you can see in the following article,
http://www.3cx.com/phone-system/edition-comparison/

Try the following and let us know if it works
Make sure you have the latest V15 windows SBC, you can try re-downloading to make sure.
Also make sure that your FQDN resolves ti the correct IP on the PBX site.
Disable antivirus and firewall on the windows SBC machine
Do not enable encryption during installation just for test.
Restart the tunnel service on the PBX and check if it works.
If not then stop the SBC service open the sbc config and comment in (remove the #) #LocalSipAddr=0.0.0.0 and #LocalSipPort=5060 and fill in the ip of the SBC machine in the LocalSipAddr.
Save the file and file start the service of the SBC and try again.

Let us know of the results

djboxny · Nov 25, 2016

I did that and Nothing.

In my mikrotik router i see the packet coming in. It seems like 3cx isw terminating the connection

ERR | 20161124-234940.848 | 3CXTunnel | TUNL | 4152 | TunnelTcp.cpp:262 | Bridge [3CXSBC15.0.60789] failure 'Connection is terminated by peer - while begin to read a packet from tunnel' on TCP connection: TunnelTcp:

rocess

3cx SBC not working PLEASE help

djboxny

leejor

djboxny

IT Hamster

djboxny

[email protected]

djboxny

pchiappisi

IT Hamster

djboxny

IT Hamster

djboxny

djboxny

IT Hamster

djboxny

[email protected]

[email protected]

djboxny

YiannisH_3CX

Support Team

djboxny

Latest Posts

Forum statistics

20 Years of VoIP
Industry Leadership

Company

Solutions

Useful Links

Learn More

3cx SBC not working PLEASE help

Support Team

Forum statistics

20 Years of VoIP Industry Leadership

Company

Solutions

Useful Links

Learn More

20 Years of VoIP
Industry Leadership