Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

<?xml version="1.0" encoding="utf-8"?>
<html>

Vegastream

The following example setup illustrates a working configuration of Vegastream 400 interoperating with SIPxchange; descriptions on the right provide details concerning entries made to the screen example on the left. Please refer to the Vegastream documentation for complete descriptions of each of the fields.

For sipX settings, access the sipX interface for the Configuration server, select Services from the left-hand main navigation menu, select Configuration, select Global Definitions from the screen that appears, and set the GW_DEFAULT_ADDR to the IP address of the Vegastream gateway in the associated field.

<table width="400" cellpadding="2" cellspacing="2">
<tr>
<td valign="top"><center>
Image Removed
</center></td><td>
<div align="center">
<strong>LAN Configuration</strong>
</div>
<ul>
<li>NameImage Added

LAN Configuration
*Name: Vega400; the name of the gateway you want to use.</li>
<li>LAN *LAN Profile: 1</li>1 <li>LAN

  • LAN Gateway: 10.1.20.1; the IP address of the gateway to get o other subnets.

...

...

  • Use DHCP Settings From Interface: 2; the interface you will use to get the DHCP information if you use DHCP.

...

</td>
</tr>

...

<td valign="top">
<div align="center">
Image Removed
</div>
</td>
<td>
<div align="center">
<strong>LAN Profile 1</strong>
</div>
<ul valign="top">
<li>LAN Image Added

LAN Profile 1

  • LAN Interface: The LAN interface you are using; in this case, 2.

...

</td>
</tr>

...

</div></td><td>
<div align="center">
<strong>LAN Interfaces</strong>
</div>
<ul>
<li>IP

LAN Interfaces

  • IP Address: This is the IP Address of the Vegastream. Set the static IP address here.

...

</div></td><td>
<div align="center">
<strong>DNS Servers</strong>
</div>
<ul>
<li>Domain

DNS Servers

  • Domain Name Server: The IP Address of the DNS server being used. Here the DNS server is being configured statically.

...

</tr>
<tr>
<td valign="top"><div align="center">
Image Removed
</div></td><td>
<div align="center">
<strong>DSL Configuration</strong>
</div>
<ul>
<li>Network Image Added

DSL Configuration

  • Network Type: The switch type you are using, such as

...

  • ATT

...

  • Network Topology: T1 or

...

  • E1

...

  • Line Encoding: B8ZS; must be B8ZS for ISDN. AMI or B8ZS for CAS.

...

...

  • Framing: ESF; must be ESF for ISDN, ESF or SF for CAS.

...

Port Configuration

  • You should not have to modify these fields.

...

</div></td><td valign="top">
<div align="center">
<strong>Dial

Dial Planner (Profiles)</strong>
</div>
<p>You

You will need at least two dial plans. One for calls coming in from the T1 interface, and the other for calls going out of the T1 interface. In this example, Profile IDs 2 ISDN_To_LAN and 3 LAN_to_ISDN_or_PBX are used (see the next Dial Planner profiles screens and associated field text).</p></td>
</tr>
<tr>
<td valign="top"><div align="center">

</div>
</td><td valign="top">
<div align="center">
<strong>Modify Plan</strong>
</div>
<ul>
<li>Name

Modify Plan

  • Name: The name of your plan (should have association to the original Dial Planner Profile name from the first graphic in this section).

...

...

  • Source: The source of the calls; in this example, all interfaces except the LAN.

...

...

  • Destination: The destination of the calls; in this example, the LAN.

...

</ul></td>
</tr>
<tr>
<td valign="top"><div align="center">
Image Removed
</div></td><td valign="top">
<div align="center">
<strong>Modify Plan</strong>
</div>
<ul>
<li>NameImage Added

Modify Plan

  • Name: The name of your plan (should have association to the original Dial Planner Profile name from the first graphic in this section).

...

...

  • Source: The source of the calls; in this example, all calls from the LAN.

...

...

  • Destination: The destination of the calls; in this example, destination T1 interface 2.

...

<tr>
<td valign="top"><div align="center">
Image Removed
</div></td><td>
<div align="center">
<strong>Media Capability</strong>
</div>
<p>This Image Added

Media Capability

This is a list of the media capabilities supported by the Vegastream.</p>
<strong>G711 G711 u-law Profiles</strong>
<ul>
<li>Packet Profiles

  • Packet Time: The sample size of the g711 sample.

...

...

  • VADU Enabled: VAD is enabled.

...

...

  • Out of Band DTMF: 1; this must be 1 for RFC 2833.

...

G729 AnnexA

  • Packet Time: The frame size of the g729a frame.

...

...

  • VADU Enabled: VAD disabled.

...

...

  • Out of Band DTMF: 1; this must be 1 for FRC 2833.

...

</div></td><td>
<div align="center">
<strong>SIP Configuration</strong>
</div>
<ul>
<li>Default

SIP Configuration

  • Default Proxy Hostname/IP: The host name of SIPxchange should be used.

...

...

  • Local Domain: The domain the Vegastream is in.

...

...

  • Local SIP Port: Port 5060 is the default.

...

...

  • Requrest URI Port: Port 5060 is the default.

...

...

  • LAN Profile: 1; this is profile 1, in this case.

...

</div></td><td valign="top">
<div align="center">
<strong>Audio</strong>
</div>
<p>You Audio

You populate the Audio Profile fields with the coding algorithms RTP traffic is to use. Audio Profile 1 holds the first choice algorithm, Audio Profile 2 holds the second choice, etc.</p> <li>Audio

  • Audio Profile 1: G711 Ulaw; this it he first coding algorithm.

...

...

  • Audio Profile 2: G729; this is the second coding algorithm.

...

...

  • Audio Profile 3: G711 Alaw; this is the third coding algorithm.

...

...

  • Audio Profile 4: None; no fourth choice is this example.

...

</div></td><td>
<div align="center">
<strong>Miscellaneous</strong>
</div>
<p>The

Miscellaneous

The defaults should remain intact. Check to make sure that your configuration is the same as shown here.</p></td>
</tr>
<tr>
<td valign="top"><div align="center">

</div></td><td>
<div align="center">
<strong>SIP Advanced</strong>
</div>
<p>The

SIP Advanced

The defaults should remain intact. Make sure your configuration is the same as shown here.</p>

</td>
</tr>
</table>

</html>