packet timeout log error

VitalPBX Community Support General Discussion packet timeout log error

  • Post
    toxicfusion
    Participant

    Unsure what is causing this. Could be issue from client side, as their phones will not stay connected.  Happening same time as the IVR Loop issue (see other post). Scrambling to find fix.

     

    Packet timed out after 6400ms with no response
    [2019-10-23 16:43:13] WARNING[1656] chan_sip.c: Timeout on 2026245064-897691138-1202476321 on non-critical invite transaction.
    [2019-10-23 16:43:21] WARNING[1656] chan_sip.c: Timeout on 1997083236-1707736611-673989703 on non-critical invite transaction.
    [2019-10-23 16:43:26] WARNING[1656] chan_sip.c: Retransmission timeout reached on transmission 1897545996-5060-82@BJC.BGI.D.BGB for seqno 102 (Critical Request) — See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
    Packet timed out after 6400ms with no response
    [2019-10-23 16:43:28] WARNING[1656] chan_sip.c: Timeout on 356135904-147483397-409121765 on non-critical invite transaction.
    [2019-10-23 16:43:36] WARNING[1656] chan_sip.c: Timeout on 1622140938-1620135275-1996395105 on non-critical invite transaction.
    [2019-10-23 16:43:43] WARNING[1656] chan_sip.c: Timeout on 157997331-1841656359-553199610 on non-critical invite transaction.
    [2019-10-23 16:43:49] WARNING[1656] chan_sip.c: Timeout on 543840414-419285944-31089079 on non-critical invite transaction.
    [2019-10-23 16:43:57] WARNING[1656] chan_sip.c: Timeout on 1157460850-727418388-1287284724 on non-critical invite transaction.
    [2019-10-23 16:43:58] WARNING[1656] chan_sip.c: Retransmission timeout reached on transmission 2016835488-5060-422@BJC.BGI.D.IC for seqno 102 (Critical Request) — See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
    Packet timed out after 6401ms with no response
    [2019-10-23 16:44:03] WARNING[1656] chan_sip.c: Timeout on 987012759-574671042-972542671 on non-critical invite transaction.
    [2019-10-23 16:44:10] WARNING[1656] chan_sip.c: Timeout on 1021861340-1298807737-1942326983 on non-critical invite transaction.

    0
Viewing 6 replies - 16 through 21 (of 21 total)
  • Replies
    toxicfusion
    Participant
    Up
    0
    Down

    Waiting on ISP to replace modem.. Will see if resolves issues

     

    Any other theories? I’ve even disabled firewall-d without any change.  No firewall changes on customers network, no config changes. Internet otherwise seems stable. But if it is a modem config issue; perhaps its causing this.

    0
    Up
    0
    Down

    Use the sngrep tool for monitoring the OPTIONS method, and see if you can get some info about what is happening.

    0
    toxicfusion
    Participant
    Up
    0
    Down

    Update:

    What would cause the hosted PBX OWN public IP to be in the banlist for fail2ban??

    0
    Up
    0
    Down

    @toxicfusion

    This happens when there are massive attacks and the asterisk log shows that the attacks come from your own server, but, I think is a trick that attacker use to avoid being banned.

    You may use the sngrep tool to check if one of the SIP scanners is attacking to your server.

    0
    toxicfusion
    Participant
    Up
    0
    Down

    Where can i set to only allow SIP Traffic from specific WAN addresses?  Unsure how I can do that within VitalPBX

    0
    toxicfusion
    Participant
    Up
    0
    Down

    FYI – I’ve now did a FRESH install of VitalPBX, and took the time to manually re-configure. I recreated all extensions with same passwords, and then all other settings.

     

    same issue, phones go back to unreachable.

     

    At the firewall level, i see the SIP phones establishing and making connection to the hosted PBX

     

    segeng shows the phones as well. Phone traffic from client location/NAT.  Shows as OPTIONS

    0
Viewing 6 replies - 16 through 21 (of 21 total)
  • You must be logged in to reply to this topic.