Outbound Rules not working correctly

Discussion in '3CX Phone System - General' started by cellfreedom, Apr 12, 2010.

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

    Joined:
    Apr 12, 2010
    Messages:
    1
    Likes Received:
    0
    Hi everyone,

    I have 3cx setup and is working great, but I'm having a minor annoying problem.

    I have 3 DIDs (with 2 different VOIP providers, 1 with VOIP.ms and the other two with Unlimitel.) Calls work in and out from both perfectly when I leave generic outbound rules.
    [​IMG]

    The problem lies when I try to set a custom dialing rule, so that I can use a specific trunk based on the prefix.
    [​IMG]

    What ends up happening is the number at the end gets deleted, example:
    If I dial
    it deletes the last digit (2) and not the first (8) whereby attempting to dial
    instead of
     
  2. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Hi,

    Welcome to the forums.

    Kindly take a few minutes of your time to read the forums rules, regarding requesting for help.

    This time I have changed your title and will explain the steps necessary for you to take so users may Assist you. Although you have posted screenshots, it is very hard to see the issue without verbose logs. Kindly set your system into verbose logging. You can do this from the management console> Settings > Advances > "logging level" set to "verbose". Recreate the call allowing it to fail using your rules and post the entire log in the server activity log. If you are unsure of what part to post, post it all and I will edit away the unnecessary part.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. archie

    archie Well-Known Member
    3CX Support

    Joined:
    Aug 18, 2006
    Messages:
    1,299
    Likes Received:
    0
    Do not put comma (,) in your dial. It is not allowed
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.