SBC Issues

[ben rooke]

Hi Guys

One of our remote clients has chosen to install an SBC on site. ( v16 PBX and software downloaded from site ). The setup was fine and all the information is correct however in the logs they get: ( i have replace the PBX IP with 1.1.1.1 )

ERR | 20190703-112347.201 | 3CXTunnel | TUNL | 9932 | Rtp.cpp:90 | Can not bind RTP socket to 0.0.0.0:63726; error 10048
ERR | 20190703-112347.203 | 3CXTunnel | TUNL | 9932 | Rtp.cpp:90 | Can not bind RTP socket to 0.0.0.0:63728; error 10048
ERR | 20190703-112357.263 | 3CXTunnel | TUNL | 9932 | TunnelTcp.cpp:165 | Failed to resolved DNS SRV record for tunnel connection to rivanet.vcshosted.uk
ERR | 20190703-112407.315 | 3CXTunnel | TUNL | 9932 | TunnelTcp.cpp:184 | Failed to resolve host name rivanet.vcshosted.uk
ERR | 20190703-112407.315 | 3CXTunnel | TUNL | 9932 | TunnelTcp.cpp:232 | Failed to resolve connection FQDN rivanet.vcshosted.uk
ALERT | 20190703-112959.295 | 3CXTunnel | TUNL | 2212 | TunnelTcp.cpp:666 | Sending first packet from [ V4 0.0.0.0:50816 UNKNOWN_TRANSPORT ] to [ V4 1.1.1.1:5090 TCP ]
ALERT | 20190703-113707.687 | 3CXTunnel | TUNL | 2908 | TunnelTcp.cpp:666 | Sending first packet from [ V4 0.0.0.0:50823 UNKNOWN_TRANSPORT ] to [ V4 1.1.1.1:5090 TCP ]
ALERT | 20190703-121247.708 | 3CXTunnel | TUNL | 2996 | TunnelTcp.cpp:666 | Sending first packet from [ V4 0.0.0.0:50874 UNKNOWN_TRANSPORT ] to [ V4 1.1.1.1:5090 TCP ]
ALERT | 20190703-131017.922 | 3CXTunnel | TUNL | 5140 | TunnelTcp.cpp:666 | Sending first packet from [ V4 0.0.0.0:51389 UNKNOWN_TRANSPORT ] to [ V4 1.1.1.1:5090 TCP ]
ALERT | 20190703-133400.065 | 3CXTunnel | TUNL | 4256 | TunnelTcp.cpp:666 | Sending first packet from [ V4 0.0.0.0:51420 UNKNOWN_TRANSPORT ] to [ V4 1.1.1.1:5090 TCP ]
ALERT | 20190703-134617.435 | 3CXTunnel | TUNL | 7536 | TunnelTcp.cpp:666 | Sending first packet from [ V4 0.0.0.0:51436 UNKNOWN_TRANSPORT ] to [ V4 1.1.1.1:5090 TCP ]

I have changed the conf file to use the IP address not the FQDN of the pbx, I can ping the site address and get a response. The DNS settings are set to 8.8.8.8

This is on windows so i even added the information to the hosts file.... ports are open but i just cant figure it out....

 

[AWS2P]

Hi,
you said ports are open, on SBC remote side you just need 5090 UDP/TCP to be open.
pbx FQDN is not resolving from SBC site ?

Is it a completly new windows 10 pro install ? is it dedicated SBC computer?

PBX is Hosted cloud ? on premise ?

 

[ben rooke]

Sorry, Yes i checked all ports necessary so 5090 for the tunnel 5060 for SIP

no this is an existing windows installation, it is currently a test machine that the client wants to ensure we are able to get it working before setting up a VM

PBX is cloud hosted.. he has phoned provisioned at the moment via Stun but we are wanting to encourage the use of the SBC. we have other remote sites with SBC's without an issue.

its v15 of the SBC not the latest under the BETA update.

 

[ben rooke]

i am confused by this however?

Sending first packet from [ V4 0.0.0.0:50874 UNKNOWN_TRANSPORT ] to [ V4 1.1.1.1:5090 TCP ]
Ii have not amended the first IP address on this instance

 

[DSXVOICE]

Hey Ben,

Triple check the config file for the SBC, as that is usually 99% of the reason why there are issues. Best to use IP addresses in the config so as to eliminate DNS issues. Also, temporarily shut down any AV/IDT/IPS services to see if they are interfering. If you DO setup a VM, suggest you use 3CX's Debian ISO - really fast & solid deployment is assured that way.

 

[ben rooke]

Here is a copy of the conf file. again i have replaced the FQDN of the PBX with its IP and displayed here as 1.1.1.1 and the local ip as 2.2.2.2

[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
[General]
FailoverInterval=90
PrintStatsInterval=30
ReconnectInterval=30
[Bridge/123456]
Name=3CXSBC15.5.7503
SecurityMode=0
TunnelAddr=1.1.1.1
Password="kjjhjhlkjhlhj"
ID=123456
LocalSipAddr=2.2.2.2
LocalSipPort=5060
PbxSipIP=1.1.1.1
PbxSipPort=5060
TunnelPort=5090

 

[DSXVOICE]

Tnx Ben - (un) fortunately, even after 4 checks, that looks operational. So much for a simple answer. The log errors really look like a DNS issue is happening - it looks like rivanet.vcshosted.uk is not resolving. Can you do a ping etc from the SBC host machine? After replacing the URL - what errors are in the log now?

 

[ben rooke]

I am able to ping the url which is the odd thing... and to make things worse the exact same error is coming up after amending the conf file and restarting..... its driving me round the bend...

 

[AWS2P]

I have dns answer on from my french location.

Did you solved SBC problem, now you have new SBC release with v16 SP2 ?