When Size Matters. This product is small and compact, allowing for 2 24-port units in a rack mount arrangment taking up just one U (1.75"). A bulk import tool was developed by a sipXcom member and is integrated into the QXFXS24 gateway for your use.
The ability to use a large existing analog telephone base with a new IP telephony network is a very important requirement for many companies who are adapting to the Digital Age. The QXFXS24 Gateway is the perfect solution for your business because it can be added to an IP network, therefore allowing your existing analog phones to join the new VoIP network. The QXFXS24 can be stacked for additional capacity. The QXFXS24 provides a number of powerful features not found on standard FXS gateways, including a detailed call routing table with digit manipulation options.
This Gateway can be installed with any SIP-compliant IP PBX on the market. The modular approach of Epygi Gateways allows you to retain an investment from the past analog phones, while adopting the latest technology with ease.
|Ethernet LAN port||1|
|Ethernet WAN port||1|
|Call Routing capable of modifying caller ID or time of day routing|
|Firewall, VPN Router, Stacking Options, Failover|
QXFXS24 gateway configuration for sipXcom
Please refer to Epygi QXFXS24 manual for detailed information on how to configure QXFXS24 Gateway features. The examples below uses the QXFXS24 simply as a FXS gateway, and does not use the included Router functions. In this use case, the router is connected to sipXcom as an unmanaged gateway to connnect 24 analog devices. Ethernet port is connected to the same local area network the sipXcom server is connected to.
There are other use cases for the product, but this document does not attempt to provide installation assistance with those use cases.
Configuring connectivity to sipXcom server
Log into QXFXS23 Gateway and Run System Configuration Wizard.
Host Name – Give this device a unique Hostname
Domain Name – enter domain name used on sipXcom Server
IP Address – Provide unique IP address on same subnet as sipXcom Server
Subnet Mask – Provide Subnet Mask appropriate for this subnet
It is recommended that the QXFXS24 is not used for the DHCP.
Untick the DHCP Option
Locale – Select Country where Quadro is being installed
Timezone – Select correct timezone.
View Summary Screen
Run Internet Configuration Wizard
Uplink Configuration - Select Ethernet. Set speed to appropriate setting.
WAN IP Configuration - Select IP method – DHCP or Manual. Enter WAN IP if Manual
PPTP Configuration Settings
Wan Interface Configuration
Enter DNS address for the Network (I like to put sipXecs as the DNS server for this device)
Review Summary Page
Configure FXS Port Settings
Using the Bulk Import tools under Extension Management, you can import up to 24 extensions in the QXFXS24 Gateway.
The Bulk import tool provides two functions
- Common setting for the system
Click on Add - give your template a name
SIP Server - enter IP address for sipXcom server
SIP port to use - Leave at Default (5060)
Registration on SIP Server - checkmark this box
- Extension Import Settings
Download the import spreadsheet from Epygi support page
Fill out extension name, password, etc.
Ensure you set the template to the name of the template you just created.
Import spreadsheet to QXFXS24 gateway
Once imported, you will have to manually assign a port number to each extension via the FSX dropdown in the individual configuration page.
Once FXS port is assigned, the port will register in sipXecs server.
Interface Type - If Quadro is connected to a PBX, select Network for your interface type. Otherwise, select User
Select Signaling Type – CAS or CSS CSS=PRI
If you select CCS signaling type, you will be taken to a new screen – Signaling Type CCS
Enter PRI configuration information provided by your PRI service provider.
Under Route Incoming Call – Select Route with Inbound Destination Number
No configuration is required within sipXcom for this device.
The QXFXSW24 has extensive troubleshooting methods build into the system. These include packet captures, network port statistics, Event Logging, etc.