Introduction
MFC/R2, which stands for Multifrequency Compelled R2 Signaling System, is a telephony signaling protocol with a history spanning over five decades. Originally developed to provide register-to-register (switch-to-switch) signaling over analog copper pair wiring, it offered a higher speed of data transmission compared to the pulse dialing systems of its era. Its primary purpose was to convey addressing information along a telephone trunk between two switches to establish a call. While it may seem like a relic from the past in a world where SS7 and ISDN are widely deployed, MFC/R2, particularly in its digital form over E1 trunks, remains heavily utilized in many countries across Europe, Latin America, Asia, and Australia.
The protocol was widely adopted for international circuits and many national networks. With the advent of E1 PCM (Pulse Code Modulation) trunks, MFC/R2 was adapted for use over this new digital medium, ensuring its continued relevance. The protocol exists in several country-specific variants, and an international version, often referred to as CCITT-R2, is defined by the International Telecommunication Union Telecommunication Standardization Sector (ITU-T) Recommendations Q.400 through Q.490.
Core Principles of MFC/R2
MFC/R2 is a peer-to-peer, channel-associated signaling (CAS) protocol. This means that signaling for a particular voice circuit is carried on a dedicated signaling channel associated with that circuit, typically using a portion of the E1 frame. In a peer-to-peer system, only two parties are involved in the link, and both behave in a symmetric manner, unlike the client-server model of PRI where distinct "NET" and "CPE" sides exist.
The term "compelled" is central to understanding the protocol. It signifies that the transmission of each piece of information, such as a digit, is controlled and must be explicitly acknowledged by the receiving end before the sender can proceed to the next piece of information. This ensures a reliable and ordered exchange of data, preventing the sending end from transmitting signals too quickly for the receiving end to process.
The protocol defines two fundamental types of signals: line signals (also known as supervisory signals) and inter-register signals (also known as address or call setup control signals). The forward direction is defined as the path from the calling party to the called party, while the backward direction is from the called party to the calling party.
Line Signals in MFC/R2
Line signals are used to monitor and control the state of the call on the trunk line. They represent the various conditions of the line, similar to the states of an analog line, such as on-hook, off-hook, seizure, and clear-down.
In the original analog version of MFC/R2, line signals were encoded by DC voltage conditions on the line. Later, for circuits lacking DC continuity, a 3825 Hz tone was used to encode these states, with the presence or absence of the tone indicating the signal. This analog version is now rarely used.
With the digital version of MFC/R2 over E1 trunks, line signals are carried within the Channel Associated Signaling (CAS) framework. In an E1 frame, timeslot 16 is allocated for signaling for the other 30 channels (timeslots 1-15 and 17-31). For each channel, four bits, known as the ABCD bits, are used for line signaling. However, for MFC/R2, typically only two of these bits (A and B) are used to encode the line state. The A bit generally reflects the line status (1 for on-hook, 0 for off-hook), while the B bit conveys a condition (e.g., 1 for failure or seized, 0 for normal or idle). The remaining C and D bits are often set to fixed values. In some national variants, bits C or D may be repurposed for specific functions, such as sending metering pulses for charging purposes.
The line signaling states follow a specific sequential order. The typical states include Idle/Released, Seized, Seizure Acknowledged, Answered, Clear-Back, and Clear-Forward. For instance, an idle circuit is represented by forward AB bits set to 10 and backward AB bits also set to 10. When the originating switch seizes the line, it changes its forward bits to 00. The terminating switch acknowledges this seizure by changing its backward bits to 11. When the called party answers, the terminating switch sets its backward bits to 01. Special considerations are made for metering pulses, which are encoded as pulses on the line signals (e.g., pulsing backward bit A) during the conversation phase. To avoid confusion with the clear-back signal, a forced-release state is defined in some ITU supplements for systems that use metering.
Inter-Register Signals in MFC/R2
Inter-register signals are responsible for exchanging the information necessary to route and establish a call. This includes the called number (DNIS), the calling party's number (ANI), and the calling party's category. These signals are encoded as in-band, dual-tone multi-frequency (MF) tones. The tones are transmitted over the same voice path that will eventually carry the conversation.
The signaling system uses two distinct sets of six frequencies, spaced at 120 Hz intervals—one for the forward direction and another for the backward direction. A signal is composed of two and only two of these six frequencies, creating 15 possible unique tone pairs. Ten of these pairs are used to represent the digits 0 through 9, while the remaining five are used for various supervisory and control purposes.
The inter-register signals are organized into groups. At the start of a call, the originating end uses Group I forward signals, and the terminating end uses Group A backward signals. Based on the call's progress, the terminating end can instruct the originating end to switch to using Group II forward signals and Group B backward signals. In some national variants, there are also Groups III and C, which are used for transferring the calling party's number.
The meanings of the tone pairs within these groups are defined by the ITU-T recommendations but are subject to significant variation from country to country. For example, Group I forward signals primarily correspond to digits and, in international links, the first digit can also indicate the language preference of the calling party. Other Group I signals indicate requirements for echo suppressors or identify a test call. Group II forward signals convey information about the calling party's line, such as whether it is a subscriber without priority, a subscriber with priority, a payphone, or an operator. Group A backward signals are used to request specific information from the originating switch, such as "send next digit," "send calling party's category," or "address complete." Group B backward signals convey the final status of the call attempt, such as "subscriber's line busy," "unallocated number," or "subscriber's line free, charge."
Typical Call Flow and Scenarios
An MFC/R2 call setup is a compelled, step-by-step process. When a caller goes off-hook and dials digits, their local switch seizes an outgoing E1 trunk by sending the appropriate line signal (Seize). The remote switch acknowledges this (Seizure Acknowledged). The originating switch then sends the first dialed digit using a Group I MF tone. The terminating switch, upon receiving this tone, acknowledges it with a Group A backward signal, typically A-1, which means "send next digit." This compelled exchange continues for each digit of the called number.
Once the terminating switch has received enough digits to route the call, it may respond with A-3 (address complete), and then request the calling party's category using A-5. The originating switch responds with the appropriate Group II signal, such as "subscriber without priority." The terminating switch then determines the final status of the called line and responds with a Group B signal. If the line is free and charging applies, it sends B-6. If the line is busy, it sends B-3. If the call is proceeding, the terminating switch will generate ringback tone towards the caller and ring the called party's phone. When the called party answers, the line signal changes to "Answered," and the conversation phase begins.
Disconnection can be initiated by either party. If the calling party hangs up first, the originating switch sends a "Clear Forward" line signal. The terminating switch acknowledges this with a "Clear Back" signal, and both sides return to the idle state. If the called party hangs up first, the terminating switch sends a "Clear Back" signal. The originating switch typically responds by sending a "Clear Forward" and then idling the line.
Variants and Customization
One of the defining characteristics of MFC/R2 is its numerous national and regional variants. While the ITU defined an international standard, few countries adopted it exactly. This has led to a diverse landscape where the meanings of specific tone pairs, the number of digits expected, the method of ANI transfer, and the handling of supervisory tones can all differ. For example, while most variants use the 2-out-of-6 tone system, some, like India, use a 2-out-of-5 system, resulting in a different set of available signals.
Implementations of MFC/R2 software, such as those within unified call processing APIs, are designed to handle this diversity by allowing for the configuration of the specific national variant. Key parameters include the variant code, the expected number of dialed digits, and the expected number of ANI digits. Setting the expected number of dialed digits correctly is crucial. If it is set too high, the system may wait indefinitely for an explicit "end of dialing" signal that some variants do not send, leading to a timeout and call failure. Optional parameters may also control whether progress tones (like ringback or busy tones) are generated locally or passed through from the far end, as well as the order in which DNIS and ANI are requested.
Conclusion
MFC/R2 is a robust and historically significant telephony signaling protocol that continues to play a vital role in many parts of the world. Its compelled nature ensures reliable information exchange, while its division into line and inter-register signaling provides a clear separation of call supervision and routing functions. Although modern protocols like SS7 and ISDN have largely replaced it in many developed nations, the sheer number of MFC/R2 variants and its deep entrenchment in the infrastructure of numerous countries guarantee its continued presence for years to come. Understanding its fundamental principles, signal types, and call flows is essential for engineers and technicians tasked with maintaining, troubleshooting, or interfacing with these legacy yet still critical telecommunications networks.