NetGen SmartATA HX 422E

[hol9798]

Hi,

I have one of these NetGen Gateways and was trying to get it to work with 3CX. Has any one done this and if so any tips? I've created two extensions and two gateways in 3CX and set the NetGen to "Line Reg/GW Auth". After setting the phone number, Username and password in the NetGen for each, I can use the FXS as a station, but cannot receive or place call using the FXO.
I receive "Authntication Failed" and the 3CX logs show "Cause: 404 Not Found/INVITE from 10.172.20.5:5060" when I place an outbund call. Inbound, it doesn;t look like it even hits the 3CX.

 

[hol9798]

Hi Everyone - As an update for anyone else who needs it, I finally got this working after some late nights and re-reading the manuals many times.
In 3CX

• I set up two two SIP extensions (101 for FXS1 and 201 for FXS2). (Nothing unusal froma settings standpoint)
• I set up one SIP trunk (10000) for FXO1 (I'm not using FXO2, but my configuration at the NetGen would include it if it were active). DID and Outbound CID are set to 10000.

In NextGen

• SIP Set-up
  • Basic > SIP
    • Enter in 3CX Server info;
    • "Authentication mode" = "Register by line" (I putTrunk credentials in UN & PW fields)
  • Advanced > SIP
    • Left all at default except:
      • Called Party Number = "From Request Line Field"
      • Calling Party Number in Call Transfer = "Originating Number"
• FXS Set-up:
  • Phone/Line > Phone x -
    • Phone number = {extension number}
    • Registration = Checked
    • User Name = {Authentication ID} (from 3CX Extension > General > Authentication)
    • Password = {Password} (from 3CX Extension > General > Authentication)
    • All other options set to "UnChecked" (diasabled).
    • Calling features (Call Waiting, Caller ID, MWI, etc)- set as appropriate
  • Advanced > Phone
    • Left all settings as default except:
      • Caller ID trasnmit = "FSK" "MDMF" "After ringing" "with parity" (before Ringing also works, but delays the FXS from ringing one ring)
      • Display Name = Checked
      • Message Waiting Light = FSK
• FXO Set-up
  • Phone/Line > Line x
    • Line number = {Authentication ID} (from 3CX Sip Trunks > Trunk > General > Authentication >Authentication ID
    • Registration = Checked
    • User Name = {Authentication ID} (from 3CX Sip Trunks > Trunk > General > Authentication >Authentication ID
    • Password = {Password} (from 3CX Sip Trunks > Trunk > General > Authentication > Password)
    • Inbound handle = "Binding" (This sends inbound calls to the "Binding number" account or extension; Second stage gives inbound caller ATA dial tome; Direct will route to FXS of same number (FXO1 to FXS1 )
    • Binding number = {{Authentication ID} (from 3CX Sip Trunks > Trunk > General > Authentication >Authentication ID
    • Caller ID detection and Echo Cancellation both set to checked (enabled)
  • Advanced > Line
    • Left all as default except: Caller Number sending mode = "FROM"
• Routing (Probably the part I spent the longest figuring out, as this is where you tell the ATA what routes where)
  • Routing > Dialing
    • I deleted all entries under "Digit Map", so it uses the 3CX Dialing rules. The ATA will automatically re-populate with minimal rules, such as "x.t" which allows any length of number, *, or # to be dialed until a time-out occurs and "x.#" which allows any length of number, or * dialed until # is pressed, which forces dialing, avoiding timeout.
    • Changed repopulated digit map entries to allow longer short codes used by 3CX
      • #xx -> #x.T
      • *xx -> *x.T
  • Routing > Routing Table
    Here you need to tell the ATA what calls will go where. Since I have two FXS and one FXO, I have four lines entered - one for each FXS and two for the FXO. I will list them separately below, and also explain what each does. Keep in mind, the ATA works from top to bottom, so if it meets criteria in the first line, it won't look at the 3rd.
    • "IP 101 ROUTE FXS 1" Tells ATA all IP calls to 101 go to FXS Port 1
    • "IP 201 ROUTE FXS 2" Tells ATA all IP calls to 101 go to FXS Port 2
    • "IP x ROUTE FXO 1" Tells ATA all IP calls to any number (not mentioned aboved), route to FXO Port 1. IF you have two FXO, you can add "-2" at the end for it to use FXO1 first, then FXO2. Google the manual for additional syntax for round robin access to trunks or adding trunk codes.
    • FXO[1-2] x ROUTE IP 172.168.0.182:5060 Tells ATA to route all incoming calls on FXO Ports 1&2 to IP Gateway at IP Address & port of 3CX. Again, Google the manual for additional syntax if you would like to set CID or Prepend/Delete numbers for DID or advanced Call routing purposes.
  • Advanced > Feature Codes (Optional)
    "Service Feature codes" = Unchecked (Disabled) - Allows me to use 3CX Features instead and avoid overlap in star codes.

I'm attaching .pdfs with screen shots of my configs.