Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.7

FreeSWITCH
FreeSWITCH Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: FreeSWITCH is a scalable telephony platform designed to route and interconnect popular communication protocols using audio, video, text, or any other form of media. FreeSWITCH can perform full video transcoding and Multipoint Control Unit (MCU) functionality. Additionally, this technology supports many advanced Session Initiation Protocol (SIP) features such as presence/ Busy Lamp Field (BLF)/ Service Level Agreement (SLA) as well as Transmission Control Protocol (TCP) Transport Layer Security (TLS) and Secure Real-Time Transport Protocol (sRTP). This technology can also be used as a transparent proxy with and without media in the path to act as a Session Border Controller (SBC) and proxy T.38 (International Telecommunication Union (ITU) recommendation for allowing transmission of fax over Internet Protocol (IP) networks in real time) and other end-to-end protocols.

The FreeSWITCH core provides the Application Programming Interface (API) for modules to make connections to databases. FreeSWITCH currently supports the following Data Source Name (DSN) types: PostgreSQL, Open Database Connectivity (ODBC), and SQLite. The default FreeSWITCH configuration uses a series of SQLite databases that are stored in the /usr/local/freeswitch/db directory of a FreeSWITCH installation. This configuration can be changed to connect to other databases such as ODBC-compliant databases. Freeswitch supports ODBC, enabling various aspects of a system configuration and state to be stored within a database. SIP registrations, call/ channel state, voicemail messages, and voicemail preferences may be stored in the database. Additionally, mod_limit configuration, mod_nibblebill, and call detail record information may be stored in a database.

The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO/
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information: This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v24.7
Decision Date: 07/01/2024 at 19:39:33 UTC
Introduced By: TRM Request
Vendor Name: SignalWire
- The information contained on this page is accurate as of the Decision Date (07/01/2024 at 19:39:33 UTC).