...
Analogue handsets would be simply standard analogue handsets.
Vega Gateway 1 FXO Configuration
NOTE The Vega would be used such that each analogue PBX line is connected to one Vega FXO port. The calls from one phone system to another will always IP PBX should be set up to treat each extension as a individual line to the PBX.
...
Proxy Domain name this is normally the IP address or Hostname of the SIP PBX we are sending calls to and receiving calls from.
| Info |
|---|
NOTE Vega 1 will be send SIP traffic to Vega 2 in this way only need the proxy address needs to be defined. |
Proxy Address this will be the IP address of Vega 2 in the example this would be 192.168.1.200
...
STEP 6: The parameters to be configured by Quick config are complete
select the "Submit" button.
| Info |
|---|
NOTE The Quick Config Submit creates a popup Click "OK" on the next window to apply the settings. |
...
| Info |
|---|
NOTE The save process creates a popup window select "Continue" on this window. |
...
STEP 7: Next goto the Expert Config>Dial Planner web page and select to modify the "To_SIP" dial plan profile.
| Info |
|---|
NOTE: This defines the use routing for calls from the Analogue PBX ----> IP-PBX |
...
STEP 8: The next step is to modify the To_SIP profile. The standard To_SIP profile has a single entry sending all calls from analogue interfaces to SIP. This profile will forward calls from the Analogue PBX extension to the remote handset via the Vega FXO through SIP and out to the Vega FXS gateway.
...
"IF:9901" defines the SIP interface to send the call that matches the source expression,
"TEL:2001" defines that the call from PBX extension 2001 will be sent to Vega 2 with the DID 2001 which Vega 2 will use to route the call Vega 2 FXS port that corresponds to the remote handset
| Info |
|---|
NOTE: If more than one analogue PBX extension is required to be configured the same style of configuration can be used - a different source TEL number and a different destination IF need to be specified eg source "IF:0202,TEL:" destination "IF:9901,TEL:2002" |
...
...
| Info |
|---|
NOTE For calls inbound to FXO interface from the analogue PBX there are some specific POTS limitations which limit the conifg above. Inbound calls from a POTS line do not have a called party telephone number as the POTS line is the terminating point for the call (but they can have CLID). As such a call from a POTS line will only arrive at Vega with CLID information. One of the requirements of SIP is that call cannot be made without a destination telephone number > this means the Vega Dial plan must be used to define a DID number that is sent on to the SIP PBX, in our example is this given as "2001" but this can be configured to what ever is required. |
...
|
STEP 9: The next step is to configure the Dial plan for calls from the PBX 2 to PBX 1. This is the important section which defines the Vega behaviour while calling the analogue PBX 1 extension.
...
This defines the SIP - FXO behaviour in only one direction - SIP -->Analogue PBX.
| Info |
|---|
NOTE: If more than one analogue PBX extension is required to be configured the same style of configuration can be used - a different source TEL number and a different destination IF need to be specified eg source "IF:99..,TEL:2002" destination "IF:0202,TEL:" |
...
Be sure to select the "Submit" to confirm the configuration changes ready to be applied and saved to the Vega
STEP 11: This completes the configuration for Vega gateway 1 - make sure the config is submitted to the Vega, this concludes the Vega Configuration please select the "save" and "apply" to commit the configuration back to the Vega.
Vega Gateway 2 FXS Configuration
This Vega gateway would be used to connect the remote analogue handset/extension to SIP from Vega Gateway one. used. When the remote extension goes off hook a SIP call will go to Vega 1 and the appropriate extension will go off hook sending PBX dial tone back to the Vega extension.
...
STEP 13: 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:
| Info |
|---|
NOTE This is where the Country localisation and IP address configuration is specified. NOTE You must specify the correct country or the Vega will not be able to recognise the network tones for you Telephone lines |
CHANGES TO THE VEGA IP ADDRESS WILL REQUIRE A REBOOT TO BECOME OPERATIONAL
...
Enabled?: This determines if the port/extension is enabled, unused ports should be disabled
| Info |
|---|
NOTE All Enabled ports will try to register to the IP PBX as such make sure that only the ports that are going to be used are enabled. |
Enable Caller-ID generation:This turns on the generation of caller-id - for incoming calls CallerID will be sent to the POTS handset as a burst of tones.
Numeric Caller-ID: Defines the telephone number that is sent as Caller ID for outbound calls from the extension
Textual Caller-ID: Defines where applicable the textual name of the Caller ID name for outbound calls from the extension
Telephone number(s) to route...: Defines the dial plan routing to this extension (eg 2001 through 2004)
Registration and Authentication ID: Not Used
Authentication Password: Not used
STEP 16: The parameters to be configured by Quick config are complete - select the "Submit" button.
| Info |
|---|
NOTE The Quick Config Submit creates a popup Click "OK" on the next window to apply the settings. |
...
| Info |
|---|
NOTE The save process creates a select "Continue" on this window. |
...
STEP 17: Next goto the Expert Config>Dial Planner web page and select to modify the "To_SIP" dial plan profile.
| Info |
|---|
NOTE: This defines the use routing for calls from the Analogue PBX into the IP-PBX |
...
STEP 18: The next step is to modify the To_SIP profile. The standard To_SIP profile has a single entry sending all calls from analogue interfaces to SIP. This profile will forward calls from the Analogue PBX extension to the remote handset via the Vega FXO through SIP and out to the Vega FXS gateway.
...
"IF:9901" defines the SIP interface to send the call that matches the source expression,
"TEL:2001" defines that the call from PBX extension 2001 will be sent to Vega 1 with the DID 2001 which Vega 2 with which Vega 1 will know to route the call FX) port1 and so to the correct port on the analogue PBX.
| Info |
|---|
NOTE: If more than one analogue PBX extension is required to be configured the same style of configuration can be used - a different source TEL number and a different destination IF need to be specified eg source "IF:0102,TEL:" destination "IF:9901,TEL:2002" |
...
|
...
Be sure to select the "Submit" to confirm the configuration changes ready to be applied and saved to the Vega