Vegastream Vega 400 SIP Digital Gateway
Total Page：16
File Type：pdf, Size：1020Kb
VegaStream Vega 400 SIP Digital Gateway
1 Important Notes Check the Digital Gateway Feature Matrix for current validation status. The Digital Gateway Feature Matrix can be viewed from the Interactive Intelligence Inc. Testlab website located at: http://testlab.inin.com/ProductsPage.aspx? ProductType=1 It is recommended to utilize the web interface for gateway configuration. As this unit is a critical piece of the SIP infrastructure, it is highly recommended that DHCP not be used. A static IP address is the preferred method and is how the unit was configured during validation. After a factory reset, the Vega 400 will default to G.711 as its primary codec Dial plan entries will supersede all proxy settings.
2 Vendor Documentation
Documentation can be found on the CD shipped with the Vega 400.
3 Validated Firmware Version
R080S016
When upgrading from a pre-R8 build to an R8.x build, a special upgrade procedure must be performed. Refer to the Upgrading document. In R8 and beyond, all products will require a license key.
4 Install Download the Vega 400 firmware files from the Interactive Intelligence Testlab website: http://testlab.inin.com/ProductsPage.aspx?ProductType=1 Contained in the zip file will be the R8 Upgrader file, validated version of firmware (.abs), and a sample configuration file (.txt). The sample CurrentConfig.txt file will configure the Vega 400 Ports (trunks) as ISDN user side. 5 Configuration
Methods:
Console connection using the serial RS232 interface (using supplied cable) was used to perform initial Vega 400 command line configuration. Log in using the serial connection and configure the Vega 400 IP address, login username and pw. TFTP was used to upgrade the Vega 400 via a TFTP server using Pumpkin. Follow the steps in the documentation to perform the firmware upgrade. Manipulation of the supplied configuration file, then uploading it via the web interface. This method is recommended for a quick start scenario. The I3 supplied .txt file, with just a few modifications will get a basic setup up and running. Please note, the I3 supplied .txt file is not meant to be a drop in configuration for every environment, it is provided as reference only (ports 1 and 2 connected to a live ISDN PRI). Restore the configuration file using get tftp:
Initial Setup: Connect a LAN connection to the LAN1 port on the back of the Vega 400 and verify a link light. Unzip the ZIP file containing the Vega 400 configuration file and firmware, and place on a T/FTP server into the desired root directory. Pumpkin was used for validation testing. Browse to the root directory where the Vega files are located. In Options > Network, set default timeout to 60 sec, and block size = 16384. Follow the VegaStream instructions (on the product CD or in the booklet shipped with the Vega 400) for getting an IP address assigned to the gateway, and configuring the T/FTP server. Modify the I3 provided .txt file if necessary. Start a web browser and type in the IP address of the Vega 400. Connect the RJ-45 console cable between the Vega 400 and a computer using a terminal emulator program. The default user name is “admin” and the password is “admin”. It is recommended to change the password at this time for security reasons.
Download Current Firmware (ABS file): Refer to the Vega Upgrade documentation provided in the Testlab web page. Using the serial Console interface, save the Vega’s current configuration (.txt) to the T/FTP server. Skip this step if you have a new gateway and have no initial configuration. Enter the upgrade mode and download the UpgraderR8 file via the T/FTP server, and reboot. Download the latest firmware file via the T/FTP server, and reboot. Log into the Vega using the web browser, and load the license key at the Maintenance > System Upgrade link, and reboot. Using the serial console, restore the previous configuration file (.txt) from the T/FTP server. If no previous configuration existed, restore the R08CurrentConfig.txt file provided. Save and reboot. The Vega 400 is now ready for operation. Once the restart is complete, return to the web interface and click Maintenance > Show Version. The displayed Version should match the installed firmware version. If it does not, double check the upgrade steps and consult the VegaStream documentation if necessary. Click Maintenance > System Upgrade. Verify that “LICENSE KEY = OK”, and that the expected number of channels and DSL topology type (T1) are shown. If not, contact the system administrator responsible for license key generation per the Vega S/N.
Changing the Configuration: Prior to making any changes, the VegaStream documentation should be consulted for information on configuration parameters, options and functions. Changes on the Vega 400 can be made via the web interface. The .txt file can be modified, then restored using FTP/TFTP. The serial console may be used for the command line interface, or the web UI Advanced > CLI Command dialog.
Testing the Configuration: Refer to the Information Note Connecting a T1/E1 Checklist document. From the web UI, verify configuration of the DSL Ports for T1, ATT (5ESS), ESF, B8ZS, and g711Ulaw. Save and Reboot if changes are made. Connect a live ISDN PRI to the I/F 1 port, and verify that the L2 LED is a solid green, indicating both physical layer 1 and signaling layer 3 are OK. Verify that both inbound and outbound calls can be made via the gateway.
6 Redundant Proxy Configuration The following configuration options are found under SIP > SIP Profiles in the web interface. Configure the following information for SIP Profile 1: Name Interface ID Local Domain In order for the Vega 400 to function with redundant proxies, configure the following Information for SIP Proxy: Add and enable SIP Proxy 1 with the IP/DNS Name (IP address of primary SIP Proxy). Add and enable SIP Proxy 2 with the IP/DNS Name (IP address of secondary SIP Proxy).