Vega Gateway Lync Configuration Guide

OverviewIntroductionVega Configurations

Quick configurationSystem configurationSIP configurationMedia configuration

Overview

This document will guide you through the process of configuring Vega series of Gateway’s to work with Microsoft Lync Server 2013.

Introduction

Vega Gateway Lync Configuration Guide provides detailed information about the configuration requirements in Vega series of Gateways (Vega 100G, Vega 200G, Vega 400G and Vega 800G) to deploy this in a Lync environment.

A typical deployment connects PSTN/Mobile Network to Vega Gateway on one side using Vega T1/E1 interface and Lync Server on the other side using Vega LAN interface with SIP as a control protocol.

 

Vega Configurations

Quick configuration

Run “Quick Config” on Vega GUI

On “Basic Config” tab select country. The default country setting is “UK”.

 

 

Move to “VoIP” tab of “Quick Config”. 

Enter “SIP Domain” field with the domain where the Lync server 2013 is running.

Enter “SIP Server IP/Name” field with the Mediation server IP/Name.

 

 

Move on to “E1” tab of “Quick config”. Make sure it looks like as below.

 

 

Click on the check box for “New Install?”, Then Click on Submit. Save and Apply the settings.

 

 

System configuration

Now come to the specific configurations under “Expert Config”

Click on “Expert Config  > LAN/WAN”.

Configure a unique name for Vega Gateway on “Hostname” field and “Submit” the configuration.

NOTE: A DNS record should be added in DNS server on the Domain.  Lync server would need to resolve this name to contact Vega Gateway.

 

 

On the same page “Expert Config  > LAN/WAN”, scroll down till “DNS Parameters”

Enter “Static DNS Servers” field with DNS server IP running in the Domain and “Submit”

 

NOTE: Vega Gateway would be using this DNS sever to resolve mediation server IP address.

 

 

SIP configuration

Click on “Expert Config > SIP”.

Enter “Local SIP Port” field with port number Vega SIP would like to listen on.

NOTE: The same port should be configured in “trunk configuration” on Lync Server as Vega Gateway port.

 

On the same page “Expert Config > SIP”, under “SIP Profiles” click on “Modify” link and enter into “SIP > SIP Profile 1” configuration page.

Enter “Local Domain” field with the domain name Vega gateway and Lync Server is associated with.

Select “Transport” as tcp, and “Submit”

 

On same page, “SIP > SIP Profile 1” , on “SIP Profile 1 Proxy Parameters 1”

Enter “Request-URI Port” field with the port number Mediation server opened for listening SIP traffic.

Select “Accessibility Check” as “options”

Select “Accessibility Check Transport” as tcp and “Submit”

 

 

On the Same page “SIP > SIP Profile 1” Click on the “Modify link to enter into “SIP > SIP Profile 1 > Proxy 1”

Make sure

“Enable” is checked

“IP/DNS Name” field is entered with Mediation server IP/DNS name

“Port” is configured with the port number Mediation server opened for listening SIP traffic.

 

 

Click on page “Expert Config > SIP”, scroll down and click the link “Advanced SIP”

On this page,

Check “REFER INVITE to proxy”

Enter “Outgoing Call Setup Timeout” field with value 180000 and “Submit”

 

 

Click on page “Expert Config > Advanced”

On “CLI Command” field enter “set .sip.sig_transport=tcp”

 

 

Enter one more “CLI command”

“set ._advanced.sip.max_forks=20”

 

 

Click on Page “Exper Config > SIP”, Scroll down and click on the link “SIP Response-Q.931 Cause Mapping”

Enter “488” field with value 31

Enter “606” field with value 31

 

 

Click on Page “Exper Config > SIP”, Scroll down and click on the link “Q.931 Cause-SIP Response Mapping”

Enter “18” field with value 408

 

 

On the same page

Enter “31” field with value 480

Enter “38” field with value 503

 

On the same page

Enter “102” field with value 504, and “Submit”

 

 

Media configuration

Click on Page “Expert Config > Media

Click on “Packet Profile > Packet profile1”, click “Modify” link and enter into “Media > Packet Profile 1”

Select “Silence Suppression” field enable.

Select “Out of Band DTMF” field enable and submit.

Now we need to make some adjustments on the Codec Configuration to avoid offering codecs not needed to establish a call with Lync Mediation Server.

Let's reduce the codec offering to just G.711 and T.38. Remember from the previous points that we are using Capability Set 2-Voice+T38

Click on Page “Expert Config > Media

You will notice all 7 codecs are selected by default on the Capability Set 2.

 

Click on Modify and lets reduce to codecs 2, 3 and 5

 

Click on "Submit"Click on "Apply"Click on “Save” to save the configurationsClick on “Reboot System”