New to 3cx, setting up SBC

[Biathlon]

Hi,

We recently had 3CX installed by someone. It was done with a rasppi but I am now trying to setup a windows SBC. I installed the SB, input my settings but I can't seem to get it to connect. I believe I have my username, password and SIP address settings correct. Not really sure what I'm missing here. It was working a few month ago then the SBC was taken away. I assumed it would all start working again when I put in my new SBC.

DEBUG | 20180928-145730.214 | 3CXTunnel | RESIP:TRANSPORT | 3000 | InternalTransport.cxx:121 | Creating fd=892 V4/TCP
DEBUG | 20180928-145730.214 | 3CXTunnel | RESIP:TRANSPORT | 3000 | InternalTransport.cxx:133 | Binding to 0.0.0.0
NOTICE | 20180928-145730.214 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:103 | TCP socket (892) is created and bound to [ V4 0.0.0.0:49822 UNKNOWN_TRANSPORT ]

   MAC=XX:XX:XX:XX:XX:XX; MAC hash =
DEBUG | 20180928-145730.214 | 3CXTunnel | RESIP:TRANSPORT | 3000 | InternalTransport.cxx:121 | Creating fd=936 V4/UDP

NOTICE | 20180928-145730.214 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:341 | UDP listener is bound to 0.0.0.0:49822

NOTICE | 20180928-145730.214 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:241 | Making TCP connection to [ V4 x.x.x.x:5090 TCP ]

STACK | 20180928-145730.214 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:457 | FdSet timeout = 1000

DEBUG | 20180928-145730.370 | 3CXTunnel | TUNL | 3000 | security.cpp:1114 | Ready to send, send q size = 0

NOTICE | 20180928-145730.370 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:615 | Tunnel connection to [ V4 x.x.x.x:5090 TCP ] is accepted

ALERT | 20180928-145730.370 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:666 | Sending first packet from [ V4 0.0.0.0:49822 UNKNOWN_TRANSPORT ] to [ V4 x.x.x.x:5090 TCP ]

DEBUG | 20180928-145730.370 | 3CXTunnel | TUNL | 3000 | security.cpp:669 | Creating SSL BIO on socket 892

STACK | 20180928-145730.370 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:457 | FdSet timeout = 1000

INFO | 20180928-145730.495 | 3CXTunnel | TUNL | 3000 | security.cpp:1342 | Keep-alive received

STACK | 20180928-145730.495 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:457 | FdSet timeout = 875

WARNING | 20180928-145730.576 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:637 | Tunnel connection to [ V4 x.x.x.x:5090 TCP ] is disconnected; error: Connection is terminated by peer - while begin to read a packet from tunnel

ERR | 20180928-145730.576 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:268 | Bridge [3CXSBC15.5.7503] failure 'Connection is terminated by peer - while begin to read a packet from tunnel' on TCP connection: TunnelTcp::process

NOTICE | 20180928-145730.576 | 3CXTunnel | TUNL | 3000 | TunnelTcp.cpp:580 | === Statistics:
  Keep-alives: recv 1, sent 0
  Transfers:   recv last 81 ms ago,    total 8 bytes
              sent last 206 ms ago,    total 62 bytes
===
WARNING | 20180928-145730.576 | 3CXTunnel | TUNL | 3000 | Bridge.cpp:261 | Tunnel disconnected. Terminating all active calls.

A few pointers would be handy, I am tempted to take the whole setup home and try it from there first as a means of testing on an unfiltered connection. To my knowledge the firewall ports were opened months ago.

 

[oguruma]

I'm a 3CX newbie, so I can't offer any guidance, but I am curious why you don't still use the Raspberry Pi? Were there reliability issues? Or was it not powerful enough of a device for your implementation.

I just set up my system with a Pi, so I am curious about user experiences.

 

[Biathlon]

It would help if I read correctly during installation . Got the new password from the front end, made some progress but still not connecting.

Ending up with:

ALERT | 20181001-091029.454 | 3CXTunnel | TUNL | 824 | TunnelTcp.cpp:666 | Sending first packet from [ V4 0.0.0.0:53105 UNKNOWN_TRANSPORT ] to [ V4 XX.XX.XX.XX:5090 TCP ]

ERR | 20181001-091029.543 | 3CXTunnel | TUNL | 824 | TunnelTcp.cpp:268 | Bridge [3CXSBC15.5.7503] failure 'Connection is terminated by peer - while begin to read a packet from tunnel' on TCP connection: TunnelTcp:rocess

The reason I'm running it on windows, is I don't have a rasppi handy. I've got about 300 windows machines sat around doing nothing. If we put this into the wild, we may use rasp's. The originally used one was someone's personal device to use a proof of concept.

 

[eddv123]

The Raspi variants are solid SBC devices up to 20 extensions so do not worry about reliability.

Ports required for the SBC to connect will be 5090 (for the 3CX tunnel) and 5001 (for provisioning).

I would also ensure that you have tried the connection with the Windows firewall (on the machine hosting the SBC) off.

 

[Biathlon]

It must be the windows machine, I got hold of that Pi for testing, it connects straight away. Windows firewall looks okay, internet firewall must be fine as Pi connects. Obviously something on this windows machine isnt happy.

 

[eddv123]

Turn off (as a test temporarily) Windows firewall, Antivirus software and ensure there are no static routes configured on the Windows machine and go from there.

 

[Biathlon]

Turn off (as a test temporarily) Windows firewall, Antivirus software and ensure there are no static routes configured on the Windows machine and go from there.

Thanks, yeah I've tried that, but something still isn't quite right. I've put TCP view on it, looks like 5060 is allowed outbound.

 

[eddv123]

What about your network - for example the Windows machine - does it pickup a VLAN tag from the network to be on another network - does it pickup a different IP to that of the Pi ?

What do you have set as your default gateway ?

 

[YiannisH_3CX]

Hello @Biathlon

Please navigate to C:\ProgramData\3CXSBC\3cxsbc.conf and make sure that the settings are correct. If option "SecurityMode" is enabled set it to "0" and try again.
Also make sure that options "TunnelAddr" and "PbxSipIP" contain your FQDN and that option "LocalSipAddr" contains the local IP of the SBC. Restart the SBC service after making changes to the config file.