Failing to get SBC to run on Windows 10

Discussion in '3CX Phone System - General' started by simonog, Mar 31, 2018.

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

    Joined:
    Mar 27, 2018
    Messages:
    16
    Likes Received:
    1
    I have installed SBC on a fully up to date windows 10 machine with firewall turned off.

    ports 5060 and 5090 are forwarded to that machine.

    the network check on the cloud installation of 3CX finds everything is fine.

    the fqdn of my cloud 3CX server returns the right address to nslookup. all 3CX software is latest versions downloaded in the last 4 days (since I started to set the system up).

    yet SBC service on my local LAN refuses to start. this is the (verbose) log file. does anyone have any instant suggestions? I apologise in advance for what is probably a newbie error - but neither google nor some hours of experimenting have fixed it!

    NOTICE | 20180331-155334.666 | 3CXTunnel | TUNL | 6568 | Log.cpp:39 | Log started: type = file, level = VERBOSE
    INFO | 20180331-155334.676 | 3CXTunnel | RESIP:DNS | 6568 | DnsUtil.cxx:170 | local hostname does not contain a domain part OG-Server
    INFO | 20180331-155334.676 | 3CXTunnel | TUNL | 6568 | RPiTunnel.cpp:200 | Local host name: OG-Server
    DEBUG | 20180331-155334.676 | 3CXTunnel | RESIP:TRANSPORT | 6568 | WinCompat.cxx:191 | WinCompat constructor complete!
    NOTICE | 20180331-155334.686 | 3CXTunnel | TUNL | 6568 | Bridge.cpp:1091 | Check:
    Bridge config: [Bridge/123456]
    #Mandatory:
    ID = 123456
    Password = <edited to remove my password>
    TunnelFqdn = ogpbx.3cx.co.uk
    #Optional
    SecurityMode = 1
    ClientsCertificateFile ''
    ClientsPrivateKeyFile ''
    PBX SIP addr = ogpbx.3cx.co.uk:5060
    Name = 3CXSBC15.5.7503
    LocalSipAddr = 172.31.4.102
    LocalSipPort = 5060
    NumRtpPorts = 32
    #===========
    DEBUG | 20180331-155334.686 | 3CXTunnel | RESIP | 6568 | Security.cxx:1075 | BaseSecurity::BaseSecurity
    WARNING | 20180331-155334.976 | 3CXTunnel | RESIP | 6568 | Security.cxx:2966 | unable to load DH parameters (required for PFS): TlsDHParamsFilename not specified
    DEBUG | 20180331-155334.976 | 3CXTunnel | RESIP | 6568 | Security.cxx:3013 | ECDH initialized
    WARNING | 20180331-155334.976 | 3CXTunnel | RESIP | 6568 | Security.cxx:2966 | unable to load DH parameters (required for PFS): TlsDHParamsFilename not specified
    DEBUG | 20180331-155334.976 | 3CXTunnel | RESIP | 6568 | Security.cxx:3013 | ECDH initialized
    INFO | 20180331-155334.976 | 3CXTunnel | RESIP:DNS | 6568 | AresDns.cxx:369 | DNS initialization: found 2 name servers
    INFO | 20180331-155334.976 | 3CXTunnel | RESIP:DNS | 6568 | AresDns.cxx:380 | name server: 10.0.0.1
    INFO | 20180331-155334.976 | 3CXTunnel | RESIP:DNS | 6568 | AresDns.cxx:380 | name server: 8.8.8.8
    DEBUG | 20180331-155334.976 | 3CXTunnel | RESIP | 6568 | Compression.cxx:44 | COMPRESSION SUPPORT NOT COMPILED IN
    DEBUG | 20180331-155334.976 | 3CXTunnel | RESIP | 6568 | Compression.cxx:47 | Compression configuration object created; algorithm = 0
    DEBUG | 20180331-155334.976 | 3CXTunnel | RESIP:TRANSPORT | 6568 | TransportSelector.cxx:99 | No compression library available
    DEBUG | 20180331-155334.976 | 3CXTunnel | RESIP:TRANSPORT | 6568 | InternalTransport.cxx:121 | Creating fd=504 V4/UDP
    DEBUG | 20180331-155334.976 | 3CXTunnel | RESIP:TRANSPORT | 6568 | InternalTransport.cxx:133 | Binding to 172.31.4.102
    INFO | 20180331-155334.976 | 3CXTunnel | RESIP:TRANSPORT | 6568 | Transport.cxx:185 | The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer
    ERR | 20180331-155334.976 | 3CXTunnel | RESIP:TRANSPORT | 6568 | InternalTransport.cxx:148 | Could not bind to [ V4 172.31.4.102:5060 UDP flowKey=504 ]
    DEBUG | 20180331-155334.976 | 3CXTunnel | RESIP | 6568 | BaseException.cxx:21 | BaseException at InternalTransport.cxx:149 Could not use port
    ERR | 20180331-155334.976 | 3CXTunnel | TUNL | 6568 | Bridge.cpp:159 |
    ** Resip exception caught while starting bridge '3CXSBC15.5.7503' (123456)
    ! Exception: Could not use port
     
  2. Saqqara

    Saqqara Well-Known Member

    Joined:
    Mar 12, 2014
    Messages:
    1,147
    Likes Received:
    174
    Start with you do not need any portforwarding for the SBC setup on the router protecting the SBC - so remove these settings.

    On the local IP address have you specified the Win 10 IP address https://www.3cx.com/docs/3cx-sbc-windows/

    Do you have any other software running on port 5060
     
    #2 Saqqara, Mar 31, 2018
    Last edited: Mar 31, 2018
  3. simonog

    Joined:
    Mar 27, 2018
    Messages:
    16
    Likes Received:
    1
    Thank you. That is really helpful - I should have been able to work out that I didn't need port forwarding.

    No other software running on 5060. the SBC is on my local LAN (10.*); 3CX is in the cloud. I found the documentation unclear as to whether one needed the local IP address in the SBC config file to be of the SBC server or of the cloud 3CX on its remote cloud LAN.
     
    #3 simonog, Mar 31, 2018
    Last edited: Mar 31, 2018
  4. simonog

    Joined:
    Mar 27, 2018
    Messages:
    16
    Likes Received:
    1
    Definitely getting much further now. SBC runs - just having an issue getting packets read.
    ALERT | 20180331-171859.213 | 3CXTunnel | TUNL | 16432 | TunnelTcp.cpp:666 | Sending first packet from [ V4 0.0.0.0:60468 UNKNOWN_TRANSPORT ] to [ V4 35.176.47.40:5090 TCP ]
    ERR | 20180331-171859.231 | 3CXTunnel | TUNL | 16432 | 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
     
  5. ivank

    3CX Support

    Joined:
    Jan 4, 2017
    Messages:
    54
    Likes Received:
    6
    simonog, now you need to look into 3CXTunnel.log at PBX side to see why connection breaks.
     
  6. simonog

    Joined:
    Mar 27, 2018
    Messages:
    16
    Likes Received:
    1
    Thank you.

    Is there a way to pull the log from the dashboard? I installed the cloud image on Amazon direct from the excellent 3cx website instructions and set it all up (and it works fine with mobile clients).

    I made the assumption it installed a windows environment and now suspect it's Linux. If so, can anyone kindly point me to something that says where 3cx stores its tunnel log and how I find it if I can't get it from the dashboard?
     
  7. ivank

    3CX Support

    Joined:
    Jan 4, 2017
    Messages:
    54
    Likes Received:
    6
    On Windows, it's in c:\ProgramData\3CX\Instance1\Data\Logs folder (or whatever the system drive is). You should be able to connect via RDP.
    On Linux, you need to use any SSH client to connect. Logs are in /var/lib/3cxpbx/Instance1/Data/Logs
     
  8. simonog

    Joined:
    Mar 27, 2018
    Messages:
    16
    Likes Received:
    1
    Thank you for the locations - I couldn't find that documented anywhere.

    I used the 3cx provided setup procedure for an amazon instance. it gave me no choice of platform - does it use windows or Linux?
     
  9. ivank

    3CX Support

    Joined:
    Jan 4, 2017
    Messages:
    54
    Likes Received:
    6
    It should be Linux.
     
  10. simonog

    Joined:
    Mar 27, 2018
    Messages:
    16
    Likes Received:
    1
    Seems to be Debian Linux thank you. This is the last section of the tunnel log file. Is it clear from here why the SBC session is dropping? I noticed the comment about passwords mismatch yet I cut and pasted the password from the 3cx dashboard into the local sbc conf file.

    Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1439): TimerActions: Removed 20<-::ffff:81.156.39.180:64852:20
    10:19:41.554|7f2864b6a700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/TCPSide.cpp(212): 20<-::ffff:81.156.39.180:64852:20: Destroyed; num.conn=0
    10:19:41.586|7f2861151700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/TCPSide.cpp(195): 21<-::ffff:81.156.39.180:64853:20: Created; num.conn=1
    10:19:41.586|7f2861151700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(859): 21<-::ffff:81.156.39.180:64853:20: Waiting For first packet
    10:19:41.586|7f2864b6a700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1432): TimerActions: Added 21<-::ffff:81.156.39.180:64853:20
    10:19:41.586|7f286636d700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1033): IncomingSlaveUDP: skip to ADD connection 21<-::ffff:81.156.39.180:64853:20. It has no input channel for this handler.
    10:19:41.587|7f286536b700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1295): OutgoingTCP: Added 21<-::ffff:81.156.39.180:64853:20
    10:19:41.587|7f2865b6c700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1048): IncomingTCP: Added 21<-::ffff:81.156.39.180:64853:20
    10:19:41.588|7f2865b6c700|Error|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(788): 21<-::ffff:81.156.39.180:64853:20: Tunnel connection authentication failed! Passwords mismatch. identifying as '3CXSBC15.5.7503'(123456)
    10:19:41.588|7f2865b6c700| Warn|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/Multiplexer.cpp(593): 21<-::ffff:81.156.39.180:64853:20: no tunnel object defined for first packet. Shutdown.
    10:19:41.588|7f2865b6c700|Error|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1188): IncomingTCP: Connection 21<-::ffff:81.156.39.180:64853:20 read failure
    10:19:41.588|7f2865b6c700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1201): IncomingTCP: Removing 21<-::ffff:81.156.39.180:64853:20 . reason - processing failed (closed or failed connection)
    10:19:41.588|7f2865b6c700| Warn|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1109): IncomingTCP: 21<-::ffff:81.156.39.180:64853:20 requested remove
    10:19:41.588|7f2865b6c700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1055): IncomingTCP: Removed 21<-::ffff:81.156.39.180:64853:20
    10:19:41.588|7f286536b700| Warn|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/Multiplexer.cpp(177): Socket 20 got error (32) while writting
    10:19:41.589|7f286536b700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1300): OutgoingTCP: Removed 21<-::ffff:81.156.39.180:64853:20
    10:19:41.589|7f286636d700| Info|/home/repomaster/workspace/15.5SP4/SPBuild/Sources/Projects/Tunnel/SRBridgeProxy/ConnMgr.cpp(1033): IncomingSlaveUDP: skip to DELETE connection 21<-::ffff:81.156.39.180:64853:20. It has no input channel for this handler.
    10:19:41.589|7f2864b6a700|
     
  11. ivank

    3CX Support

    Joined:
    Jan 4, 2017
    Messages:
    54
    Likes Received:
    6
    Tunnel connection authentication failed! Passwords mismatch. identifying as '3CXSBC15.5.7503'(123456)

    Make sure that password set in the Settings/Security/3CXTunnel matches one specified in the SBC config.
     
  12. simonog

    Joined:
    Mar 27, 2018
    Messages:
    16
    Likes Received:
    1
    when I set up SBC on the local machine I copied and pasted the password from the 3cx dashboard settings - security settings - 3cx tunnel into the conf file.
    Is that the right place or do I need to change something else?
     
  13. Saqqara

    Saqqara Well-Known Member

    Joined:
    Mar 12, 2014
    Messages:
    1,147
    Likes Received:
    174
    Manually type the password, as copy and paste may copy hidden / special characters
     
  14. simonog

    Joined:
    Mar 27, 2018
    Messages:
    16
    Likes Received:
    1
    Just done and there is no difference. it still fails the same way.

    I did try to turn off encryption too as that was a problem last year I see. also no difference.

    both 3cx and sbc were downloaded a week ago a day apart so I am assuming there were no incompatibilities between them :(
     
  15. simonog

    Joined:
    Mar 27, 2018
    Messages:
    16
    Likes Received:
    1
    I thought I would try to change the password in both places in case in some way the 3cx version is corrupted. Once I had changed the password, the tunnel connected properly.

    Clearly there was some character in the password on 3cx which was not displaying.

    Now the phones register and I can call a deskphone on the remote LAN from the 3cx client on a mobile. interestingly, however, I get this in the sbc log:
    ERR | 20180402-172622.177 | 3CXTunnel | TUNL | 9912 | Bridge.cpp:712 | Has no registered RTP session for local destination 10.0.0.37:10007
    (repeated another 3 times for a single call).

    This is a series of little hurdles isn't it? :)
     
    #15 simonog, Apr 2, 2018
    Last edited: Apr 2, 2018
Thread Status:
Not open for further replies.