AudioCodes Gateways

Owned by Former user (Deleted)
Last updated: May 31, 2011 by Former user (Deleted)Version comment

Detailed Information

Supported Models And Features

Analog PSTN gateways

AudioCodes MP114 FXO

Featuring 4 analog ports, this gateway connects analog PSTN lines to the IP network using FXO connectivity.

AudioCodes MP118 FXO

Featuring 8 analog ports, this gateway connects analog PSTN lines to the IP network using FXO connectivity.

Digital PSTN gateways

AudioCodes TP-260 - 8 E1/T1 PCI VoIP Communications Board


The TP-260 PCI VoIP communications board is a solution for trunking gateways to the PSTN and integrated gateways for IP PBXs and all-in-one communications servers. The TP-260 provides 256 ports for voice, fax or data implementing VoIP media gateway applications.

The TP-260 supports a broad selection of voice processing related algorithms, including G.711, G.723.1 and G.729A Vocoders, G.168 compliant echo cancellation, T.38 real-time FAX over IP, as well as a wide selection of in-band and out-of-band tone detection and generation. The TP-260 supports E1, T1, and J1 PSTN interface standards. For more information see the Audiocodes Web site.

AudioCodes Mediant 1000 VoIP Media Gateway


The Mediant 1000 VoIP gateway is a cost-effective, entry level member of the AudioCodes family of SIP gateways. It scales up to 4 E1 / T1 / J1 PSTN trunks in a 1U chassis. Features include NEBS level 3 certified, SIGTRAN backhauling (SS7: M2UA/M3UA,PRI), SS7 peer-to-peer tunneling over IP, G.711, G.723.1, G.726, G.729A codecs, echo cancellation, FAX support, tone generation.

Auto Configuring AudioCodes Gateways

AudioCodes gateways can be managed automatically by sipXecs.  Some DHCP configuration changes are required however to make things work properly. The steps required are:

  1. Upload Device Files to sipXecs
  2. Add Gateway to sipXecs and Generate Profile
  3. Configure DHCP

Upload Device Files to sipXecs

To upload device files to sipXecs:

1. Login to the GUI as superadmin.

2. Click on the 'Devices' menu and select the 'Device Files' menu item. The following page will appear:
3. Click on the 'Add files...' drop down box and select the type of AudioCodes gateway you are adding.

4. Give the device files a descriptive name as shown below and click on OK.
5. Back in the Device Files list, click on the name of the newly added device file entry and the following page will be displayed:
6. Click on the Browse button and locate the firmware file you'd like to use.  After the file is selected, click on the 'Activate' button and the firmware will be uploaded and set to 'Active'.

Add Gateway to sipXecs and Generate Profile

To add a gateway to sipXecs:

1. Login to the GUI as superadmin.

2. Click on the 'Devices' menu and select the 'Gateways' menu item. The following page will be displayed:

3. Click on the 'Add new gateway...' drop down menu and select the type of AudioCodes gateway you'd like to add.  The following page will then be displayed:

4. At a minimum specify the gateway a name (no spaces or special characters in name), IP Address, Serial Number (MAC Address), Firmware version and a description.

5. Click the 'OK' button.

6. Click on the gateway name hyperlink and the following page will be displayed:
7. Click on 'PSTN Lines' in the left side menu and add the FXO ports you'd like to use.

8. Click the 'OK' button after you have added lines and are done.

9. If prompted to, click on the hyperlink to restart required services.

10. In the gateways page, click on the check box beside the newly added gateway and click on the 'Send Profiles' button.

Don't forget that you'll need to add the gateway into dial plans to use it for outbound dialing.

Configure DHCP

To configure DHCP, ssh to the sipXecs system and login as root.

At the command prompt enter: nano -w /etc/dhcpd.conf

  • Add a 'next-server' option into the subnet that will contain the AudioCodes gateway.
  • Add a 'group' section to the subnet.  This will contain the host entries for the gateways.
  • Add a 'host' section for each gateway.  Note that case in MAC address and file names is important!
  • The 'filename' is a concatenation of the firmware file name followed by the name of the ini file generated by sipXecs.

After dhcpd.conf file is edited, restart the dhcpd service. To do this enter: service dhcpd restart

If you get a 'Failed' message on service restart, check the syntax in the dhcpd.conf file, it is likely you missed a bracket or semi-colon.

Example dhcpd.conf
authoritative;
ddns-update-style  ad-hoc;
option sip-servers-name code 120 = text;

subnet 172.16.2.0 netmask 255.255.255.0 {
        next-server 172.16.2.2;
        option tftp-server-name "172.16.2.2";
        default-lease-time 43200;
        max-lease-time 43200;
        option routers 172.16.2.1;
        option subnet-mask 255.255.255.0;
        option domain-name "sipxecs.info";
        option sip-servers-name "sipx.sipxecs.info:12000/cmcprov/login";
        option domain-name-servers 172.16.2.2 , 172.16.1.254 , 8.8.8.8;
        option ntp-servers 172.16.2.2;
        range 172.16.2.5 172.16.2.250;
group {
        host acgateway {
                hardware ethernet 00:90:8f:0c:aa:aa;
                fixed-address 172.16.2.5;
                filename "MP118_SIP_F5.80A.053.003.cmp;00908F0CAAAA.ini";
                }

        host acm1000 {
                hardware ethernet 00:90:8f:2d:aa:aa;
                fixed-address 172.16.2.6;
                filename "M1000_SIP_F6.00A.025.004.cmp;00908F2DAAAA.ini";
                }
        }
}

Additional Notes

1. If you are having difficulty getting the gateway to pickup the changes, reset the gateway (hold in reset button for at least 6 seconds) and then power cycle the gateway. A regular reset from the AudioCodes GUI menu does not force the gateway to pickup.

2. Disconnect on Broken RTP needs to be set to No. This can be found in Protocol Definition or Advanced SIP settings (must be in Full menu to see).