Drop Inbound calls from SIP Trunk

Discussion in '3CX Phone System - General' started by orlando2606, Dec 11, 2015.

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

    Joined:
    Aug 13, 2015
    Messages:
    5
    Likes Received:
    0
    Hi all I am getting drop calls from my SIP Trunk Provider and I can seem to figure out the problem here are some logs from the 3CX system and wire shark can someone please help


    10-Dec-2015 21:35:17.353 Leg L:80.1[Line:10002<<5926244587] is terminated: Cause: BYE from PBX
    10-Dec-2015 21:34:45.250 [CM503007]: Call(C:80): Line:10002<<5926244587 has joined, contact <sip:17187959380@81.201.82.45:5060>
    10-Dec-2015 21:34:45.246 L:80.2[Extn] has joined to L:80.1[Line:10002<<5926244587]
    10-Dec-2015 21:34:41.607 [CM503025]: Call(C:80): Calling T:Extn:115@[Dev:sip:115@192.168.1.105:5065,Dev:sip:115@192.168.1.105:1024] for L:80.1[Line:10002<<5926244587]
    10-Dec-2015 21:34:41.599 [CM503025]: Call(C:80): Calling T:Extn:115@[Dev:sip:115@192.168.1.105:5065,Dev:sip:115@192.168.1.105:1024] for L:80.1[Line:10002<<5926244587]
    10-Dec-2015 21:34:41.578 [CM503027]: Call(C:80): From: Line:10002<<5926244587 ("Voxbone:Rogers, Orlando" <sip:5926244587@voip.xxxxxxx.xxx:5065>) to T:Extn:115@[Dev:sip:115@192.168.1.105:5065,Dev:sip:115@192.168.1.105:1024]
    10-Dec-2015 21:34:41.578 [CM503004]: Call(C:80): Route 1: from L:80.1[Line:10002<<5926244587] to T:Extn:115@[Dev:sip:115@192.168.1.105:5065,Dev:sip:115@192.168.1.105:1024]
    10-Dec-2015 21:34:41.574 [CM503001]: Call(C:80): Incoming call from Line:10002<<5926244587 to <sip:115@192.168.168.57:5065>
    10-Dec-2015 21:34:41.574 Line limit check: Current # of calls for line Lc:10002(@Voxbone[<sip:17187959380@81.201.xx.xx:5060>]) is 1; limit is 3
    10-Dec-2015 21:34:41.567 [CM503012]: Inbound out-of-office hours rule (Voxbone) for 10002 forwards to DN:115

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

    186500 2139.949506000 81.201.82.45 192.168.168.57 SIP/SDP 958 Request: INVITE sip:17187959380@190.108.212.11:5065 |
    186505 2140.085639000 192.168.168.57 81.201.82.45 SIP 423 Status: 100 Trying |
    186517 2140.234318000 192.168.168.57 81.201.82.45 SIP 573 Status: 180 Ringing |
    186647 2143.639788000 192.168.168.57 81.201.82.45 SIP/SDP 1014 Status: 200 OK |
    186695 2143.895298000 81.201.82.45 192.168.168.57 SIP 609 Request: ACK sip:17187959380@190.108.212.11:5060 |
    186696 2143.895381000 192.168.168.57 81.201.82.45 ICMP 590 Destination unreachable (Port unreachable)
    186778 2144.267358000 192.168.168.57 81.201.82.45 SIP/SDP 1014 Status: 200 OK |
    186836 2144.514863000 81.201.82.45 192.168.168.57 SIP 609 Request: ACK sip:17187959380@190.108.212.11:5060 |
    187029 2145.285820000 192.168.168.57 81.201.82.45 SIP/SDP 1014 Status: 200 OK |
    187081 2145.541876000 81.201.82.45 192.168.168.57 SIP 609 Request: ACK sip:17187959380@190.108.212.11:5060 |
    187082 2145.541950000 192.168.168.57 81.201.82.45 ICMP 590 Destination unreachable (Port unreachable)
    187565 2147.317515000 192.168.168.57 81.201.82.45 SIP/SDP 1014 Status: 200 OK |
    187641 2147.571910000 81.201.82.45 192.168.168.57 SIP 609 Request: ACK sip:17187959380@190.108.212.11:5060 |
    187642 2147.571995000 192.168.168.57 81.201.82.45 ICMP 590 Destination unreachable (Port unreachable)
    188981 2151.385442000 192.168.168.57 81.201.82.45 SIP/SDP 1014 Status: 200 OK |
    189052 2151.640854000 81.201.82.45 192.168.168.57 SIP 609 Request: ACK sip:17187959380@190.108.212.11:5060 |
    189053 2151.640947000 192.168.168.57 81.201.82.45 ICMP 590 Destination unreachable (Port unreachable)
    190571 2155.439552000 192.168.168.57 81.201.82.45 SIP/SDP 1014 Status: 200 OK |
    190643 2155.684618000 81.201.82.45 192.168.168.57 SIP 609 Request: ACK sip:17187959380@190.108.212.11:5060 |
    190644 2155.684702000 192.168.168.57 81.201.82.45 ICMP 590 Destination unreachable (Port unreachable)
    191650 2159.384710000 192.168.168.57 81.201.82.45 SIP/SDP 1014 Status: 200 OK |
    191706 2159.639373000 81.201.82.45 192.168.168.57 SIP 609 Request: ACK sip:17187959380@190.108.212.11:5060 |
    191707 2159.639445000 192.168.168.57 81.201.82.45 ICMP 590 Destination unreachable (Port unreachable)
    192716 2163.535866000 192.168.168.57 81.201.82.45 SIP/SDP 1014 Status: 200 OK |
    192782 2163.789821000 81.201.82.45 192.168.168.57 SIP 609 Request: ACK sip:17187959380@190.108.212.11:5060 |
    192783 2163.789905000 192.168.168.57 81.201.82.45 ICMP 590 Destination unreachable (Port unreachable)
    193855 2167.681012000 192.168.168.57 81.201.82.45 SIP/SDP 1014 Status: 200 OK |
    193940 2167.932215000 81.201.82.45 192.168.168.57 SIP 609 Request: ACK sip:17187959380@190.108.212.11:5060 |
    193941 2167.932292000 192.168.168.57 81.201.82.45 ICMP 590 Destination unreachable (Port unreachable)
    195143 2171.764451000 192.168.168.57 81.201.82.45 SIP/SDP 1014 Status: 200 OK |
    195263 2172.013194000 81.201.82.45 192.168.168.57 SIP 609 Request: ACK sip:17187959380@190.108.212.11:5060 |
    195264 2172.013286000 192.168.168.57 81.201.82.45 ICMP 590 Destination unreachable (Port unreachable)
    196536 2175.813523000 192.168.168.57 81.201.82.45 SIP 537 Request: BYE sip:5926244587@81.201.82.107:5060;transport=udp |
    196574 2176.067126000 81.201.82.45 192.168.168.57 SIP 374 Status: 200 OK |
     
  2. andreaschr

    andreaschr Support Team
    Staff Member 3CX Support

    Joined:
    Oct 26, 2015
    Messages:
    93
    Likes Received:
    6
    Hi ,

    As i can see from the logs

    ICMP 590 Destination unreachable (Port unreachable)

    The PBX can not contact the 190.108.212.11 .

    So the issue it should be to Your Voip Provider or your ISP
     
  3. orlando2606

    Joined:
    Aug 13, 2015
    Messages:
    5
    Likes Received:
    0
    Hi,

    The 190.108.212.xx address is the public IP of the PBX and it can be ping from with in the PBX
     
  4. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    2,978
    Likes Received:
    183
    perhaps give STUN a try.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.