Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

SBC Setup Not Working?

Discussion in '3CX Phone System - General' started by swink, Sep 5, 2015.

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

    Joined:
    Oct 9, 2014
    Messages:
    15
    Likes Received:
    0
    I have am using 7-8 Yealink T-23G's behind a NAT'd firewall to a 3CX server which is NOT behind a NAT'd firewall. I'm not sure the SBC install is setting the config correctly and there isn't much in the way of tools to diagnose. The phones simply will not register. They work fine with STUN except station to station calls on their own LAN. I was hoping SBC would fix this.

    192.168.0.156(T-23G) ---> 192.168.0.10 (Windows Server Running SBC) ----> 64.127.28.1 (3CX Server 12.5)


    My questions: The parameter SecurityMode=0 - what is this and what does it do? I saw someone else post that SBC was incorrectly interpreting #LocalSipAddr=0.0.0.0 and trying to hit the empty set 169.254.x.x.


    Here is the SBC config:

    [Log]
    Type=file # cout, cerr, file, syslog
    File=C:\ProgramData\3CXSBC\Logs\3cxsbc.log
    Level=ERR # NONE", "EMERG", "ALERT", "CRIT", "ERR", "WARNING", "NOTICE", "INFO", "DEBUG", "STACK", "ERR", "VERBOSE"
    [Bridge/123456]
    Name="3CX SBC"
    Password="NunyaBidness"
    ID=123456
    SecurityMode=0
    #LocalSipAddr=0.0.0.0
    #LocalSipPort=5060 # local SIP (UDP/TCP) address (def: 5060)
    TunnelAddr=64.127.28.1
    PbxSipPort=5060
    TunnelPort=5090
    PbxSipIP=64.127.28.1
    [General]
    PrintStatsInterval=30
    ReconnectInterval=30
     
  2. swink

    Joined:
    Oct 9, 2014
    Messages:
    15
    Likes Received:
    0
    Ended up hacking up the .config file manually and this got the phone registered - waiting for someone onsite to test. If this works, I think the 3CX SBC installer is a bit broken and needs reworked - and the parameters for the app are not aptly named. ie LocalSipAddr should be LocalSBCAddr - it makes it a bit more transparent as to what it's doing.

    Michael



    [Log]
    Type=file # cout, cerr, file, syslog
    File=C:\ProgramData\3CXSBC\Logs\3cxsbc.log
    Level=VERBOSE # NONE", "EMERG", "ALERT", "CRIT", "ERR", "WARNING", "NOTI, "INFO", "DEBUG",

    "STACK", "ERR", "VERBOSE"
    [Bridge/123456]
    Name="3CX SBC"
    Password="NunyaBidness"
    ID=123456
    SecurityMode=0
    LocalSipAddr=192.168.0.10
    LocalSipPort=5080 # local SIP (UDP/TCP) address (def: 5060)
    TunnelAddr=64.127.28.1
    PbxSipPort=5060
    TunnelPort=5090
    PbxSipIP=64.127.28.1
    [General]
    PrintStatsInterval=30
    ReconnectInterval=30
     
  3. adrianc

    Joined:
    Sep 4, 2015
    Messages:
    20
    Likes Received:
    0
    I agree, I went through the same learning curve recently too!
    http://www.3cx.com/forums/3cx-sbc-needs-a-vpn-41787.html
     
Thread Status:
Not open for further replies.