SIP Trunk Vitelity Busy Signal

Discussion in '3CX Phone System - General' started by Irishtech, Dec 23, 2013.

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

    Joined:
    Dec 23, 2013
    Messages:
    1
    Likes Received:
    0
    I have a 3cx system set up behind a SonicWall TZ200 with all necessary ports forwarded. I have keep alives enabled on the 3cx system. I have set the TCP and UDP timeout time to a reasonable number. Everything will be working fine and then randomly when dialing in a user will get a busy signal, hang up and redial and call goes right through. Log never shows that a failure has occurred, but the CDR states that the line was indeed busy. Nobody will be on the line, internal or external when this behavior occurs. Has anyone else seen anything like this?
     
  2. sigma1

    sigma1 Active Member

    Joined:
    Nov 20, 2009
    Messages:
    542
    Likes Received:
    1
    A packet capture from the server would help much. wireshark.org
    Alternatively, what does the log say? If it makes it on the report the log would help.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. active5

    Joined:
    Jun 28, 2011
    Messages:
    72
    Likes Received:
    0
    I've seen this before with Vitelity, it has usually been a firewall issue. The packets don't get to the 3CX server before Vitelity determines the call was rejected. If you have the Vitelity number configured for failover you will see the call transferred to the failover connection instead of a busy signal.

    I'm guessing you will see the traffic coming to the router from Vitelity (if Sonicwall can let you see packets like MikroTik RouterOS) but then you will not see traffic hitting the 3CX server from the router. The call fails at the router.

    I solved this by using MikroTik routers and dumping the rest. All my Voip WAN connections are now running exclusively with MikroTik RouterOS.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.