3cx SBC not working PLEASE help

Discussion in '3CX Phone System - General' started by djboxny, Nov 14, 2016.

Thread Status:
Not open for further replies.
  1. djboxny

    Joined:
    Aug 8, 2010
    Messages:
    42
    Likes Received:
    0
    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::process
    ERR | 20161114-131307.676 | 3CXTunnel | TUNL | 4624 | Bridge.cpp:755 | Tunnel is not connected! SIP message is not sent: SipReq: REGISTER xxxxxx.3cx.us:5060 tid=513674871 cseq=18 REGISTER contact=102@10.0.0.30:5063 / 18 from(wire)
    ALERT | 20161114-131321.770 | 3CXTunnel | TUNL | 4624 | TunnelTcp.cpp:583 | Sending first packet from [ V4 0.0.0.0:52018 UNKNOWN_TRANSPORT ] to [ V4 XXX.XXX.XXX.XXX:5090 TCP ]
    ERR | 20161114-131321.847 | 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::process

    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
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,371
    Likes Received:
    230
    If you run the Firewall Checker on the PBX, does it pass on all ports?
     
  3. djboxny

    Joined:
    Aug 8, 2010
    Messages:
    42
    Likes Received:
    0
  4. IT Hamster

    Joined:
    May 21, 2015
    Messages:
    43
    Likes Received:
    0
    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.
     
  5. djboxny

    Joined:
    Aug 8, 2010
    Messages:
    42
    Likes Received:
    0
    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
     
  6. deanril@yahoo.com

    Joined:
    Oct 27, 2016
    Messages:
    51
    Likes Received:
    1
    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.
     
  7. djboxny

    Joined:
    Aug 8, 2010
    Messages:
    42
    Likes Received:
    0
    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
     
  8. pchiappisi

    Joined:
    Nov 16, 2016
    Messages:
    1
    Likes Received:
    0
    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?
     
  9. IT Hamster

    Joined:
    May 21, 2015
    Messages:
    43
    Likes Received:
    0
    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.
     
  10. djboxny

    Joined:
    Aug 8, 2010
    Messages:
    42
    Likes Received:
    0
    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
     
  11. IT Hamster

    Joined:
    May 21, 2015
    Messages:
    43
    Likes Received:
    0
    Can you enable Verbose Logging on your SBC and then restart the service then post the errors here for me to look at?
     
  12. djboxny

    Joined:
    Aug 8, 2010
    Messages:
    42
    Likes Received:
    0
    How would i do that, enable verbose
     
  13. djboxny

    Joined:
    Aug 8, 2010
    Messages:
    42
    Likes Received:
    0
    In the config file?
     
  14. IT Hamster

    Joined:
    May 21, 2015
    Messages:
    43
    Likes Received:
    0
    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.
     
  15. djboxny

    Joined:
    Aug 8, 2010
    Messages:
    42
    Likes Received:
    0
    replace my FQDN with fqdn.wan.3cx.us
    Replace my WAN ip on the server with wan.ip.my.server

    here is the debug

    NOTICE | 20161123-005614.098 | 3CXTunnel | TUNL | 5932 | Log.cpp:35 | Log started: type = file, level = ERR,DEBUG
    INFO | 20161123-005614.112 | 3CXTunnel | RESIP:DNS | 5932 | DnsUtil.cxx:170 | local hostname does not contain a domain part Richard-PC
    INFO | 20161123-005614.112 | 3CXTunnel | TUNL | 5932 | RPiTunnel.cpp:161 | Local host name: Richard-PC
    NOTICE | 20161123-005614.112 | 3CXTunnel | TUNL | 5932 | Bridge.cpp:1061 | Check:
    Bridge config: [Bridge/123456]
    #Mandatory:
    ID = 123456
    Password = 137W141st_
    TunnelFqdn = fqdn.wan.3cx.us

    #Optional
    SecurityMode = 1
    ClientsCertificateFile ''
    ClientsPrivateKeyFile ''
    PBX SIP addr = fqdn.wan.3cx.us:5060
    Name = 3CXSBC15.0.56341
    LocalSipAddr = 10.0.0.6
    LocalSipPort = 5060
    NumRtpPorts = 8
    #===========

    DEBUG | 20161123-005614.113 | 3CXTunnel | RESIP | 5932 | Security.cxx:1075 | BaseSecurity::BaseSecurity
    WARNING | 20161123-005614.292 | 3CXTunnel | RESIP | 5932 | Security.cxx:2966 | unable to load DH parameters (required for PFS): TlsDHParamsFilename not specified
    DEBUG | 20161123-005614.293 | 3CXTunnel | RESIP | 5932 | Security.cxx:3023 | ECDH initialized
    WARNING | 20161123-005614.294 | 3CXTunnel | RESIP | 5932 | Security.cxx:2966 | unable to load DH parameters (required for PFS): TlsDHParamsFilename not specified
    DEBUG | 20161123-005614.294 | 3CXTunnel | RESIP | 5932 | Security.cxx:3023 | ECDH initialized
    INFO | 20161123-005614.300 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:369 | DNS initialization: found 5 name servers
    INFO | 20161123-005614.300 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:380 | name server: 8.8.8.8
    INFO | 20161123-005614.300 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:380 | name server: 4.4.4.4
    INFO | 20161123-005614.300 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:380 | name server: 192.168.13.1
    INFO | 20161123-005614.300 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:380 | name server: 196.3.81.5
    INFO | 20161123-005614.300 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:380 | name server: 200.88.127.22
    DEBUG | 20161123-005614.300 | 3CXTunnel | RESIP | 5932 | Compression.cxx:44 | COMPRESSION SUPPORT NOT COMPILED IN
    DEBUG | 20161123-005614.300 | 3CXTunnel | RESIP | 5932 | Compression.cxx:47 | Compression configuration object created; algorithm = 0
    DEBUG | 20161123-005614.300 | 3CXTunnel | RESIP:TRANSPORT | 5932 | TransportSelector.cxx:99 | No compression library available
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=560 V4/UDP
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:133 | Binding to 10.0.0.6
    INFO | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | UdpTransport.cxx:54 | Creating UDP transport host=10.0.0.6 port=5060 ipv4=1
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | UdpTransport.cxx:68 | No compression library available: Transport: [ V4 10.0.0.6:5060 UDP flowKey=560 ] on 10.0.0.6
    NOTICE | 20161123-005614.301 | 3CXTunnel | TUNL | 5932 | Bridge.cpp:47 | Main local UDP transport is bound to 10.0.0.6:5060
    NOTICE | 20161123-005614.301 | 3CXTunnel | TUNL | 5932 | Bridge.cpp:63 | SIP UDP transport on 10.0.0.6:5060 is joined to multicast group 224.0.1.75
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP | 5932 | SipStack.cxx:678 | Adding domain alias: 10.0.0.6:5060
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | TransportSelector.cxx:221 | Adding transport: [ V4 10.0.0.6:5060 UDP transportKey=1 ]
    INFO | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | TransportSelector.cxx:293 | TransportSelector::addTransport: added transport for tuple=[ V4 10.0.0.6:5060 UDP transportKey=1 ], key=1
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=564 V4/UDP
    NOTICE | 20161123-005614.301 | 3CXTunnel | TUNL | 5932 | Rtp.cpp:104 | RTP socket 564 is bound to 0.0.0.0:58082
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=568 V4/UDP
    NOTICE | 20161123-005614.301 | 3CXTunnel | TUNL | 5932 | Rtp.cpp:104 | RTP socket 568 is bound to 0.0.0.0:58084
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=572 V4/UDP
    NOTICE | 20161123-005614.301 | 3CXTunnel | TUNL | 5932 | Rtp.cpp:104 | RTP socket 572 is bound to 0.0.0.0:58086
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=576 V4/UDP
    NOTICE | 20161123-005614.301 | 3CXTunnel | TUNL | 5932 | Rtp.cpp:104 | RTP socket 576 is bound to 0.0.0.0:58088
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=580 V4/UDP
    NOTICE | 20161123-005614.301 | 3CXTunnel | TUNL | 5932 | Rtp.cpp:104 | RTP socket 580 is bound to 0.0.0.0:58090
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=584 V4/UDP
    NOTICE | 20161123-005614.301 | 3CXTunnel | TUNL | 5932 | Rtp.cpp:104 | RTP socket 584 is bound to 0.0.0.0:58092
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=588 V4/UDP
    NOTICE | 20161123-005614.301 | 3CXTunnel | TUNL | 5932 | Rtp.cpp:104 | RTP socket 588 is bound to 0.0.0.0:58094
    DEBUG | 20161123-005614.301 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=592 V4/UDP
    NOTICE | 20161123-005614.301 | 3CXTunnel | TUNL | 5932 | Rtp.cpp:104 | RTP socket 592 is bound to 0.0.0.0:58096
    DEBUG | 20161123-005614.302 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=624 V4/TCP
    DEBUG | 20161123-005614.302 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:133 | Binding to 0.0.0.0
    NOTICE | 20161123-005614.306 | 3CXTunnel | TUNL | 5932 | TunnelTcp.cpp:103 | TCP socket (624) is created and bound to [ V4 0.0.0.0:63862 UNKNOWN_TRANSPORT ]

    MAC=FC:AA:14:97:B9:9F; MAC hash = 2776813919
    DEBUG | 20161123-005614.306 | 3CXTunnel | RESIP:TRANSPORT | 5932 | InternalTransport.cxx:121 | Creating fd=628 V4/UDP
    NOTICE | 20161123-005614.306 | 3CXTunnel | TUNL | 5932 | TunnelTcp.cpp:154 | UDP listener is bound to 0.0.0.0:63862
    NOTICE | 20161123-005614.306 | 3CXTunnel | TUNL | 5932 | Bridge.cpp:131 | Tunnel host unique ID=sbc.a582d15f
    NOTICE | 20161123-005614.306 | 3CXTunnel | TUNL | 5932 | TunnelTcp.cpp:173 | Trying to resolve tunnel connection to destination's FQDN fqdn.wan.3cx.us
    INFO | 20161123-005614.309 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:369 | DNS initialization: found 5 name servers
    INFO | 20161123-005614.309 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:380 | name server: 8.8.8.8
    INFO | 20161123-005614.309 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:380 | name server: 4.4.4.4
    INFO | 20161123-005614.309 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:380 | name server: 192.168.13.1
    INFO | 20161123-005614.309 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:380 | name server: 196.3.81.5
    INFO | 20161123-005614.309 | 3CXTunnel | RESIP:DNS | 5932 | AresDns.cxx:380 | name server: 200.88.127.22
    INFO | 20161123-005614.309 | 3CXTunnel | TUNL | 5932 | Dns.cpp:7 | [DNS] Resolving SRV records for _3cxtunnel._tcp.fqdn.wan.3cx.us
    DEBUG | 20161123-005614.379 | 3CXTunnel | RESIP:DNS | 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:DNS | 5932 | DnsStub.cxx:49 | fqdn.wan.3cx.us(A)--> wan.ip.my.server
    DEBUG | 20161123-005614.443 | 3CXTunnel | TUNL | 5932 | Dns.cpp:149 | [DNS] Got DNS A result for fqdn.wan.3cx.us: status = 0
    INFO | 20161123-005614.443 | 3CXTunnel | TUNL | 5932 | Dns.cpp:123 | [DNS] Resolved host name fqdn.wan.3cx.us to [wan.ip.my.server]
    NOTICE | 20161123-005614.443 | 3CXTunnel | TUNL | 5932 | TunnelTcp.cpp:268 | Making TCP connection to [ V4 wan.ip.my.server:5090 TCP ]
    DEBUG | 20161123-005614.518 | 3CXTunnel | TUNL | 6000 | security.cpp:1072 | Ready to send, send q size = 0
    NOTICE | 20161123-005614.518 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:532 | Tunnel connection to [ V4 wan.ip.my.server:5090 TCP ] is accepted
    ALERT | 20161123-005614.518 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:583 | Sending first packet from [ V4 0.0.0.0:63862 UNKNOWN_TRANSPORT ] to [ V4 wan.ip.my.server:5090 TCP ]
    DEBUG | 20161123-005614.526 | 3CXTunnel | TUNL | 6000 | security.cpp:626 | Creating SSL BIO on socket 624
    NOTICE | 20161123-005614.526 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:680 | Sending keep-alive. Stats: KA sent: 1, KA recv: 0
    NOTICE | 20161123-005614.527 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:498 | === Statistics:
    Keep-alives: recv 0, sent 1
    Transfers: recv last 75 ms ago, total 0 bytes
    sent last 18446744073709551608 ms ago, total 63 bytes
    ===
    INFO | 20161123-005614.594 | 3CXTunnel | TUNL | 6000 | security.cpp:1299 | Keep-alive received
    DEBUG | 20161123-005614.971 | 3CXTunnel | TUNL | 6000 | security.cpp:1264 | Packet of 4 bytes is received and put in recvQ, qsize=1
    WARNING | 20161123-005614.971 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:554 | Tunnel connection to [ V4 wan.ip.my.server:5090 TCP ] is disconnected; error: Connection is terminated by peer - while begin to read a packet from tunnel
    ERR | 20161123-005614.971 | 3CXTunnel | TUNL | 6000 | 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::process
    NOTICE | 20161123-005614.971 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:498 | === Statistics:
    Keep-alives: recv 1, sent 1
    Transfers: recv last 0 ms ago, total 16 bytes
    sent last 445 ms ago, total 63 bytes
    ===
    WARNING | 20161123-005614.971 | 3CXTunnel | TUNL | 6000 | Bridge.cpp:243 | Tunnel disconnected. Terminating all active calls.
    NOTICE | 20161123-005614.971 | 3CXTunnel | TUNL | 6000 | Bridge.cpp:353 | Unknown packet: signature = DROP
    DEBUG | 20161123-005614.971 | 3CXTunnel | TUNL | 6000 | Bridge.cpp:354 | Dump:

    --------

    0000: 44 52 4F 50 DROP


    DEBUG | 20161123-005614.971 | 3CXTunnel | RESIP:TRANSPORT | 6000 | InternalTransport.cxx:121 | Creating fd=628 V4/TCP
    DEBUG | 20161123-005614.971 | 3CXTunnel | RESIP:TRANSPORT | 6000 | InternalTransport.cxx:133 | Binding to 0.0.0.0
    NOTICE | 20161123-005614.974 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:103 | TCP socket (628) is created and bound to [ V4 0.0.0.0:63863 UNKNOWN_TRANSPORT ]

    MAC=FC:AA:14:97:B9:9F; MAC hash = 2776813919
    DEBUG | 20161123-005614.974 | 3CXTunnel | RESIP:TRANSPORT | 6000 | InternalTransport.cxx:121 | Creating fd=692 V4/UDP
    NOTICE | 20161123-005614.974 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:154 | UDP listener is bound to 0.0.0.0:63863
    NOTICE | 20161123-005614.974 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:173 | Trying to resolve tunnel connection to destination's FQDN fqdn.wan.3cx.us
    INFO | 20161123-005614.974 | 3CXTunnel | TUNL | 6000 | Dns.cpp:7 | [DNS] Resolving SRV records for _3cxtunnel._tcp.fqdn.wan.3cx.us
    DEBUG | 20161123-005614.975 | 3CXTunnel | RESIP:DNS | 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:DNS | 6000 | DnsStub.cxx:49 | fqdn.wan.3cx.us(A)--> wan.ip.my.server
    DEBUG | 20161123-005614.975 | 3CXTunnel | TUNL | 6000 | Dns.cpp:149 | [DNS] Got DNS A result for fqdn.wan.3cx.us: status = 0
    INFO | 20161123-005614.975 | 3CXTunnel | TUNL | 6000 | Dns.cpp:123 | [DNS] Resolved host name fqdn.wan.3cx.us to [wan.ip.my.server]
    NOTICE | 20161123-005614.975 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:268 | Making TCP connection to [ V4 wan.ip.my.server:5090 TCP ]
    DEBUG | 20161123-005615.051 | 3CXTunnel | TUNL | 6000 | security.cpp:1072 | Ready to send, send q size = 0
    NOTICE | 20161123-005615.051 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:532 | Tunnel connection to [ V4 wan.ip.my.server:5090 TCP ] is accepted
    ALERT | 20161123-005615.051 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:583 | Sending first packet from [ V4 0.0.0.0:63863 UNKNOWN_TRANSPORT ] to [ V4 wan.ip.my.server:5090 TCP ]
    DEBUG | 20161123-005615.059 | 3CXTunnel | TUNL | 6000 | security.cpp:626 | Creating SSL BIO on socket 628
    NOTICE | 20161123-005615.059 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:680 | Sending keep-alive. Stats: KA sent: 1, KA recv: 0
    INFO | 20161123-005616.088 | 3CXTunnel | TUNL | 6000 | security.cpp:1299 | Keep-alive received
    DEBUG | 20161123-005616.088 | 3CXTunnel | TUNL | 6000 | security.cpp:1264 | Packet of 4 bytes is received and put in recvQ, qsize=1
    NOTICE | 20161123-005616.088 | 3CXTunnel | TUNL | 6000 | Bridge.cpp:353 | Unknown packet: signature = DROP
    DEBUG | 20161123-005616.088 | 3CXTunnel | TUNL | 6000 | Bridge.cpp:354 | Dump:

    --------

    0000: 44 52 4F 50 DROP


    WARNING | 20161123-005616.092 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:554 | Tunnel connection to [ V4 wan.ip.my.server:5090 TCP ] is disconnected; error: Connection is terminated by peer - while begin to read a packet from tunnel
    ERR | 20161123-005616.092 | 3CXTunnel | TUNL | 6000 | 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::process
    NOTICE | 20161123-005616.092 | 3CXTunnel | TUNL | 6000 | TunnelTcp.cpp:498 | === Statistics:
    Keep-alives: recv 1, sent 1
    Transfers: recv last 4 ms ago, total 16 bytes
    sent last 1033 ms ago, total 63 bytes
    ===
    WARNING | 20161123-005616.092 | 3CXTunnel | TUNL | 6000 | Bridge.cpp:243 | Tunnel disconnected. Terminating all active calls.
     
  16. deanril@yahoo.com

    Joined:
    Oct 27, 2016
    Messages:
    51
    Likes Received:
    1
    Here is my config:

    Mine is working is V15
     
  17. deanril@yahoo.com

    Joined:
    Oct 27, 2016
    Messages:
    51
    Likes Received:
    1
    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...
     
  18. djboxny

    Joined:
    Aug 8, 2010
    Messages:
    42
    Likes Received:
    0
    I thinks its that. Because its the free version. Can someone comfirm this please
     
  19. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,443
    Likes Received:
    282
    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
     
  20. djboxny

    Joined:
    Aug 8, 2010
    Messages:
    42
    Likes Received:
    0
    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::process
    ALERT | 20161124-234940.958 | 3CXTunnel | TUNL | 4152 | TunnelTcp.cpp:660 | Sending first packet from [ V4 0.0.0.0:56310 UNKNOWN_TRANSPORT ] to [ V4 wan.ip.xx.xxx:5090 TCP ]
    ERR | 20161124-234941.977 | 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::process
     
Thread Status:
Not open for further replies.