Shared Line Appearance (SLA, SCA, BLA) Explained

In VoIP, a shared line appearance (SLA) lets multiple phones share one line: every phone in the group shows the line’s live status, any of them can answer or place calls on it, and a call put on hold at one desk can be picked up at another. It is not the other SLA — a service level agreement, the uptime-and-support contract — despite the identical acronym. If you searched “SLA VoIP” looking for uptime guarantees, you want a contract; this post is about the phone feature.

The feature travels under three names — shared line appearance, shared call appearance (SCA), and bridged line appearance (BLA) — depending on which platform you’re standing on. All three describe substantially the same thing: the behavior of the old key telephone system, where every CO line had its own lit button on every phone, recreated over SIP. If you’re replacing an aging Panasonic or Nortel key system as POTS lines get retired, this is the feature that makes the new phones behave the way the office expects.

What a shared line actually does

A shared line group gives every member phone a line key for the shared line. The key’s lamp tells you the line’s state at a glance — idle, ringing, or in use. On most phones, green means you’re on the call and red means someone else in the group is.

The behaviors that define a true shared appearance:

• Anyone answers. An inbound call rings the shared line on every phone in the group; whoever picks up takes it.
• Anyone dials out as the line. Outbound calls from any phone in the group present the shared line’s identity, not the individual extension.
• Hold travels. Put a call on hold at the front desk, walk to the back office, press the same line key, and resume it there.
• Hold can be private or open. Most implementations offer both modes: private hold means only the phone that held the call can retrieve it; open hold means any phone in the group can. There is no universal default — it varies by vendor, so check yours.
• Barge-in. Many platforms let another group member press the lit line key to join an active call on the shared line, usually gated behind an “allow barge” setting. Note the scope: this is joining your own shared line’s call, not the supervisor barge used for call-center monitoring — different feature, same word.

Three names, one feature: SLA vs SCA vs BLA

Which term you hear depends on whose platform you’re configuring:

Term	Expansion	Who says it
SCA	Shared Call Appearance	BroadSoft/BroadWorks platforms, and phone vendors integrating with them (Yealink, Cisco SPA docs, FusionPBX’s “Broadsoft SCA” mode)
BLA	Bridged Line Appearance	Polycom/Poly documentation and some hosted platforms; the term traces to an expired IETF draft
SLA	Shared Line Appearance	Asterisk (its feature is literally named SLA) and most cloud providers — RingCentral, Vonage, 8x8, GoTo — often just “shared lines”

Treat them as interchangeable when you’re evaluating platforms, with one operator’s caveat: the name on the datasheet doesn’t guarantee the depth of the implementation. Asterisk’s SLA, for instance, is more limited and dated than BroadWorks-style SCA — true hold-here-resume-there behavior across phones historically wasn’t fully supported. Same acronym family, very different mileage.

Shared line vs BLF vs call pickup

These three get conflated constantly, and buying the wrong one is a common small-office mistake. A BLF (busy lamp field) key is monitor-only: it watches another extension and lights up when that extension is busy or ringing, sometimes with directed pickup attached. It is not an appearance of the line — you can’t place calls on a BLF key and you can’t resume its held calls. Call pickup is narrower still: a one-shot grab of a ringing call on another extension via feature code or pickup key.

Capability	Shared line appearance	BLF key	Call pickup
Continuous line-state visibility	Yes	Yes (lamp only)	No
Answer a ringing call	Yes	Only with directed pickup	Yes (ringing state only)
Place outbound calls as the line	Yes	No	No
Resume a call held elsewhere	Yes	No	No
Join (barge) an active call	Often, if enabled	No	No
What it watches	A line/trunk	An extension	Nothing (on-demand)

One clarifying wrinkle: shared-line implementations often use BLF-style lamps to display line state. The lamp and the appearance are different things — the lamp shows you the state, the appearance gives you the line.

How it works over SIP

There is no single ratified IETF standard for shared line appearance; every implementation defines its own behavior, which is why the phone and the server must be configured for the same mechanism — a phone speaking the expired-draft BLA dialog method won’t interoperate with a server expecting BroadSoft’s SCA event packages, regardless of what either vendor’s datasheet calls the feature. At a high level, phones learn line state through SIP SUBSCRIBE/NOTIFY event subscriptions: each phone subscribes to the shared line’s state, and the server notifies the group as appearances change.

The most documented flavor is BroadSoft’s, built on its call-info and line-seize event packages. Phones subscribe to the shared address-of-record for call-info events and receive NOTIFYs as line state changes. When a phone goes off-hook on the shared line, it sends a line-seize subscription and the server assigns it an appearance index — and that subscription is deliberately short-lived, so a phone can’t camp on an appearance it isn’t using. Kamailio’s sca module implements this model, and FreeSWITCH and FusionPBX offer compatible modes. The practical takeaway: both the server and the phone must speak the same mechanism, which is why supported-device lists exist.

Who shared lines are for

Executive and assistant. The canonical case. The assistant sees every call on the boss’s line, answers and screens, places outbound calls that present the boss’s identity, and picks the boss’s held calls back up. Microsoft Teams implements this pattern as “shared line appearance” via call delegation — delegates answer and place calls on behalf of the boss, resume the boss’s held calls, and join active calls — enabled through Teams calling policy (delegation is on by default). Teams’ version is delegation-based rather than SIP line keys, but the workflow is the same.

Front desk and reception. One published number, answered wherever someone happens to be standing — counter, back room, manager’s office.

Small retail and branch offices. “The phone” is a single main line and everyone covers it. This is precisely the workflow the old key system delivered, and it’s the reason shared lines are the first feature to check when you’re replacing a key system with a cloud PBX.

How to get it: cloud vs on-prem reality

On a cloud PBX, shared lines are usually an admin-portal feature — a checkbox, not a project. But you get the vendor’s flavor with the vendor’s constraints. RingCentral, for example, currently restricts shared lines to specific supported desk-phone models — no softphone, no mobile app — recommends the phones sit at the same physical location, and caps how many lines and phones a group can hold. 8x8 and GoTo Connect expose shared-line key assignment in their admin consoles; Vonage offers it as a feature. The operator’s rule: confirm the platform’s shared-line limits and supported-device list before you promise the feature to anyone.

On-premises and open-source, support is uneven. FreeSWITCH and FusionPBX handle SLA/BroadSoft-SCA modes, Kamailio has a dedicated module, Asterisk’s implementation is limited (see above), and some popular PBXs still don’t do true shared appearances at all. Phone-side, you need desk phones with programmable line keys — Yealink, Poly, Cisco — matched to the server’s mechanism. If you’re weighing whether to run that stack yourself or let a provider host it, our hosted PBX vs SIP trunking comparison covers the tradeoff.

Frequently asked questions

What does SLA mean in VoIP?

In VoIP feature lists, SLA means shared line appearance: multiple phones share one line, all of them see its live status, any of them can answer, dial out as the line, or resume a call held on another phone in the group. The same acronym also means service level agreement — the contract covering uptime and support response. Context tells you which one a document means: phone-feature pages mean shared lines; contracts and provider comparisons mean the agreement.

Are SLA, SCA, and BLA the same thing?

Substantially, yes. Shared line appearance (SLA), shared call appearance (SCA), and bridged line appearance (BLA) all describe multiple phones sharing a line with full answer, dial-out, hold-retrieve, and often barge capability. SCA is the BroadSoft/BroadWorks term, BLA comes from Polycom and some hosted platforms, and SLA is what Asterisk and most cloud providers call it. The names are interchangeable; the implementations are not — depth varies by platform, so verify the specific behaviors you need.

Is shared line appearance the same as BLF?

No. A BLF (busy lamp field) key only monitors another extension — it lights when that extension is ringing or busy, and at most lets you grab a ringing call with directed pickup. A shared line appearance is a full appearance of the line: you can answer on it, place outbound calls that present the line’s identity, resume calls held on other phones, and often barge into an active call. Confusingly, shared-line setups typically use BLF-style lamps to show line state, but the lamp is just the indicator — the appearance is the capability.

Can I use a shared line on a softphone or mobile app?

Often not. Shared lines generally depend on physical desk phones with programmable line keys, and some cloud platforms explicitly exclude softphones and mobile apps from shared-line groups — RingCentral currently limits the feature to specific desk-phone models, for example. If your team is mobile-first, look at ring groups or call delegation instead, which deliver answer-anywhere coverage without requiring line keys. Check your provider’s supported-device list before building a workflow around shared lines.

Does Microsoft Teams support shared line appearance?

Yes, through call delegation rather than SIP line keys. A boss designates delegates who can answer and place calls on the boss’s behalf, pick up calls the boss put on hold, and join active calls. It covers the exec/assistant workflow that shared lines were built for, controlled through Teams calling policy, with delegation available by default. What it is not is a key-system emulation — there are no shared line keys lighting up across a row of desk phones.

---

The key-system workflow this post describes is exactly what SIPNEX’s own cloud PBX is priced for — $6.99 per extension monthly, from an FCC-licensed carrier, with A-level STIR/SHAKEN attestation on outbound calls. Replacing a key system? We port your existing numbers with no port-in fees, simple ports in 7–14 business days. Talk to an operator or see rates.