Remote Call Forwarding:
Testing Before Full Port
Switch to a new VoIP provider without risking a single missed call. Set up remote call forwarding first — test everything, then port.
Remote Call Forwarding (RCF) is the smart business strategy of routing your existing phone number to your new VoIP or SIP trunk system before you complete a formal number port. This lets you test call quality, IVR menus, routing rules, and all system features with live traffic — while your original number stays safely on your current carrier. In this guide, you'll learn exactly what RCF is, how to set it up, what to test, and when you're ready to commit to a full port — with zero downtime and zero risk.
- What Is Remote Call Forwarding (RCF)?
- Why Test Before You Port — The Risks of Skipping This Step
- RCF vs Full Number Port — Key Differences
- How to Set Up Remote Call Forwarding Step by Step
- What to Test During Your RCF Period
- Pre-Port Readiness Checklist
- Common Issues Found During RCF Testing (and How to Fix Them)
- When Are You Ready to Pull the Trigger on a Full Port?
- How NetViaVoice Makes This Process Easy
- Frequently Asked Questions
📡 What Is Remote Call Forwarding (RCF)?
Remote Call Forwarding is a carrier-level feature that instructs your existing phone number to forward all incoming calls to a different number — one you specify. It's typically offered by your current phone service provider and can usually be activated without a technician visit or any physical change to your infrastructure.
In the context of switching to a new VoIP or SIP trunking provider, RCF becomes a powerful testing tool. Instead of porting your number immediately — which is permanent and can take days — you first ask your current carrier to forward calls on that number to a temporary DID (Direct Inward Dial) number on your new VoIP system. Your customers still dial the same number they always have. You, meanwhile, receive those calls on your brand new system and can test everything from audio quality to call routing — with live, real-world traffic.
Once you're satisfied that the new system works exactly as expected, you initiate the full number port. The RCF is cancelled and calls flow directly into your new system permanently. If something isn't right, you simply adjust your new setup and keep testing — your original number is still safe on your old carrier.
📌 Definition: Remote Call Forwarding (RCF)
Remote Call Forwarding is a telecommunications feature that redirects all calls arriving at your existing business phone number to a forwarding destination — typically a temporary number on your new VoIP system — without requiring number porting or any physical infrastructure change. It acts as a real-world testing bridge between your old and new phone systems.
Want a Zero-Downtime Number Switch?
NetViaVoice guides you through remote call forwarding and full port — with expert support every step of the way.
⚠️ Why Test Before You Port — The Risks of Skipping This Step
A phone number port is a largely irreversible process. Once initiated, your number begins moving from your old carrier to the new one — and if your new system isn't ready, the result can be hours or even days of missed calls. For a business, that's missed sales, frustrated customers, and damaged reputation.
✅ With RCF Testing First
- Catch audio quality issues before they affect customers
- Verify call routing, IVR menus, and extensions work correctly
- Train staff on the new system with real calls
- Test failover and disaster recovery configurations
- Zero customer-facing downtime at any point
- Fix problems at your own pace — no pressure
- Complete the port only when 100% confident
❌ Porting Without Testing
- Discover call routing errors after the port is live
- Audio issues discovered by customers, not you
- IVR menus may send callers to wrong departments
- Staff unprepared for new system interface
- Rollback is slow, expensive, and often impossible
- Customer calls drop during system configuration
- Revenue and reputation damage from downtime
🔄 RCF vs Full Number Port — Key Differences
| Attribute | Remote Call Forwarding (RCF) | Full Number Port |
|---|---|---|
| Speed | Minutes to hours | 2–10 business days |
| Reversibility | Fully reversible | Largely permanent |
| Number ownership | Stays with current carrier | Transfers to new carrier |
| Call path | Old carrier → forwarded to new DID | Directly into new carrier |
| Cost | Small monthly fee (often $5–$15) | One-time port fee (often $0–$30) |
| Risk level | Very low | Medium if untested |
| Audio quality | Slight overhead (double-hop) | Direct — optimal quality |
| Best used for | Testing & validation phase | Final production switch |
| Outbound caller ID | Shows new DID unless configured | Shows your original number |
| Emergency (911) | Follows original number's 911 config | Must update 911 address |
🔧 How to Set Up Remote Call Forwarding Step by Step
The process varies slightly by carrier but follows the same general workflow. Here's exactly what to do:
Before activating RCF, you need a destination number on your new VoIP system. Ask NetViaVoice (or your new SIP provider) to provision a temporary DID number — this is where your forwarded calls will land while you test.
Call your current phone provider and request Remote Call Forwarding on your business number. Provide them with the temporary DID from step 1. Most carriers can activate this same day. Some may call it "unconditional call forwarding" or "network call forwarding."
Set up your IP-PBX or cloud phone system to receive calls on the temporary DID: build your IVR menus, extension routing, voicemail greetings, ring groups, and any other features you need. This is your sandbox environment with live traffic.
Make and receive test calls. Have colleagues call your main number from multiple device types. Test all call paths, all IVR options, all extensions. Document what works and what needs adjustment. (Full test checklist in the next section.)
Ensure your new system presents your original business number as the caller ID on outbound calls — not the temporary DID. Most SIP providers allow you to set a custom caller ID in your trunk configuration.
Register your correct office address with your new VoIP provider's emergency services (e-911) before porting. This is legally required and critical for safety.
Once every test passes and your team is comfortable, submit the number port request to your new provider. Keep RCF active until the port completes — then cancel it. You're done.
🧪 What to Test During Your RCF Period
The RCF testing period is your window to find and fix every issue before it affects a customer. Test methodically — don't just make one call and call it done. Here's a comprehensive testing framework:
| Test Category | What to Check | Pass Criteria | Priority |
|---|---|---|---|
| Inbound call quality | Audio clarity, latency, jitter, echo | MOS score 3.8+ · No echo · <150ms latency | Critical |
| Outbound caller ID | Your original number appears to recipients | Correct number shown on all outbound calls | Critical |
| IVR / Auto-attendant | All menu options route correctly | Every keypress goes to correct destination | Critical |
| Extension routing | Internal extensions receive calls correctly | All extensions ring and answer properly | Critical |
| Voicemail | Unanswered calls route to voicemail · Messages stored correctly | Voicemail activates after set timeout · Transcription works | High |
| Hold & transfer | Warm transfer · Blind transfer · Hold music | No dropped calls during transfer · Music plays on hold | High |
| Conference calling | Multi-party calls · External bridge access | 3+ parties can join without audio degradation | Medium |
| After-hours routing | Night mode · Holiday schedules · Overflow | Calls route correctly outside business hours | High |
| Failover | What happens if internet drops? | Calls route to mobile or backup number automatically | High |
| CRM integration | Screen-pops · Call logging · Click-to-dial | Customer data appears on inbound · Calls log automatically | Medium |
| Mobile/softphone | Remote workers can make/receive calls | Works on WiFi and cellular · Audio quality acceptable | Medium |
| 911 / Emergency | Emergency calls route with correct address | Confirmed with provider in writing | Critical |
✅ Pre-Port Readiness Checklist
Before submitting your full port order, every item on this list should be ticked:
- All inbound calls arrive clearly with no audio quality issues
- IVR menus route to the correct departments or extensions
- Voicemail is configured and messages are being received and stored
- Outbound calls show your original business number as caller ID
- Hold music is configured and plays correctly
- Call transfers (warm and blind) work without dropped calls
- After-hours and weekend routing is configured and tested
- Disaster recovery / failover routing is set up and tested
- Emergency (911) address is registered with new provider
- All staff are trained on new phone system interface
- CRM / helpdesk integration is working (if applicable)
- Call recording is configured (if required for compliance)
- Mobile / softphone apps are installed and tested by remote staff
- Port rejection documentation has been reviewed and LOA prepared
- You have confirmed porting timeline with your new provider
🔍 Common Issues Found During RCF Testing (and How to Fix Them)
| Issue Discovered | Likely Cause | Fix |
|---|---|---|
| Echo on calls | Acoustic echo from IP phone speaker, or codec mismatch | Enable echo cancellation in PBX settings; use G.711 codec; adjust phone speaker volume |
| One-way audio | NAT traversal issue; firewall blocking RTP ports | Configure SBC or STUN server; open UDP ports 10000–65535; disable SIP ALG on router |
| Dropped calls after ~30 seconds | SIP timeout due to NAT; missing ACK packets | Enable SIP keepalives; configure NAT settings in PBX; check firewall UDP timeout settings |
| IVR routes to wrong extension | Dial plan misconfiguration in PBX | Audit dial plan rules; test each DTMF digit; verify DTMF mode matches (RFC2833 vs in-band) |
| Caller ID shows wrong number | SIP trunk caller ID override not configured | Set outbound caller ID in trunk settings; verify P-Asserted-Identity header configuration |
| Voicemail not triggering | Ring timeout too long; voicemail not assigned to extension | Adjust ring timeout to 20–25 seconds; verify voicemail box assigned to each extension |
| Poor audio during peak hours | Insufficient bandwidth; QoS not configured | Set up QoS on router to prioritize voice traffic; consider upgrading internet or adding bandwidth |
🚀 When Are You Ready to Pull the Trigger on a Full Port?
There's no fixed timeline for how long you should run RCF testing. For a simple setup — a few extensions and basic routing — a week of live-traffic testing is usually plenty. For complex multi-site configurations with CRM integrations and compliance recording, allow 2–4 weeks.
📋 You're Ready to Port When:
- Every item on the Pre-Port Readiness Checklist is ticked
- You've received at least 50–100 real inbound calls with zero complaints
- All staff have used the new system and feel comfortable
- You've tested from multiple device types and locations (office, home, mobile)
- Failover has been tested by deliberately disconnecting your internet and confirming calls still route
- Your Letter of Authorization (LOA) is prepared and account details for your current carrier are confirmed
- You've reviewed the expected porting timeline with your new provider
Once you submit the port order, keep your RCF active right up until the moment the port completes. Many businesses make the mistake of cancelling RCF early, which can create a gap if the port takes longer than expected. Your provider will confirm when the port is complete — only then should you contact your old carrier to cancel the RCF.
🌐 How NetViaVoice Makes This Process Easy
At NetViaVoice, we've guided hundreds of businesses through exactly this process — from setting up a temporary DID for RCF testing, through full number port, to final production go-live. Our team handles the technical complexity so you can focus on running your business.
🛠️ What NetViaVoice Provides During Your RCF & Port Journey
A temporary DID for testing at no extra charge during the trial period · Full SIP trunk configuration support · Step-by-step guidance on RCF setup with your current carrier · Port order management and LOA preparation · Real-time port status tracking · Post-port quality verification call with our technical team · 24/7 support throughout the process at +1 201 979 3825 or via WhatsApp at +92 333 5908806.
Start Your Risk-Free Switch Today
Get a temporary DID from NetViaVoice and test your new phone system with live calls — before you commit to anything.