Introduction
Imagine you're trying to call your friend who lives in another city. When you dial their number, your phone needs to talk to many different telephone exchanges (big computers that route calls) along the way. But how do these exchanges communicate with each other? They need a common language, a set of rules, to understand what you want. This is where signaling protocols come in, and one of the oldest and most interesting ones is called MFC/R2.
MFC/R2 stands for Multi-Frequency Compelled R2 Signaling System. That's quite a mouthful, so let's break it down into simpler pieces. Think of it as a conversation between two telephone switches (the big computers that handle calls) using special sounds and signals to set up, manage, and end phone calls. Even though this technology is over 50 years old, it's still used in many parts of the world today, especially in Asia, Latin America, and Eastern Europe.
The Basic Idea: Two Types of Signals
MFC/R2 uses two main types of signals to have its conversation: line signals and inter-register signals. It's like having two languages – one for basic status updates and another for detailed information.
Line Signals: The Simple Status Updates
Line signals are like simple text messages that tell the other switch about the basic state of the call. They answer questions like: Is the line idle (free)? Has someone picked up the phone? Is the call over?
In the digital version of MFC/R2 that runs on E1 lines, these line signals are sent using special bits (tiny pieces of data) in a dedicated signaling channel. Think of it as a separate lane on a highway just for these simple updates. The system uses four bits (called A, B, C, and D), but usually only A and B are used. Here's roughly what they mean:
· A bit: Tells if the line is on-hook (phone hung up) or off-hook (phone picked up).
· B bit: Tells if there's a problem or if the line has been seized (grabbed for a call).
The C and D bits are usually set to fixed values and don't change, though some countries use them for special purposes like sending charging pulses.
Here are some common line signal states you might see:
· Idle: The line is free and waiting for a call.
· Seized: The calling switch has grabbed the line to start a call.
· Seizure Acknowledged: The other switch says, "I see you, go ahead."
· Answered: The person you're calling has picked up the phone.
· Clear Back: The person you're calling has hung up.
· Clear Forward: You have hung up.
Think of these as emojis in a text conversation – they give quick, clear information without needing long explanations.
Inter-Register Signals: The Detailed Conversation
Now, line signals are not enough to set up a call. The switches also need to exchange detailed information like: What number are you trying to reach? What's your phone number? Are you calling from a regular phone or a payphone? This is where inter-register signals come in.
Inter-register signals are special sounds made by combining two specific frequencies (tones) at the same time. There are six possible frequencies, and picking any two gives you 15 different combinations. Ten of these combinations represent the digits 0 through 9, and the other five are used for special messages.
Here's the clever part: the switches use two different sets of frequencies – one for the direction from the calling party to the called party (called forward) and another for the opposite direction (called backward). This way, they can talk over each other without confusion, like two people having a conversation on walkie-talkies using different channels.
The signals are organized into groups. At the start of a call, the calling switch uses Group I signals (mainly digits), and the called switch uses Group A signals (requests like "send me the next digit" or "send me your category"). Later in the call, they might switch to Group II and Group B signals to exchange more detailed information.
Bridging Old and New: Modern Solutions for MFC/R2 Networks
As communication technology evolves, there is a growing need to connect traditional MFC/R2 networks with modern IP-based systems. This is where products like the Baudcom BD-E1-SIP Trunk Gateway come into play. This device acts as a translator between the old world of E1 lines (which carry MFC/R2 signaling) and the new world of VoIP (Voice over IP) using SIP protocol.
The BD-E1-SIP is a cost-effective trunk gateway designed to work seamlessly with popular open-source PBX platforms like Asterisk, Elastix, and Freeswitch, as well as small and medium IPPBX systems. It allows businesses to protect their investment in existing telephone infrastructure while gradually transitioning to modern VoIP technology.
How the Gateway Works with MFC/R2
When an MFC/R2 signal arrives on an E1 line, the Baudcom gateway receives it and performs several important functions. First, it understands the MFC/R2 signaling – the line signals and inter-register tones we discussed earlier. The gateway supports MFC/R2 variants from China and over 22 other countries, making it suitable for use around the world. Then, it converts this signaling into SIP (Session Initiation Protocol) messages that can be understood by IP-based phone systems.
At the same time, the gateway handles the conversion of voice itself. It supports multiple voice codecs including G.711A/U, G.729, G.723, and iLBC, allowing it to work with different VoIP systems and network conditions. Built-in features like echo cancellation (G.168), voice activity detection (VAD), and jitter buffering ensure that call quality remains high even when converting between old and new technologies.
A Typical Call: Walking Through the Steps
Let's walk through what happens when you make a call using MFC/R2. We'll keep it simple and imagine you're calling your friend.
1. Idle: Both switches are sitting there, waiting for something to happen. The line signals show "idle."
2. You dial: You pick up your phone and dial your friend's number. Your local switch (let's call it Switch A) gets ready to send this information to the next switch along the path (Switch B).
3. Seize: Switch A sends a line signal to Switch B saying, "I need to use this line for a call." This is the "seize" signal.
4. Acknowledgment: Switch B sends back a line signal saying, "OK, I'm ready. Go ahead." This is "seizure acknowledged."
5. Sending the number: Now the real conversation begins. Switch A sends the first digit of your friend's number using a Group I tone. As soon as it sends it, it stops and waits. Switch B receives the digit and sends back a Group A tone meaning "send next digit." This compelled exchange continues for every digit of the phone number.
6. Address complete: Once Switch B has all the digits it needs to route the call, it might send a signal saying "address complete." This means it has enough information to proceed.
7. Who's calling?: Switch B might then ask for your category (are you a regular subscriber, a payphone, etc.) and your phone number (caller ID). This information is exchanged using Group II and Group B tones, still in the same compelled manner.
8. Finding your friend: Switch B checks if your friend's line is free. If it is, it sends back a signal saying "subscriber free" and starts sending a ringback tone to you so you can hear the phone ringing at the other end. At the same time, it sends a ringing signal to your friend's phone.
9. Answer: Your friend picks up the phone. Switch B sends a line signal saying "answered," and now you can talk. The special tone detectors are turned off because they're not needed anymore – the line is now just carrying your voice.
10. Ending the call: When you finish talking and hang up, your switch sends a "clear forward" line signal. The other switch acknowledges with a "clear back" signal, and both lines return to the idle state, ready for the next call.
Conclusion
MFC/R2 is like a grand old language that telephone switches have been speaking for over 50 years. It uses simple line signals for basic status updates and a more complex system of inter-register tones for detailed information exchange. The "compelled" nature of the conversation ensures that nothing gets lost or misunderstood. While it might seem complicated at first, breaking it down into these basic pieces makes it much easier to understand.
Whether you're a student learning about telecommunications, an engineer working with older systems, or just someone curious about how phone calls actually work, MFC/R2 is a fascinating example of how clever engineering from decades ago can still be relevant and useful today. It reminds us that sometimes the old ways are still the best ways, especially when they've been tested by time and proven to work reliably, day after day, call after call, for over half a century.