Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Help with config of a Sangoma on NTL business to the 3cx

Discussion in '3CX Phone System - General' started by dslgroup, Jul 14, 2009.

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

    Jun 13, 2009
    Likes Received:

    I hope some one can help me; I am new to the 3cx software I have been trying to config this to run on NTL business if I set the Sangoma A101 card to

    Config used on the card setup by using the quick setup on the netborder express v2.0 software

    Board: A101
    County: USA (if set to the UK the line will not come up)

    Interface Type: E1
    Framing Type: CRC4
    Encoding Type: HDB3
    ISDN Switch Variant: Nete5 (ETS1, EuroISDN)

    Default Sip: localhost: 5060
    Default Sip Port: 5066
    Default Transport: UDP

    I save and run with the standard routing-rules.xml that Sangoma makes, the system will come online but all the calls will come in on one line not on each DDI plus can not make any out going calls and the max all time is about 1min. and I have used the config file that the 3cx system makes but with no look

    I have been on the phone to Sangoma with not look

    Can any please help me or does any one use the same setup as me and have a working routing-rules.xml file they can send me

    The 3CX software version is 7.1.7139.0

    Thank you for looking


    Attached Files:

  2. 5qg4

    5qg4 Active Member

    Jan 31, 2007
    Likes Received:
    The config xml generate by 3CX:
    - Not working for DID in
    - Works for outgoing call, but unable to send the correct CID to telco

    No license netborder express v2.0 software or try version are drop call at 60sec (MAX. 1 min call)

    Your local 3CX partner can help you to fix all the issue as above.
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.