SBC phones losing registration

Discussion in '3CX Phone System - General' started by fireflyuk, Jan 5, 2017.

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

    Joined:
    May 17, 2012
    Messages:
    4
    Likes Received:
    0
    I've searched but can't find anything :-(

    I have a v15 (Win Box) PBX hostied in the cloud with a handfull of extensions in two offices, all Yealink T23Gs.

    Both offices have identical SBC versions (v15) and configs however every now and then and without rhyme or reason, extensions in Office A randomly lose their registration from the PBX.

    When logging on to each phone in Office A, the phones all say they are registered (to the SBC presumably).

    Office B appears unnaffected.

    Office A has a good Draytek router, SIP ALG disabled, firewall rules identical to Office B.

    All handset FW versions are the same (44.80.0.130)

    Nothing obvious showing in the SBC logs, this is an extract from around the time it last happened when only a single extension decided to go away;

    -----------------------------------
    ERR | 20170105-112800.698 | 3CXTunnel | TUNL | 4568 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:53636}: error 10054
    ERR | 20170105-112800.744 | 3CXTunnel | TUNL | 4568 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:53636}: error 10054
    ERR | 20170105-112800.744 | 3CXTunnel | TUNL | 4568 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:53636}: error 10054
    ERR | 20170105-112800.744 | 3CXTunnel | TUNL | 4568 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:53636}: error 10054
    ERR | 20170105-112800.760 | 3CXTunnel | TUNL | 4568 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:53636}: error 10054
    ERR | 20170105-112800.807 | 3CXTunnel | TUNL | 4568 | Rtp.cpp:143 | Error reading from RTP socket 456, {RS:53636}: error 10054

    -----------------------------------


    Thanks in advance for any thoughts.
     
  2. GiannosC_3CX

    GiannosC_3CX Guest

    Dear Fireflyuk,

    Please check again the firewall rules on Office A if it permits the outbound connection to the cloud PBX and vice versa. Then check the 3cxsbc.conf file on the LocalSipAddr value if it has local SBC IP Address and is not commented out (remove #). Also please ensure that you are using the latest version of SBC.
     
  3. SHREK

    Joined:
    Feb 22, 2017
    Messages:
    3
    Likes Received:
    0
    3CXTunnel | TUNL | 3152 | Rtp.cpp:143 | Error reading from RTP socket 584, {RS:55084}: error 10054
    We are showing the same issues here as well
     
  4. GiannosC_3CX

    GiannosC_3CX Guest

    Hi shrek,

    Please let us know what kind of SBC are you using? (Linux/Windows)
    Also please let us know what version of SBC are you on and what version of 3cx Phone system?
     
  5. SHREK

    Joined:
    Feb 22, 2017
    Messages:
    3
    Likes Received:
    0
    We are using Windows v14 SBC to a multitenant v14 hosted platform running win2012svr at a colo site.


    [Bridge/123456]
    Name=3CXSBC14.0.48426.61
    ID=123456
    #LocalSipPort=5060
    #LocalSipAddr=0.0.0.0
    Password=removed
    PbxSipPort=10060
    PbxSipIP=removed
    SecurityMode=1
    TunnelAddr=removed
    TunnelPort=10090
    [General]
    FailoverInterval=90
    PrintStatsInterval=30
    ReconnectInterval=30
    [Log]
    Type=file # cout, cerr, file, syslog
    File=C:\ProgramData\3CXSBC\Logs\3cxsbc.log
    Level=ERR # "ERR", "NONE", "EMERG", "ALERT", "CRIT", "ERR", "WARNING", "NOTICE", "INFO", "DEBUG", "STACK", "ERR", "VERBOSE"
     
  6. GiannosC_3CX

    GiannosC_3CX Guest

    Hi shrek,

    Could you please un-comment #LocalSipPort=5060 #LocalSipAddr=0.0.0.0 and on LocalSipAddr type you SBC IP Address. Also, on Level=ERR please change with Level=VERBOSE.
    Please restart your SBC and let us know if the issue persists.
     
Thread Status:
Not open for further replies.