Vega 100G and Vega 200G Gamma Config Guide

This document aims to go through the steps necessary to configure the Vega SBC to be used with a Gamma SIP Trunk.

When a SIP trunk is provisioned by Gamma a list of information will be provided an example list is show below:

- The Public IP that the SIP trunk communicates with

- DDIs allocated to the Trunk
- Gamma SIP Trunk Source - 88.215.61.201

Gamma SIP Trunk SIP to PBX

VEGA SBC

To help make this example guide more complete we will use some example network configuration:

The Example Gamma Trunk Telephone number 01258 159826

The example installation public IP - 212.36.44.14

The default gateway IP for LAN – 192.168.5.1

The Vega SBC LAN IP address - 192.168.5.100

The Vega SBC External LAN IP address - 192.168.5.215*

The SIP PBX Internal IP address - 192.168.5.50

*The SBC External IP maybe a LAN address or maybe a WAN IP address

NOTES:

Gamma SIP Trunks are normally IP Authenticated, this means that SIP Registration is not used.

The Gamma VoIP servers are located at 88.215.61.201 (SIP) and 88.215.61.202 (Media), if the installation environment is
behind a NAT both of these IP address will need to be port forwarded in the router to the internal Vega IP Address.

The setup procedure that follows will focus on the configuration of the Vega SBC for basic operation behind a NAT,
STEP 1: Log into the Vega SBC using the WebUI interface. The default user is root and password is sangoma.

STEP 2: Once logged in, the Control Panel will be displayed by the SBC WebUI

Select the "Configure" button next to the "Hardware" line. This will take you to the "Signalling Interfaces" page.

Step 3: Once the "Signalling Interfaces" page has loaded this will display 3 interfaces:

eth0 - Internal Interface

eth2 - External Interface
sngdsp0 - Media Transcoding Interface

The interface that will be configured is the External Interface, this is the interface which will communicate with the
Gamma SIP Trunk.

Select the "Edit" for the ETH2 Interface

The “eth2” configuration page, allows the IP configuration here select whether to use "DHCP" or a "Static IP" and enter
the required information.
When the settings have been entered selection the "Confirm" to accept the changes.

STEP 4: To configure the SBC Dial plan route for calling from SIP PBX to Gamma please follow this step.

Navigate to the Configuration Menu and select “Call Routing”

Create a New Advanced Routing entry for this example name it “TO_GAMMA”

This dial plan will handle call routing from the SIP PBX to the Gamma SIP trunk through the SBC.
To populate the TO_GAMMA dial plan route please use the configuration below, once filled out please select the “Save”
at the base of the dial plan panel

NOTE the field “<regex field="network_addr" expression="192\.168\.0\.210"/>” this defines the LAN address of the
local SIP PBX

STEP 5: To configure the SBC Dial plan route for calling from Gamma to the SIP PBX please follow this step.

Navigate to the Configuration Menu and select “Call Routing”

Create a New Advanced Routing entry for this example name it “TO_PBX”

To populate the TO_PBX dial plan route please use the configuration below, once filled out please select the “Save” at
the base of the dial plan panel

NOTE the field “<regex field="network_addr" expression="88\.215\.61\.201"/>” this defines the Addresses of the
Gamma SIP servers and will only allow calling from Gamma to arrive at the PBX.
STEP 6: Next the SIP Profile configuration will be created – Navigate to > Configuration > Signaling > SIP Profiles

Select “Add” to create a new SIP Profile – Please name the Profile “External” – this will hold the configuration for the
Gamma SIP settings

->The SIP IP address should be the External LAN IP Address configured

->External SIP and External RTP IP Addresses should be configured with the External Public IP address if the SBC is
behind a NAT

->The NAT Traversal Settings should also be configured if behind a NAT

-> The Routing plan that should be selected is the TO_PBX plan

Once settings are complete please select the save at the base of the page
STEP 7: Next the second SIP Profile configuration will be created – Navigate to > Configuration > Signaling > SIP Profiles

Select “Add” to create a new SIP Profile – Please name the Profile “Internal” – this will hold the configuration for the
local SIP PBX

->The SIP IP address should be the Internal LAN IP Address configured

->Set Authenticate calls to disabled

-> The Routing plan that should be selected is the TO_GAMMA plan

Once settings are complete please select the save at the base of the page
STEP 8: Create SIP Trunk Configuration – Navigate to > Configuration > Signaling > SIP Trunks

Select “Add” to create a new SIP Trunk – Please name the Profile “PBX” – this will hold the configuration for the local SIP
PBX

->The SIP Domain is the sIP IP address of the PBX server - 192.168.5.50

-> The SIP Profile that should be selected is the Internal SIP Profile

->The other settings can be left at defaults

Once settings are complete please select the “save” at the base of the page
STEP 9: : Create SIP Trunk Configuration for Gamma Trunk – Navigate to > Configuration > Signaling > SIP Trunks

Select “Add” to create a new SIP Trunk – Please name the Profile “Gamma” – this will hold the configuration for the
local SIP PBX

->The SIP Domain is the IP address of the Gamma SIP server 88.215.61.201

->The FROM domain is the public IP of the local system

-> The SIP Profile that should be selected is the External SIP Profile

->The other settings can be left at defaults

Once settings are complete please select the save at the base of the page
STEP 9: Once attached, go to Configuration-> Management -> Apply to generate the configuration changes and to start
or reload the gateway. Once completed, you should be able to place a call from Lync to a SIP Trunk and then Vice Versa.

Navigate to > Configuration > Management > Apply

This will cause the SBC configuration to update and apply changes

The Control panel should load up after applying the config from here the SBC can be started:
Appendix 1

Below is an example of a Gamma provisioning Email

IPDC Order Confirmation Email

Your Order Details

Order ID 159xxx

IPDC Endpoint Name DC2N13QEO9xxx

Your CPE IP Address <your WAN IP Address>

Channels Created x

DDIs Allocated to this endpoint

0149441xxxx

0149441xxxx

0149441xxxx

0149441xxxx

 Traffic on the following ports must be

Configuration - Ports & IP forwarded through relevant routers
and firewalls on the customer premises

Signalling:UDP port 5060 egress/ingress to:- 88.215.61.201

Media: All UDP ports between 6000 - 40000 egress/ingress

88.215.61.202
to:-

 The SIP headers originated from the

Configuration - SIP Headers CPE should be set as follows:-

Request-URI Header
The number within the Request-URI is used for routing calls and should contain the called number. The format of this
number can either be UK national format (with leading zero) or full e.164 format (with leading +).

Examples
INVITE sip:+441618777148@100.100.100.29 SIP/2.0
INVITE sip:00441618777148@100.100.100.29 SIP/2.0
INVITE sip:01618777148@100.100.100.29 SIP/2.0

TO Header
Header must contain IPDC SIP gateway address and the called number. The format of this number can either be UK
national format (with leading zero) or full e.164 format (with leading +).

Examples:
To: <sip:+441618777148@100.100.100.29>
To: <sip:00441618777148@100.100.100.29>
To: <sip:01618777148@100.100.100.29>

FROM Header
The user part of the SIP URI within the 'From' header must contain the Calling Line Identity of the originating device. This
identity must be a number registered to the endpoint. The format of this number can either be national significant (with
or without a leading zero), or in full e.164 format. The domain part of the SIP URI within the 'From' header can contain
either the IP address of the public facing interface or a customer-defined FQDN. Gamma will not use this FQDN for any
purpose

Examples
From: <sip:+441618777148@100.100.100.29> or using FQDN From: <sip:+441618777148@your.domain.local>
From: <sip:01618777148@100.100.100.29> or using FQDN From: <sip:01618777148@your.domain.local>
From: <sip:1618777148@100.100.100.29> or using FQDN From: <sip:1618777148@your.domain.local>

PAID Header
The format of the PAID number can either be national significant (with or without a leading zero), or in full e.164 format.
If no PAID header is provided, Gamma will insert a PAID header with the default network CLI.

Examples
P-Asserted-Identity: <sip:+441618777148@100.100.100.29>
P-Asserted-Identity: <sip:01618777148@100.100.100.29>
P-Asserted-Identity: <sip:1618777148@100.100.100.29>

Important Notes

Number Porting
If you require to port numbers to the IP Direct Connect endpoint, this process can only commence once the new IP
Direct Connect node has successfully been provisioned and tested.

Quality of Service (QoS)

For connections to IPDC via public internet, Gamma will not support or deliver marked voice traffic (Signalling or Media).
For connection to IPDC via private interconnect, QoS markings will be agreed during the interconnect establishment
stage.

Service Acceptance Tests

The Endpoint is now in a position to be tested, can you please undertake the pre-defined Service Acceptance Tests that
were outlined in the e-mail that Gamma forwarded to you on Order Acceptance. (The tests are included in an
attachment to this mail for your information).

Technical Support
If you have technical issues or service problems with IP Direct Connect Service or require an issue raised during the
testing of the connection, please contact our technical support on 0808 178 8000 (Option 1, Option 1 and then Option
2).

FAQS
We have published a list of 'Frequently Asked Questions' and a SIP A to Z to help answer any queries you have around
the service you have ordered, or SIP in general. You can find this on the Gamma Portal under 'Channel Partner Support >
Knowledgebase > SIP Trunking > Technical Support'.