A basic phone line from a carrier is "dumb" – it connects two people, and that's it. No routing logic, no call forwarding, no call parking, no recording, and no call transfer. A call control service platform is "smart" – it implements business logic that determines what happens to each call.

With a basic line, calls go unanswered if you're not at your desk. Call control service means calls automatically forward to your mobile phone or transfer to an available employee.

Call control service requires application server software like BroadWorks or Metaswitch, SBC hardware to enforce policies, and proper network design. Most modern businesses use call control service delivered either on-premises (they buy and operate their own equipment) or in the cloud (a service provider operates the infrastructure and they access it via the internet). 

Call forwarding is a phone system feature that automatically routes incoming calls to a different destination – another phone number, another extension, or voicemail. 

In BroadWorks and similar platforms, how call forwarding works is entirely at the application server level. For instance, when Alice calls Bob and Bob has call forwarding set to Carol's number, the application server looks up Bob's forwarding configuration and sends the outbound INVITE directly to Carol – Bob's device never rings.

Call forwarding works regardless of whether Bob's phone is registered, powered on, or even physically present. It also means the application server is the single authoritative place to configure call forwarding, and troubleshooting call forwarding failures requires understanding the application server feature logic, not just endpoint behavior.

A virtual phone number (also called a DID or local number) is a phone number that isn't tied to a specific physical phone line or location. Virtual phone number forwarding routes calls to that number to a destination of your choosing – another phone number, an extension, a phone system, or even a mobile phone.

Here's how it works:

1. A customer dials your virtual phone number

2. Your VoIP carrier (or hosted PBX provider) receives the call and consults routing rules

3. The call is forwarded to the destination phone number you've configured

Virtual phone number forwarding lets businesses maintain a local presence in multiple cities without physical phone lines in each location – for example, a service center in New York can have a local Los Angeles number that forwards calls back to New York. 

BLF allows one phone to display the call state (idle, ringing, or on a call) of another user on the same platform. The monitoring phone sends a SUBSCRIBE message to the application server for each user it wants to watch. The application server then sends a NOTIFY to the monitoring phone every time that user's state changes.

In attendant console or receptionist environments monitoring dozens of lines, or with expansion key modules, the resulting SUBSCRIBE, NOTIFY, and 200 OK message volume can be substantial – enough to trigger SBC rate-limiting if the medium manager is not sized correctly.

At ECG, we size the SBC medium manager and validate BLF at full production scale, ensuring BLF indicators stay responsive even in large contact-center deployments. 

There are several compliance requirements tied to E911:

• E911 mandates from the FCC require interconnected VoIP providers to transmit a callback number and the customer's registered physical location with every 911 call.

• Kari's Law (2018) requires that 911 can be dialed without a prefix and that someone on-site is notified when a 911 call is placed from a multi-line system.

• RAY BAUM's Act extends this to require a dispatchable location – enough to identify the specific room or floor, not just a street address – for customers in multi-tenant buildings and enterprise environments.

Non-compliance penalties can reach $10,000 plus $500 per device per day in continuing violations. 

Call Admission Control on a session border controller limits the number of concurrent calls and the rate of new call arrivals per peer, per customer, or globally. CAC protects your network against call loops (where calls get forwarded back to themselves), fraudulent dialing (where a compromised account dials thousands of international numbers), or a misbehaving carrier peer suddenly sending ten times its contracted call volume.

Default CAC settings from the SBC vendor are usually either too permissive – offering no meaningful protection – or too restrictive for environments with large attendant phones, BLF-heavy deployments, or extension modules that generate high SIP message rates. Correct CAC values must be derived from actual packet captures measuring SIP byte rates and CPU load simultaneously; there is no universal number.

ECG handles this by calculating your actual CAC limits from traffic data and configuring per-peer policies before the next incident. 

REFER is the SIP method a phone sends when the user presses the transfer button. For a blind transfer, the REFER-To header contains just the target URI. For an attended (consultative) transfer – where the transferring party speaks to the target first – the REFER-To header includes a Replaces parameter containing the Call-ID, from-tag, and to-tag of the call leg being transferred. The receiving endpoint uses those identifiers to find the correct dialogue to take over.

Attended transfer failures occur when the SBC has modified SIP headers that make the Replaces identifiers inconsistent with what the endpoint recorded, the endpoint doesn't support the Replaces extension, or the confirming NOTIFY signaling transfer completion is blocked.

ECG can trace these failures with simultaneous packet captures on both sides of the SBC to identify exactly where dialogue identifiers diverge.

Call control customer service techniques include:

• Training agents to verify the transfer target's name and availability before transferring

• Using attended transfer (speaking to the target first) rather than blind transfer where possible

• Implementing call park for calls that can't be immediately transferred

• Using call forwarding for after-hours to reduce missed calls

• Monitoring call transfer success rates to identify systemic issues 

From a platform perspective, ECG helps implement the call control features (call parking, forwarding, transfer) that enable these techniques and ensures they work reliably so customer service teams can focus on the customer experience rather than troubleshooting dropped calls. 

Call parking is a feature that allows one user to place an active call on hold and then retrieve it from another phone. When a user presses the park button, the system assigns the call a park extension (like 7001, 7002, etc.), announces it to the caller, and places the call on hold. Another user can then dial that park extension to retrieve the call.

What does park mean on a phone? It means the call is being held by the system rather than by an individual phone, freeing up that phone to make other calls.

ECG helps service providers and enterprises implement call parking that works reliably, including timeout handling, hold music playback, and integration with BLF so users can see which calls are parked.