Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

How to connect an LQ to a traditional POTS line via Vega Sangoma

Instructions

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

    Image Added

  2. 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:

    Image Added

  3. The WebUI will present a warning message please read the message and then select "Continue" on the screen below

    Image Added


  4.  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


    Image Added



  5. Once the Basic config is completed select the "VoIP" tab.  The screen shot below highlights the most important fields

    Image Added

    SIP Domain: 
    This is normally the IP address or Hostname
    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


  • Once the VoIP config is competed select the "FXO" tab.  A screenshot below gives the example of the FXO tab with default configuration

    Image Added

    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:

    Image Added
    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.



Image Added


Image Added

Image Added



Info

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@105e3
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ( "sangoma" , "sip" ) and type = "page" and space = "CSS"
labelssangoma sip

...