Scribd
Upload
141 views5 pages

FXO Extensions - Vega 50 - 60G - Vega Gateways - Documentation

This document provides instructions for configuring FXO lines on a Vega 50/60G gateway as SIP extensions to an IP-PBX. It involves logging into the Vega gateway's web interface, completing basic configuration like country and IP settings, and configuring VoIP and FXO tab settings. On the VoIP tab, fields like SIP domain, proxy address, and registration mode must be configured. On the FXO tab, caller ID, telephone number filters, and DID numbers that will route calls between the FXO ports and PBX extensions need to be set up. This allows each FXO port to function as a unique extension that can be routed to a specific extension on the PBX.

Uploaded by

Anthony Ivery
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
141 views5 pages

FXO Extensions - Vega 50 - 60G - Vega Gateways - Documentation

This document provides instructions for configuring FXO lines on a Vega 50/60G gateway as SIP extensions to an IP-PBX. It involves logging into the Vega gateway's web interface, completing basic configuration like country and IP settings, and configuring VoIP and FXO tab settings. On the VoIP tab, fields like SIP domain, proxy address, and registration mode must be configured. On the FXO tab, caller ID, telephone number filters, and DID numbers that will route calls between the FXO ports and PBX extensions need to be set up. This allows each FXO port to function as a unique extension that can be routed to a specific extension on the PBX.

Uploaded by

Anthony Ivery
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

5/24/2021 FXO Extensions - Vega 50/60G - Vega Gateways - Documentation

Dashboard / … / Vega 50/60G FXO

FXO Extensions - Vega 50/60G


Created by Leo D'Alessandro, last modified by Marc Celsie on 15 Jan , 2018

The following information will guide you to configure your Vega 50 FXO line as sip extensions to your IP-PBX

1. Log into the Vega gateway using the WebUI interface. The default user is admin and password is admin

As the Vega gateway WebUI loads up the Status page as shown below. Once the page has finished select the "Quick Config" menu option as shown
below:

2.

https://wiki.freepbx.org/pages/viewpage.action?pageId=60915726 1/5
5/24/2021 FXO Extensions - Vega 50/60G - Vega Gateways - Documentation
The WebUI will present a warning message please read the message and then select "Continue" on the screen below

3.
Once the Quick Config UI has loaded should select the "Basic" Tab

This is where the Country localisation and IP address configuration is specified


You must specify the correct country or the Vega will not be able to recognise the network tones for you Telephone lines

4.

https://wiki.freepbx.org/pages/viewpage.action?pageId=60915726 2/5
5/24/2021 FXO Extensions - Vega 50/60G - Vega Gateways - Documentation
Once the Basic config is completed select the "VoIP" tab. The screen shot below highlights the most important fields

SIP Domain: This is normally the IP address or Hostname of the SIP PBX we are sending calls to and receiving calls from.
Proxy Address: This will be the IP network destination for SIP calls from the Vega to the PBX
Outbound Proxy address Not used
Registration mode Must be set to off

5.

https://wiki.freepbx.org/pages/viewpage.action?pageId=60915726 3/5
5/24/2021 FXO Extensions - Vega 50/60G - Vega Gateways - Documentation
Once the VoIP config is competed select the "FXO" tab. A screenshot below gives the example of the FXO tab with default configuration

Enable Caller ID Detection- Enable this checkbox for every port to enable Caller ID
Numeric Caller ID- This is the caller ID number for this port that will be seen on remote devices.
Textual Caller ID- Caller ID name to be presented on remote devices.
Telephone number(s) to route to the FXO inteface- Filter to catch inbound calls from SIP to the specific port. .* means that port will accept
any/every call from SIP and send it out through that FXO port.
This is where you will hard code a unique pre-fix for each port so that only phone calls from SIP matching those prefix will route through that port.

DID to Forward to SIP- Calls from the specific FXO port can push a DID towards SIP. This is how you will identify the individual FXO ports as SIP
extensions to the IP PBX. Enter a DID number for reach of the FXO ports you will use.
These DID numbers do not have to exist as real extension on your PBX, but you will use them to filter your dialplan so that the PBX can dedicate each
port as an extension. Then you can route each port to a specific extension that exists on your PBX.

For example:

For this example, all calls from SIP to the Vega that begin with 202 will pass through FXO port 2 only.
For calls from FXO port 2 to SIP will pass with a called destination of 124. The PBX will find 124 and filter it out and send the call to the specific
extension.

No labels

Powered by a free Atlassian Confluence Open Source Project


License granted to FreePBX.org. Evaluate Confluence today.

https://wiki.freepbx.org/pages/viewpage.action?pageId=60915726 4/5
5/24/2021 FXO Extensions - Vega 50/60G - Vega Gateways - Documentation
This Confluence installation runs a Free Gliffy License - Evaluate the
Gliffy Confluence Plugin for your Wiki!

https://wiki.freepbx.org/pages/viewpage.action?pageId=60915726 5/5

You might also like