ADAM PULSE Can a Zoom Phone user set a different ringtone for a specific line on a Poly desk phone?
Only for lines that are a true SIP registration or a static BLF (busy-lamp-field) entry. A non-primary shared line that is neither — i.e., a shared-line appearance or Shared Line Group member with no registration of its own — cannot be given its own ringtone on the Poly. That is a Zoom/Poly platform limitation, not a missed setting.
- Distinct per-line ringtones exist only for real SIP registrations and static BLF entries.
- The on-phone Attendant Calls setting is one ring for all monitored lines — it separates BLF lines from your primary line, not line from line.
- Genuine per-line control lives in provisioning:
attendant.resourceList.x.ringType, applied by Bind and Resync — not an end-user menu. - A shared-line appearance with no registration or BLF entry has no per-line ringtone anywhere — phone or Zoom portal.
- Ringtones picked in the Zoom desktop/mobile app affect the softphone only, never the desk-phone speaker.
Where is a ring actually decided on a Zoom-provisioned Poly?
A Poly running under Zoom Phone has three separate places a ring is decided, and only two expose a distinct ringtone:
1. Primary (registered) line
On the phone: Settings → Basic → Ring Type. This menu lists only real SIP registrations. A Zoom-provisioned Poly normally has just one registration (your extension), which is why other line appearances don't appear here to select — there's no separate registration behind them.
Provisioning equivalent: reg.x.ringType = "ringerN" (per registered line); global fallback np.normal.ringing.calls.tonePattern.
2. "Attendant Calls" ring (global BLF ring)
On the phone: Home → Settings → Basic → Ring Type → Attendant Calls. This sets one ring for all monitored/BLF lines at once. Use it to make your BLF lines ring differently from your primary line — but it is a single ring for the whole group and will not make line 5 ring differently from line 6.
3. Per-line BLF ringing (the real per-line control)
Distinct rings per monitored line come from the provisioning parameter attendant.resourceList.x.ringType (with global attendant.ringType as fallback). This is set in the provisioning template, then Bind and Resync the phone — it is not an end-user, on-phone menu. This is where genuine line-5-vs-line-6 differentiation lives.
How do you get distinct rings on specific lines in practice?
- Want distinct rings on specific monitored lines? Represent those lines as static BLF entries in the resource list and give each its own
attendant.resourceList.x.ringType. - Can a line be provisioned as a true second registration? Then its
reg.x.ringTypealso surfaces it in the phone's Basic → Ring Type menu for the end user to pick. - A non-primary shared line that is neither a registration nor a static BLF entry? No per-line ringtone exists — not on the phone, not in the user's Zoom portal.
What is the equivalent on Yealink desk phones?
- On the phone: Menu → Basic → Sound → Ring Tones (per registered line).
- To silence a monitored/BLF line instead of differentiating it: set that line's Ring Type to Silent Ring, or in the web GUI disable Audio Alert for BLF Pickup under Features → Call Pickup.
Do ringtones set in the Zoom desktop or mobile app affect the desk phone?
In Zoom Workplace app → Settings → Audio → Ringtones, a user can pick distinct ringtones for their Extension, Direct Number, Call Queue, Shared Line Group, and Shared Line Appearance numbers. Important: these govern the Zoom softphone ring, not the physical Poly/Yealink speaker. (Desk-phone sync applies to Zoom Phone Appliance-mode devices, not a standard-firmware Poly.)
Frequently asked questions
Why doesn't my second line show up in the Poly's Ring Type menu?
The Settings → Basic → Ring Type menu lists only real SIP registrations. A Zoom-provisioned Poly normally has just one registration — your extension — so other line appearances have no separate registration behind them and do not appear in that menu.
Can I make line 5 ring differently from line 6 on a Zoom-provisioned Poly?
Only if both lines are static BLF (busy-lamp-field) entries in the phone's resource list, each given its own attendant.resourceList.x.ringType value in the provisioning template. The on-phone Attendant Calls setting cannot do this — it sets one ring for all monitored lines at once.
Can end users change per-line BLF ringtones themselves?
No. Per-line BLF ring types are provisioning-template parameters (attendant.resourceList.x.ringType), applied by binding and resyncing the phone. They are not exposed in any end-user, on-phone menu or in the user's Zoom portal.
Will picking a ringtone for my Shared Line Group in the Zoom app change my desk phone's ring?
No. Ringtones chosen in Zoom Workplace app → Settings → Audio → Ringtones govern the Zoom softphone only, not the physical Poly or Yealink speaker. Desk-phone ringtone sync applies to Zoom Phone Appliance-mode devices, not a standard-firmware Poly.
How do I silence a monitored (BLF) line on a Yealink instead of differentiating it?
Set that line's Ring Type to Silent Ring on the phone, or in the Yealink web GUI disable Audio Alert for BLF Pickup under Features → Call Pickup.
Sources
- Zoom Support — Customizing Zoom Phone ringtones (KB0069244)
- Poly/HP PVOS Administrator Guide — "Distinctive Ringtones"; Poly Edge E / CCX Parameter Reference Guides (
attendant.resourceList.x.ringType,attendant.ringType,reg.x.ringType) - OnSIP — Setting a unique ring tone on a Polycom phone (Basic → Ring Type covers registered lines only)