The Patton SN4141 FXS device allows users to connect analog telephones to a VoIP network, facilitating communication through extensions created on the Vodia PBX. After logging in to the device and setting up extensions, users can utilize the Patton Wizard to configure FXS ports, entering necessary details such as the number of ports and the PBX IP address. Once the configuration is completed, it's uploaded to the device for it to register with the PBX, enabling seamless connectivity for analog devices in a VoIP environment.
Under the product search function, type in your model. For this tutorial, we are using the following: SN4141
Choose the following wizard, Trinity 1-8 port FXS SmartNode with SIP Registration, and run the Wizard.
Wizard setup
Enter the password for your device.
Country selection
Number of FXS ports & SIP Server IP Address
We are using two FXS ports. If you have more than one FXS port, you can choose in this section.
Enter your PBX IP address
SIP Server SIP Settings
In this section, you will enter the following for (FXS 0/0):
Name of extension (FXS 0/0) is the extension account created on the PBX
Extension or DID (FXS 0/0) is the extension account created on the PBX
SIP Server username (FXS 0/0) is the extension account created on the PBX
SIP Server Password (FXS 0/0) is the extension SIP password
Retype SIP Server password
In this section, you will enter the following for (FXS 0/1)
Name of extension (FXS 0/1) is the extension account created on the PBX
Extension or DID (FXS 0/1) is the extension account created on the PBX
SIP Server username (FXS 0/1) is the extension account created on the PBX
SIP Server Password (FXS 0/1) is the extension SIP password
Retype SIP Server password
Uploading the Patton configuration file
Login in to your Patton device with user admin and no password. If the password was provided in the .cfg file, then you will enter that password after you reboot the unit.
Navigate to the right-hand panel and choose System ---> Configuration Files
Upload your configuration file
Browse and upload your configuration file. Save as startup-config and press OK.
Reboot the device
Status Registrations
Now that your Patton is running the new start config file, we will need to verify if the FXS ports are registered to the PBX.
Navigate to All account --- Extensions and check the status for registration. If the ports are registered, congrats! If not visit us at https://doc.vodia.com/admin_logging ;)
Vodia has launched a new prepaid PBX offering on AWS Marketplace, enabling businesses of all sizes to quickly and easily deploy a secure, feature-rich phone system in the cloud. Building on the success of our prepaid solutions for Microsoft Azure and DigitalOcean, this new AWS package offers a cost-effective, scalable, and reliable way to integrate enterprise-grade telephony into your existing infrastructure. Whether you're connecting SIP devices with Microsoft Teams via our certified SBC or establishing a standalone PBX, the deployment process is streamlined, flexible, and built for growth.
Installing Vodia PBX on Linux offers system administrators a powerful, enterprise-grade communication solution with built-in monitoring, automated backups, and disaster recovery features. This guide walks through supported Linux distributions, pre-installation requirements, and step-by-step instructions using a universal install script. With options for service monitoring, backup scheduling, and cloud deployment, it ensures a scalable and secure setup. Post-installation, standard Linux tools manage service status, updates, and logs, making ongoing maintenance simple.
Vodia now integrates its industry-leading PBX with Microsoft Dynamics 365, enabling automatic synchronization of call data with the CRM to enhance customer interaction tracking and streamline communications. This integration offers features such as automatic contact creation for unknown numbers, comprehensive call activity logging including direction, duration, and outcomes, and seamless user matching for accurate call attribution. Designed to empower businesses, this connection supports more efficient and scalable communication workflows within the Microsoft ecosystem.