From hybrid labor to smarter workspaces, combining technology and touchpoints to provide exceptional experiences.
View DetailsUsing Baker's top-notch technology to create exceptional experiences for people, environments, and things.
View DetailsUnderstand best practices, explore innovative solutions, and establish connections with other partners throughout the Baker community.
From hybrid labor to smarter workspaces, combining technology and touchpoints to provide exceptional experiences.
Learn moreUsing Baker's top-notch technology to create exceptional experiences for people, environments, and things.
Learn moreUnderstand best practices, explore innovative solutions, and establish connections with other partners throughout the Baker community.
Encyclopedia
An FXO gateway is a VoIP gateway that connects analog PSTN lines or legacy PBX trunk ports to an IP PBX, SIP server, cloud PBX, or unified communications platform. It allows an IP-based phone system to make and receive calls through traditional analog telephone lines, making it a practical bridge for VoIP migration, PSTN backup, and hybrid voice networks.
The term FXO stands for Foreign Exchange Office. From the perspective of the analog telephone line, an FXO interface behaves like a telephone or terminal device. It receives battery, ringing voltage, caller ID information, and disconnect signals from the line-providing side, such as the PSTN or a legacy PBX analog port.
An FXO gateway is a hardware voice gateway equipped with one or more FXO ports. These ports connect to analog PSTN lines, analog CO lines, or analog trunk interfaces from a traditional PBX. On the IP side, the gateway connects to an Ethernet network and communicates with an IP PBX, SIP server, softswitch, or hosted voice platform.
Its main function is to translate between analog telephony and IP voice communication. On the analog side, the gateway handles ringing, off-hook status, caller ID, line voltage changes, tone detection, and disconnect supervision. On the IP side, it uses SIP for call signaling and RTP for voice media transmission.
In practical deployment, an FXO gateway is often used when a company wants to keep existing PSTN lines, preserve local phone numbers, connect a legacy PBX to VoIP, provide emergency fallback lines, or migrate from analog telephony to IP telephony in stages.
An FXO gateway works between the analog telephone line and the IP voice network. One side connects to PSTN lines or analog PBX interfaces. The other side connects to the LAN or WAN and communicates with the IP PBX, SIP server, or cloud voice service.
When an incoming call arrives from the PSTN, the analog line sends ringing voltage to the FXO port. The gateway detects the ring, receives caller ID when supported, and sends a SIP INVITE to the configured IP destination. That destination may be a receptionist extension, ring group, IVR, call queue, or dispatch console.
Once the call is answered on the IP side, the gateway converts analog audio into RTP packets. During the call, it manages echo control, gain adjustment, tone detection, and media bridging between the analog line and the IP endpoint.
For outgoing calls, the process works in the opposite direction. A user dials an external number from an IP phone or softphone. The IP PBX routes the call to the FXO gateway according to its dial plan. The gateway selects an available analog line, seizes the line, sends the dialed digits, and connects the voice path to the PSTN.
A typical FXO gateway handles the following functions during call processing:
Line detection: Monitors ringing, line voltage, off-hook status, polarity changes, and other supervisory signals.
SIP conversion: Converts analog call events into SIP messages such as INVITE, 180 Ringing, 200 OK, and BYE.
Digit processing: Applies routing rules, prefix handling, digit stripping, number normalization, and dial timeout settings.
Media conversion: Converts analog voice into RTP audio streams using codecs such as G.711 or other configured codecs.
Echo and tone handling: Uses DSP resources for echo cancellation, tone detection, silence handling, gain control, and call progress detection.
Disconnect supervision: Detects polarity reversal, CPC, battery drop, busy tone, reorder tone, or timer-based release conditions to clear calls correctly.
A customer calls the company’s analog PSTN number.
The PSTN line rings the FXO port on the gateway.
The gateway detects the incoming call and sends a SIP INVITE to the IP PBX.
The IP PBX routes the call to an extension, queue, IVR, or operator.
After the call is answered, the gateway converts analog voice into RTP media.
When the call ends, the gateway detects the disconnect signal and releases both the analog and SIP call legs.
Although the call flow looks simple, stable FXO deployment depends on local analog line behavior. Caller ID timing, tone plan, impedance, loop current, disconnect method, and regional PSTN standards can all affect call reliability. In actual installation, disconnect detection and caller ID recognition are usually among the first items to test.
FXO and FXS are related analog telephony interfaces, but they are used for different purposes. Choosing the wrong port type is one of the most common mistakes in analog VoIP projects.
An FXO port connects to a line that already provides battery, dial tone, and ringing. It behaves like a telephone toward the PSTN or PBX line side. An FXS port does the opposite. It provides battery, dial tone, and ringing to an analog endpoint such as a telephone, fax machine, analog intercom, or speakerphone.
Therefore, an FXO gateway is used to bring analog outside lines into an IP system, while an FXS gateway is used to connect analog devices to an IP system. Some projects use both types, but they solve opposite connection problems.
| Item | FXO Gateway | FXS Gateway |
|---|---|---|
| Main purpose | Connect analog PSTN or PBX lines to IP telephony | Connect analog phones, fax machines, or intercoms to IP telephony |
| Port behavior | Acts like a telephone toward the line side | Acts like a line provider toward the analog endpoint |
| Typical connection | PSTN line, CO line, analog PBX trunk | Analog phone, fax, speakerphone, intercom |
| Common use case | PSTN access, analog trunk retention, backup outbound calling | Retaining analog endpoints in an IP PBX or SIP platform |
| Simple way to remember | FXO receives line service | FXS provides line service |
The exact feature set depends on the vendor and model, but business-grade FXO gateways usually include the following functions for hybrid voice deployment.
The core function of an FXO gateway is to connect analog PSTN lines to an IP-based phone system. This gives the organization local inbound numbers, outbound PSTN access, or fallback calling when SIP trunks or WAN links are unavailable.
Most FXO gateways support SIP registration, peer-to-peer SIP trunking, codec negotiation, DTMF transmission, and interoperability settings for IP PBX systems, SIP servers, softswitches, and hosted voice services.
Administrators can define how inbound and outbound calls should be routed. For example, specific analog lines can be assigned to local calls, emergency calls, branch calls, business-hour routing, or backup routes. Digit manipulation, prefix insertion, and caller ID settings are also commonly supported.
Analog lines may introduce echo, level mismatch, or noise because of impedance differences and line conditions. FXO gateways usually include DSP-based voice processing, echo cancellation, gain adjustment, jitter handling, and tone detection to improve call quality.
Caller ID delivery varies by country and carrier. Some lines send caller ID before the first ring, while others send it between rings or with different signaling formats. A reliable FXO gateway should support regional caller ID standards and allow related timing parameters to be adjusted.
Failed call release is a common issue in analog integration. A good FXO gateway should support multiple disconnect detection methods, including CPC, polarity reversal, battery drop, busy tone detection, silence timeout, and timer-based release. Correct disconnect supervision prevents stuck calls and unavailable lines.
Some sites still need fax over analog lines. Depending on the model, an FXO gateway may support fax passthrough, codec locking, jitter settings, or T.38 on the IP side. Fax performance depends on the complete path, including the PSTN line, gateway configuration, network quality, and the remote fax endpoint.
Business deployments usually require web management, configuration backup, firmware upgrade, syslog, SNMP, status monitoring, call statistics, and alarm reporting. These functions are important for multi-site deployment and long-term maintenance.
In a hybrid voice network, FXO gateways are often used as backup voice routes. If SIP trunk service, WAN access, or a hosted PBX connection fails, local analog PSTN lines can still support limited but important calling, especially for emergency or site-critical communication.
FXO gateways are used wherever analog line access needs to be retained while the voice system moves toward IP. They are practical devices for phased migration, backup calling, and legacy system integration.
When a business replaces a traditional PBX with an IP PBX, it may still need to keep existing analog outside lines for a period of time. An FXO gateway allows the new IP system to use those lines without waiting for a complete carrier migration.
Remote offices may need local calling, local number presentation, or independent PSTN access. An FXO gateway can provide local analog trunk access while the branch remains connected to a centralized IP PBX or unified communications platform.
Even when SIP trunks are the primary voice service, some organizations keep analog lines for backup. If the internet connection, SIP trunk, or hosted PBX service becomes unavailable, the FXO gateway can provide an alternate path for essential calls.
Some enterprises need to interconnect a new IP system with an existing PBX. FXO ports can connect to analog trunk or extension interfaces on the legacy system, helping both platforms communicate during a phased upgrade.
Hotels, shops, clinics, and small offices often keep analog lines because of local service availability, existing numbers, or simple operating requirements. FXO gateways allow these sites to add IP phones, IVR, call recording, or remote management without removing all analog dependencies at once.
Factories, substations, tunnels, utility stations, and remote facilities may still rely on analog lines for resilience, local carrier access, alarm connection, or legacy dispatch integration. An FXO gateway can bring these lines into a modern IP voice or dispatch environment while preserving local access.
Choosing an FXO gateway is not only about the number of ports. The right model should match the analog line environment, SIP platform, call volume, and maintenance requirements.
The number of FXO ports should match the number of analog lines that need to be used at the same time. For example, four concurrent analog PSTN calls normally require a 4-port FXO gateway. For future expansion, it is better to reserve some port capacity instead of selecting only for the current minimum requirement.
The gateway should support the SIP registration or peer trunk mode required by the IP PBX, SIP server, or cloud PBX. Codec support, DTMF mode, NAT traversal, authentication method, and keepalive behavior should also match the voice platform.
Country and carrier settings matter. Ring cadence, impedance, tone plan, caller ID format, line voltage, and disconnect behavior vary by region. A gateway used in international projects should support country templates and manual analog parameter adjustment.
In real deployment, this is one of the most important checks. If the gateway cannot detect when the remote party has hung up, the line may remain occupied. Before large-scale rollout, test CPC, polarity reversal, busy tone detection, and release timers with the actual carrier line.
If fax is required, check whether the gateway supports fax passthrough, T.38, codec control, and jitter tuning. For best reliability, test fax behavior under real network conditions instead of relying only on datasheet support.
The gateway should support secure administrator access, password control, firmware maintenance, configuration backup, log export, and access restrictions. If it is connected across an IP network, SIP account protection and management security should be part of the design.
If the FXO gateway is used for survivability, confirm how calls will be routed when the primary SIP trunk or WAN link fails. The dial plan should clearly define emergency numbers, local fallback routes, and recovery behavior after the primary service returns.
A stable FXO gateway deployment depends on both telephony configuration and IP network design. The following items should be checked before the system is placed into production.
Analog lines may use loop start or ground start signaling. The gateway and the connected line must support the same signaling method. A mismatch can cause seizure conflicts, glare, failed outbound calls, or unreliable line status detection.
Caller ID behavior is not the same everywhere. Some carriers deliver caller ID before the first ring, while others deliver it after the first ring. If caller ID is missing or unstable, ring delay and caller ID detection parameters may need adjustment.
Busy tone, dial tone, reorder tone, and ringback tone differ by region. Incorrect tone settings may cause failed call progress detection or delayed call release. For international sites, local tone plan verification is important.
On the IP side, call quality depends on codec selection, packet timing, jitter, packet loss, and network QoS. G.711 is often preferred for PSTN interworking because it provides transparent voice quality, while compressed codecs may be used where bandwidth is limited.
If analog PSTN lines are used as backup routes, the gateway itself should also be protected. Consider UPS power, redundant network paths, and clear routing rules so that the backup line remains usable during service interruptions.
An FXO gateway offers several practical benefits. It protects existing telecom investment, allows phased migration to IP telephony, keeps local PSTN numbers usable, and provides backup calling routes when SIP service or WAN access is unavailable.
It also gives organizations more flexibility. A site can keep analog lines for local calling, emergency fallback, carrier transition, or legacy PBX interconnection while still adopting IP phones, SIP servers, cloud PBX services, recording systems, and unified communications platforms.
However, FXO gateways also have limitations. Analog trunks have limited channel capacity, less predictable signaling, and fewer advanced service features than SIP trunks or digital circuits. Large systems may be better served by SIP trunking, PRI, or other scalable interconnection methods.
For this reason, an FXO gateway is best viewed as a practical bridge rather than a full replacement for modern IP trunking. It is most valuable when analog lines are still required, when migration must be gradual, or when local PSTN backup is part of the communication design.
An FXO gateway is a type of VoIP gateway. The term specifically refers to a gateway that connects analog PSTN lines or analog PBX trunk ports to an IP-based voice system.
Not in the normal way. An analog phone requires an FXS interface because it needs dial tone, battery, and ringing from the line side. An FXO port is designed to connect to a line-providing interface, not to provide service to an analog endpoint.
An FXO port receives line service from the PSTN or PBX, while an FXS port provides line service to analog devices. In simple terms, FXO connects to the outside line, and FXS connects to the analog phone or fax device.
The number of FXO ports should match the number of analog lines that need to be active at the same time. For example, if a site has four analog PSTN lines and all four may be used simultaneously, a 4-port FXO gateway is required.
Yes. Many FXO gateways can register to or communicate with a cloud PBX using SIP. This allows local analog lines to be used as call routes for a hosted voice system, as long as the cloud platform supports the integration method.
It can provide PSTN access for an IP PBX, but it does not fully replace SIP trunking in larger systems. SIP trunks are usually more scalable and feature-rich, while FXO gateways are better for analog line retention, backup calling, or phased migration.
Disconnect problems usually happen because analog line supervision varies by carrier and region. If the gateway’s release detection settings do not match the actual line behavior, calls may stay connected after one side hangs up.
Many FXO gateways can be used in fax-related deployments, but fax reliability depends on the PSTN line, codec settings, IP network quality, gateway configuration, and remote fax equipment. Real testing is recommended before production use.
Choose an FXO gateway when analog lines already exist, when SIP trunks are unavailable, when local PSTN backup is required, or when a business wants to migrate from legacy telephony to VoIP in stages.
An FXO gateway is a practical bridge between analog telephone lines and modern IP communication systems. It converts analog line signaling and voice into SIP-based call sessions, allowing IP PBX systems, SIP servers, cloud PBX platforms, and unified communications systems to use traditional PSTN lines.
For businesses that still depend on analog outside lines, local PSTN backup, emergency calling routes, or legacy PBX interconnection, an FXO gateway remains a useful and cost-effective solution. The best results come from selecting the right port density, matching local line parameters, testing caller ID and disconnect supervision, and integrating the gateway carefully with the broader IP voice network.
Becke Telcom specializes in IP PBX business phone software systems for enterprises, offices, campuses, hotels, and industrial sites. Its platform supports SIP extensions, call routing, IVR, voicemail, recording, conferencing, operator console, and centralized management, helping organizations build flexible, scalable, and easy-to-manage VoIP communication networks.
