Home Video Conferencing Yealink Divisible Room Solution
Yealink divisible room solution — AP08 audio processor and YPS20 partition sensor automate wall-open and wall-closed configurations for hotels, training centres and event venues in Dubai
YEALINK PREMIUM PARTNER — MEA · DIVISIBLE ROOM SYSTEMS, DESIGNED & INSTALLED

Yealink divisible room solution for Dubai & the UAE.
The wall moves. The rooms follow. No technician required.

The ballroom splits into two boardrooms on Tuesday, runs as a full hall on Wednesday, and divides again for Thursday training. Every configuration is a separate booking and a separate revenue line — but only if the AV follows the partition without a technician present every time. This page is that system: Yealink's dual MVC architecture, YPS20 partition sensing, AP08 audio automation, and the engineering that makes three configurations work from one investment. Vector Digital Systems — Yealink Premium Partner for MEA, designing and installing divisible room systems across all seven UAE emirates since 2009.

Three configurations — one investment
  • Room A only — independent meeting, isolated audio
  • Room B only — independent meeting, isolated audio
  • Combined venue — one meeting, both sides
  • Wall moves → rooms reconfigure automatically
  • No IT intervention, no AV technician on standby
  • Every configuration commissioned before handover
In stock — Dubai warehouse
Installing since
2009
Partner status
Premium Partner MEA
Stock
Dubai warehouse
Export reach
45 Countries

The venue had three configurations. The AV had one.

This is the standard story in Dubai hotels, training centres and event venues. And the cost is not the AV — it's the person who has to reconfigure it every time.

A 300-seat hotel ballroom. The events manager books it three ways: full hall for conferences, left half for corporate training, right half for boardroom dinners. Three sellable products from one space — which is exactly how the hotel justifies the square footage.

The AV told a different story. One system, one camera at the front, microphones covering the full space, speakers running wall to wall. Wall closed: the training session on the left could hear the boardroom dinner on the right — not clearly, but enough. The camera on the training side showed participants on both sides when the wide shot was on. And every Monday morning, before the first event, an AV technician arrived to reconfigure the system for whatever the week's bookings required. If the technician was sick, the events coordinator called the AV company. If the AV company couldn't send someone by 9am, the event started late.

This is the standard configuration of divisible rooms in Dubai. Not because nobody solved it. Because almost nobody who specifies AV systems mentions that it can be solved. The Yealink divisible room architecture solves it at the wall. An infrared sensor detects whether the partition is open or closed. That information tells both room systems what configuration they are now in. Wall closed — two independent meetings, audio zones separated so neither room hears the other. Wall open — one combined venue, cameras and audio merged, one console running both sides. The technician's job disappears.

Say it simply: the wall tells the rooms what to be.

The mechanism · YPS20 + AP08 + Room Designer

Three devices and a wall — how the Yealink system knows what the room is

The mechanism is simpler than the problem it solves. Here is the full chain, from wall movement to room configuration.

The YPS20 partition sensor

An infrared sensor the size of a smoke detector mounts on the wall beside the partition track. Its job is one fact: is the wall in the closed position or the open position? Infrared diffuse-reflection technology detects the wall's presence within 1.5 metres. Adjustable sensitivity handles rooms where the partition doesn't always stop in exactly the same position. A 10-metre cable runs from the sensor to the AP08 processor. Two LED indicators show wall state at a glance. The sensor fires continuously — it doesn't wait to be asked.

The AP08 audio processor

The AP08 is Yealink's audio DSP for large and divisible rooms. It has 16 Dante audio channels, 3 PoE+ LAN ports that power ceiling microphones and speakers directly, and 2 USB-B ports — one for each room system's Windows engine — operating simultaneously. The GPIO interface accepts the YPS20's wall-position signal and translates it into a room configuration preset. Wall closed: audio routing switches to two isolated zones. Wall open: zones merge. Automatic EQ adjustment runs on the CS10-D ceiling speakers based on Teams meeting status.

Room Designer presets

Yealink's Room Designer software holds the configuration presets — "divided" and "combined" — as named states. The AP08 reads the wall position from the YPS20, matches it to the correct preset, and applies it. Each preset carries the full routing definition: which microphones feed which USB-B port, which speaker zones are active, which Teams or Zoom session receives which audio. The transition takes seconds. The IT manager sets up the presets once during commissioning. Nothing further is required.

Two complete MVC systems

The critical architectural decision: not one system with a split mode, but two complete and independent MVC systems — one per side of the partition. Each side has its own camera, its own MCore 4 engine, its own MTouch Plus console, its own Teams or Zoom licence. Wall closed: Room A and Room B are fully independent — neither system knows the other exists. Wall open: Yealink's official divisible room merge links both systems through the AP08 and the AVHub, coordinating cameras from both sides as a single intelligent feed. Two complete systems, not one system with a toggle.

Yealink YPS20 partition sensor — how it works in a divisible room, wall closed vs wall open, GPIO chain to AP08 Room Designer presets

YPS20 automation chain — wall closed/open → IR detection → AP08 GPIO → Room Designer preset → divided or linked configuration. Click to enlarge.

Yealink YPS20 partition sensor — how it works in a divisible room, wall closed vs wall open, GPIO chain to AP08 Room Designer presets — full size
The video director · AVHub

The Yealink AVHub — how cameras connect and who decides the shot

The AVHub is the video processing hub that sits at the centre of a multi-camera MVC room. Every UVC86 camera connects to it via Cat cable using Yealink's own VCH camera link — not the building LAN, not USB, Cat cable. Long cable runs, no USB distance limits. The AVHub accepts the camera feeds, applies the director logic, and sends one clean video output to the MCore 4 Teams engine over a single USB 3.0 connection.

9
Max cameras
Up to 9 UVC86 cameras per AVHub — each connects via Cat cable, each tracks independently
1
USB to MCore
One USB 3.0 cable carries all camera feeds from AVHub to the MCore 4 engine — clean and simple from the rack
2
AVHubs in divisible room
One AVHub per side when the wall is closed. When open, they link via the official Yealink divisible merge — one combined feed
🎬
How the director logic works
Each UVC86 tracks the active speaker using its own built-in microphone arrays and face detection — the AVHub does not steer the cameras. What the AVHub does is decide which camera's tracked view goes live to the Teams call at any moment. Wall closed: each AVHub directs its own room's cameras independently. Wall open: the linked AVHubs coordinate across both rooms, cutting to whichever camera has the active speaker — from either end of the hall.
Yealink AVHub connection diagram — cameras connected via Cat cable to AVHub video processor, one USB 3.0 to MCore 4 Teams engine, showing the AP08 integration path for divisible room coordination

AVHub architecture — cameras connect via PoE Cat cable, one USB 3.0 to MCore 4. In a divisible room, the AP08 sits between the AVHub and both room systems, routing audio zones per wall state. Click to enlarge.

Yealink AVHub connection diagram — full size

Three states — what the room is, what it does, and how the AV knows

The divisible venue is never ambiguous. It is in one of three configurations, and the system knows which one automatically.

State 1
Room A — independent
  • Wall closed, left side in use
  • Room A runs its own Teams or Zoom session
  • Room A cameras, ceiling mics, console — independent
  • AP08 routing: Room A microphones feed only Room A's system
  • Room B is acoustically and electronically absent
  • Two simultaneous meetings possible — zero crosstalk
State 2
Room B — independent
  • Wall closed, right side in use
  • Room B runs its own Teams or Zoom session
  • Room B cameras, ceiling mics, console — independent
  • AP08 routing: Room B microphones feed only Room B's system
  • Whatever happens in Room A is irrelevant to Room B
  • The booking that paid for Room B gets Room B — cleanly
State 3
Combined venue
  • Wall open — Yealink official divisible merge activates
  • Both MVC systems link through AP08 and AVHub
  • Cameras on both ends serve one meeting — director logic coordinates
  • Ceiling mic zones from both sides join — one audio field
  • One console commands the whole space
  • Town hall, full-hall conference, combined training — one meeting at scale

Nobody presses a button. Nobody calls IT. The wall moves — the rooms follow. This is not a feature in the settings menu. It is how the hardware is architected.

The two states · what actually happens

Partition closed vs partition open — what every room, camera and microphone does

This is the question that comes up in every client conversation. Here is the complete answer for both states.

State: Partition closed
Two independent rooms.
Two separate meetings.
Room A
📹
Camera · Mics · Console
Own Teams call
PARTITION
Room B
📹
Camera · Mics · Console
Own Teams call
What happens in each room
Room A
  • ✓ Room A camera frames Room A only
  • ✓ Room A ceiling mics → Room A's MCore
  • ✓ Room A MTouch Plus controls Room A
  • ✓ Room A speakers play Room A's far end
  • ✓ Room A joins Teams independently
Room B
  • ✓ Room B camera frames Room B only
  • ✓ Room B ceiling mics → Room B's MCore
  • ✓ Room B MTouch Plus controls Room B
  • ✓ Room B speakers play Room B's far end
  • ✓ Room B joins Teams independently
AP08 does this automatically
YPS20 detects wall closed → AP08 switches to divided preset → Room A microphones route exclusively to Room A's USB port, Room B microphones route exclusively to Room B's USB port. Neither side hears the other's meeting.
Client experience
The person in Room A has no idea Room B exists. Same in reverse. Two separate, complete meeting rooms. Zero audio bleed. Zero camera overlap.
State: Partition open
One combined venue.
One meeting at scale.
Room A + Room B
📹     📹
Both cameras · All mics
One combined session
OPEN
AVHub + AP08
🔗
Director · Audio merge
Linked automatically
What happens in the combined venue
  • Both cameras feed the AVHub simultaneously — director AI picks the active speaker's angle
  • All ceiling mics from both sides merge into one audio field — one complete room pickup
  • Both displays show the same meeting content — same far-end participants on every screen
  • Either MTouch Plus can control the combined session — stage side or back of room
  • No manual switching — wall opens, system reconfigures, meeting continues
AP08 does this automatically
YPS20 detects wall open → AP08 switches to combined preset → all microphone zones route to a single merged audio path → AVHub coordinates both camera feeds as one intelligent multi-camera system.
Client experience
One large room. One meeting. The camera cuts to whoever is speaking — from either end of the hall. The far end sees the active speaker cleanly framed, not a wide shot of 100 people.
The transition is automatic — nothing for the client to do
The wall moves. The YPS20 reads the new position. The AP08 applies the correct preset. Room A and Room B reconfigure — cameras, microphones, speakers, display routing — before anyone has touched a console. The meeting continues. The technician is not required.

The detail everyone misses — audio zone isolation

Two rooms that share a wall share a problem: sound travels through walls. The question is whether the microphone on the wrong side picks it up and amplifies it.

Without audio zone isolation, both rooms' microphone arrays pick up everything in the combined space — beamforming tries to suppress the other side, but imperfectly, and what arrives at the far end of each Teams session is a mixed signal with the wrong meeting audible in the background. This is the scenario most Dubai divisible rooms currently operate in, because the specifier gave each side a microphone and assumed that was enough.

The AP08 solves this at the routing level. When the wall is closed, the AP08 assigns specific CM20 ceiling microphone units to specific USB-B output ports — Room A's microphones to Room A's MCore 4, Room B's microphones to Room B's MCore 4. The routing is absolute: Room B's CM20 units send audio exclusively to Room B's system. The wall's imperfect acoustic separation becomes a physical background noise issue — not an amplified problem in the call — because the microphones on each side are feeding their correct systems only.

The zone design is a survey deliverable, not a day-of decision. We map the ceiling microphone positions against the partition track before specifying unit counts. At the UAE venue we designed — 17m × 7.2m with a partition at the 8-metre line — the zone assignment determined the CM20 count (5 units) and CS10-D count (6 units) in the final design. The number isn't a catalogue default. It's the answer to the geometry of that room's partition and ceiling.

Say it simply: the zones are designed before anything is ordered — because the microphone routing is the isolation.

Camera placement in a divisible room — Yealink's 8m and 10m deployment rules

The most common camera mistake: placing cameras for the combined space and assuming they serve the divided configuration too. They don't.

A camera positioned to cover a 17-metre hall covers 17 metres when the hall is combined. When the wall closes and Room A is 8 metres deep, that camera's zoom, field and focus were calibrated for a room twice the size. The far-side seats in the now-8-metre room appear in correct scale. The near-side seats appear too large and too close. It's wrong — not broken, but wrong.

Yealink's own deployment guide gives two distance rules for the UVC86: 8 metres for standard quality and 10 metres with optical zoom engaged. These are the rules we apply when positioning cameras in each half of a divisible venue. Room A at 8m: one UVC86 at the front of Room A, pointed down the 8-metre length. Room B at 8.8m: one UVC86 per side or running in optical zoom mode, depending on seat count and table layout.

In the combined configuration, both cameras serve the AVHub as a multi-camera system — the director logic coordinates between them, cutting to the active speaker regardless of which side they're on. The combined venue gets both-sides coverage. Each divided room gets its own camera, sized for its own depth.

The partial partition problem

At the UAE venue we built, the partition opened to a partial passage — not a full-width opening. This invalidated our initial combined-venue camera geometry, which assumed a wide open space. The actual combined configuration has a structural element that constrains the sightline from one end. We caught this at survey, redesigned the camera positions for the actual open geometry, and commissioned both states against the physical wall before handover. Survey before design. Design before order. This is the sequence that catches the partial-opening problem before installation day.

In the combined state — wider coverage

With both cameras live and the AVHub directing between them, the combined venue has full-width coverage from both ends — the director logic finds the active speaker and cuts to the camera with the best angle, regardless of which side. A town hall of 200 people: both camera positions serve one session, one intelligent feed, no manual switching. The director handles it. The MTouch Plus on the stage side can switch to a fixed layout or custom arrangement mid-meeting if needed.

Yealink UVC86 camera tracking — built-in mic arrays and face detection, no audio DSP required for tracking, AVHub is director not sensor

The UVC86 tracks with its own microphone arrays and face detection. The AP08 audio chain never triggers or steers the camera — AVHub is the director, not the sensor. Click to enlarge.

Yealink UVC86 camera tracking — built-in mic arrays and face detection, no audio DSP required for tracking, AVHub is director not sensor — full size
BYOD · WPP30 · HDMI switching

Guest access and secondary displays — both sides, both states

BYOD and display routing in a divisible venue follow the wall state — automatically.

BYOD per side
Divided configuration
  • Each side has its own VCH51 Pro extender
  • Room A guest: one USB-C cable → Room A cameras and ceiling audio
  • Room B guest: one USB-C cable → Room B cameras and ceiling audio
  • Both guests on their own platforms simultaneously
  • Teams, Zoom, Meet, Webex — any platform
  • Unplug → room returns to native mode instantly
WPP30 per side
Wireless screen sharing
  • WPP30 dongle per room side — tap to share wirelessly
  • Guest plugs dongle into USB-A → laptop screen to room display
  • No HDMI cables across a long meeting table
  • Receiver sits in the room's sharing port permanently
  • In combined mode: active-side WPP30 serves the full hall
  • Survey establishes which side's console commands combined sharing
HDMI switching
Secondary and trolley displays
  • Any secondary display in the venue goes on the scope document
  • Trolley displays, overflow screens, side monitors — all named
  • AP08 GPIO state triggers contact-closure HDMI switching
  • Wall closed: Room B trolley mirrors Room B's content
  • Wall open: trolley follows combined session feed
  • Automatic — same trigger as the audio zone change
Survey · Design · Quotation

The six questions every divisible room survey asks

A divisible room quotation without a site survey is a guess with a price tag. These are the questions that turn the estimate into a specification.

1 — Partition track type and stop position

Is the partition sliding-stack, folding or operable? Where does it stop — full width of the space, or a partial passage? The camera geometry for the combined configuration depends entirely on whether the opening is full-width or partial. A partial stop position changes the combined-venue camera positions completely.

2 — Room dimensions on each side

Depth, width and ceiling height per side, not overall. Yealink's 8-metre standard and 10-metre optical rules apply to the room each camera serves when the wall is closed. These determine the camera count and zoom configuration per side separately from the combined state.

3 — Ceiling type and height

Solid concrete, suspended tile or open structure. Ceiling height in metres — 3m behaves differently from 5m. These inputs determine the CM20 microphone unit count and mounting positions. The zone isolation design depends on getting the ceiling geometry right before ordering.

4 — Acoustic isolation rating

What is the partition's STC rating? STC 45 (office standard) is different from STC 55 (good acoustic partition). Higher-rated walls need fewer microphone zone corrections; lower-rated walls require tighter zone assignment to compensate for what the wall lets through acoustically.

5 — Which side commands combined mode

Does Room A's console always command the combined state, or does it depend on the event? This determines console positioning, the WPP30 primary registration, and the pre-set structure in Room Designer. Getting this wrong means the operations team fights the system every time they merge.

6 — Secondary displays and trolley screens

Any display in the space beyond the primary wall-mounted screens. Trolley displays, overflow screens, side monitors — named on the scope document before design. Contact-closure HDMI switching handles them from the same AP08 GPIO logic as the audio zones.

These six questions produce the design. The design produces the quotation. The quotation names every component — sensors, processor, camera count, ceiling unit count, extenders, consoles and licences — as separate lines. What you approve is what arrives.

AP08 wiring · for integrators and technical buyers

AP08 — every port, every connection

How the existing venue PA system joins the Teams call — wireless receiver, audio mixer, amplifier and ceiling speakers all bridged through the AP08 to the MCore engine.

Yealink AP08 audio DSP wiring diagram — existing PA system bridge to Microsoft Teams, YPS20 GPIO connection, MCore USB audio path, Dubai

AP08 rear-panel connections — existing handheld receiver and mixer into Line Inputs, Line Out to amplifier, YPS20 sensor to GPIO In 1, USB to MCore Teams engine, LAN for Dante and management. Click to enlarge.

Yealink AP08 audio DSP wiring diagram — existing PA system bridge to Microsoft Teams, YPS20 GPIO connection, MCore USB audio path, Dubai — full size

Five venues in the UAE — and what each one is afraid of

The technology is the same. What changes is which failure the buyer cannot afford.

Hotels & venues

The AV fails at the biggest booking of the year

A hotel ballroom that splits into two training venues. The AP08 partition automation and YPS20 sensor reconfigure both sides without a human in the loop. The venue manager's job becomes the event, not the technology. Three configurations from one AV investment — Room A, Room B, and the full ballroom — with the system switching between them by itself. No technician call-out per partitioned booking.

Corporate training

The class on one side hears the session on the other

A corporate training hall splits for two parallel classes. AP08 audio zone isolation assigns each side's CM20 ceiling microphones exclusively to that side's system. Class A trains without audio contamination from the boardroom running in Class B simultaneously. The acoustic wall helps but the microphone routing is the isolation — and it's absolute.

Government & civic

IT cannot be on-site every time the configuration changes

A government building divides a chamber for committee work and reconvenes as a plenary. The IT department configures the Room Designer presets once during commissioning. Partition staff move the wall. The systems follow. IT is available for escalations, not for routine reconfiguration. The automation handles the daily reality without an engineer present.

Universities

Timetable changes require a configuration change nobody planned for

A large lecture hall moves to two parallel tutorials at short notice. Room Designer holds both configurations — the unified lecture and the divided tutorial. A timetable change means moving the partition and tapping the MTouch Plus. The AV adapts in seconds. Nothing needs to be programmed on the day.

Event venues

A mixed programme day requires three configurations without extra staffing

Morning keynote in the full hall. Afternoon breakout sessions in divided rooms. Evening dinner in the combined space again. Three AV configurations, one day, no additional AV staffing between transitions. The catering team moves the wall. The system switches. The event programme runs.

How VDS delivers divisible room projects

Surveyed, designed, staged and commissioned in both states

A divisible room is commissioned in both configurations — wall closed and wall open — before handover. This is not optional.

Survey with the six questions

Partition track type, stop position, both room dimensions, ceiling type and height, acoustic rating, which side commands combined mode, and every secondary display on site. Named before design starts, because these answers determine the system. An assumption at survey becomes a problem at commissioning.

Design on your floor plan

Camera positions drawn with their coverage zones per side. Ceiling mic grid with unit counts per zone and AP08 port assignments. Cable routes and the PoE budget per hub port. The full Room Designer preset structure for divided and combined states. You read the design and understand what the room will do before anything is ordered.

One line per component

The quotation names every camera, the AP08 processor, the YPS20 sensor, each ceiling unit, the two MCore 4 engines, the consoles, the BYOD extenders, the licences, the installation and the commissioning as separate named lines. Nothing hidden inside a bundled figure. What you approve is what arrives and what you pay.

Staged in Dubai before site

The full system — both MVC sets, AP08, YPS20, cameras, ceiling units — assembled, powered, firmware-matched and platform-enrolled in our Dubai warehouse. The divided presets verified on the bench. Installation day is mounting, cable-dressing and venue commissioning. Not diagnosing why the sensor isn't triggering.

Commissioned in both states

Wall closed first: Room A independent session run and verified. Room B independent session run and verified. Acoustic zone isolation confirmed — Room A cannot hear Room B in the call. Wall open: combined session run, director logic tuned to both-sides camera coverage. The handover document states which presets do what and who to call if a configuration fails.

Handover and documentation

Your operations team walked through which console commands each configuration. Room Designer preset names explained. The six survey decisions documented in writing — so any future engineer who arrives on site knows what the room is and how it was designed. Rooms outlast the people who built them. The documentation stays.

What a Yealink divisible room system costs in Dubai

Divisible room systems are scoped per venue. The range is real — a single-partition training room and a hotel ballroom with complex BYOD and overflow requirements occupy different points in it.

AED 80,000–120,000
Single-partition training room or boardroom
  • Two MVC systems — one per side, independent
  • YPS20 sensor + AP08 automation
  • Ceiling audio grid per side (CM20 + CS10-D)
  • BYOD extender per side, WPP30 per room
  • Teams Rooms Pro licence as named line per room
AED 120,000–200,000+
Hotel ballroom or multi-use event space
  • Dual MVC S90 systems with AVHub multi-camera coordination
  • AP08 with full Dante audio integration
  • Ceiling audio grid designed per side and combined mode
  • WPP30 pods, secondary display switching
  • Staged in Dubai before installation day
Scoped per venue
Council chamber, auditorium, ProAV
  • Dante backbone integration with existing audio infrastructure
  • NDI camera feeds to recording systems
  • Multi-room linked divisible systems
  • Contact-closure control to building management
  • Survey first — every line named before approval

Every quotation states both camera counts, the AP08, YPS20, ceiling units per side, both MCore engines, both consoles, both licences and installation as separate named lines. The number you approve before the project starts is the number at completion.

Six inputs to start — we produce the design

Partition type. Both room dimensions. Ceiling height and type. Acoustic rating if known. Which side commands combined mode. And any secondary displays on site. A floor plan photo helps. "Our ballroom needs to run as two rooms automatically" is enough to start the conversation. Survey scheduled within the week across all seven UAE emirates. Design and named-line quotation follows.

EXPORT FROM DUBAI

Divisible room systems exported from Dubai — staged before they ship

As an authorized Yealink distributor and Premium Partner for MEA, we export complete divisible room kits — both MVC systems, AP08, YPS20, ceiling audio, consoles — from Dubai stock, staged and preset-verified before dispatch. The receiving team mounts and commissions. They don't diagnose.

GCC & Levant

Hotel and government divisible builds

Saudi Arabia, Qatar, Oman, Bahrain, Kuwait, Jordan and Iraq — hotel ballrooms and government chambers where partition automation is specified but the local AV ecosystem lacks the engineering depth. Complete kits with the Room Designer preset structure documented per venue, staged in Dubai before dispatch.

Africa

Universities and training centres

Kenya, Nigeria, Ghana, Egypt and South Africa — universities and corporate training academies building divisible lecture halls and training rooms. Integrators buying AP08, YPS20 and MVC system stock with engineering documentation — the connection standard, GPIO wiring guide and preset structure — in the consignment.

South & Central Asia

Complete kits with commissioning documentation

Pakistan, Bangladesh, Sri Lanka and the Central Asian republics — per-room staging notes, mounting hardware and AP08 preset documentation in the same consignment. On-site commissioning starts from a checklist, not from a blank page. Both states — wall open and wall closed — verified before dispatch.

Export enquiries — country, venue type (hotel/corporate/university), partition count, Teams or Zoom.

WhatsApp the Export Desk →

What divisible room clients say

★★★★★

"We run back-to-back events in our ballroom. Before this system, the AV team reconfigured manually every time we split the room — two calls, two schedules, one technician on standby. Now the wall moves and both rooms are independently ready. We have not called an AV technician for a partition change since commissioning day."

Marwan Al Sayed, Director of Events — Hotel group, Dubai Direct Client
★★★★★

"Two groups train simultaneously in our split hall. The old setup had bleed — trainers heard the other session through the wall and it showed up in the calls. The microphone zone routing fixed it completely. Class A hears nothing from Class B, even during the loudest presentations. The acoustic wall helps, but the isolation is in the microphone routing."

Priya Menon, Head of Facilities — Corporate training provider, Business Bay Direct Client
★★★★★

"We specified the AP08 and YPS20 on a government council chamber project. The presets arrived verified — divided and combined states both confirmed before we touched the room. On-site integration took four hours. The client's IT team ran through both configurations independently without us present. That is the difference when the documentation and staging are done properly before dispatch."

Tariq Hussain, Senior AV Project Engineer — Systems integrator, Dubai Integrator

Yealink divisible room solution — common questions

What is a Yealink divisible room solution?
A configuration where two complete video conferencing systems share a space separated by a moveable partition — each system serving one side when the wall is closed, both systems merging into one combined venue when the wall opens. The Yealink divisible solution adds automation: a YPS20 infrared partition sensor detects the wall position and tells the AP08 audio processor which configuration to apply, so the rooms reconfigure automatically when the wall moves — without manual IT intervention or an AV technician standing by.
We move our partition wall every morning. Why does it currently need an AV technician?
Because the AV system was designed for one configuration and manual reconfiguration is the default. Without a partition sensor and automation, someone has to change camera inputs, re-route microphone zones, adjust speaker coverage and switch display sources every time the wall moves. The Yealink YPS20 sensor + AP08 processor handles all of this automatically — the wall moves, the AP08 reads the new position, and the system reconfigures. The technician's role disappears.
How does the YPS20 sensor know when the wall has moved?
Infrared diffuse-reflection: the sensor emits an infrared beam and detects whether the partition wall is within 1.5 metres. When the wall is closed, the beam reflects back. When the wall is open, it doesn't. This binary signal — wall present or wall absent — travels down the 10-metre cable to the AP08's GPIO interface, which uses it to select the correct room preset. Adjustable sensitivity handles partition tracks where the wall doesn't stop in exactly the same position every time.
What is the AP08 and why does the divisible room need it?
The AP08 is Yealink's audio DSP for large and divisible rooms. It has 16 Dante audio channels, 3 PoE+ LAN ports that power ceiling microphones and speakers directly, and — critically — 2 USB-B ports that operate simultaneously, one for each room system's Windows engine. This is what allows the AP08 to serve both MVC systems at the same time and route audio to the correct system based on the wall position. The GPIO port is where the YPS20's wall-position signal arrives and triggers the preset change.
We need Room A to be completely silent from Room B when the wall is closed — is that possible?
Acoustically, no wall eliminates all sound — the partition's STC rating determines how much sound passes through. But electronically, yes: the AP08 assigns specific CM20 ceiling microphone units to specific output ports by room preset. When the wall is closed, Room B's CM20 microphones send audio exclusively to Room B's system. They do not feed Room A's system. The acoustic leakage through the wall is a physical background that doesn't appear amplified in Room A's Teams session because Room A's microphones are not picking it up and routing it to Room A's call.
Why do we need two complete MVC systems — can't we split one system between two rooms?
Two complete systems is the correct architecture, and Yealink's own divisible room guide recommends it. One system with a split mode creates dependencies: if one side's MCore fails, both rooms go down. Two complete systems mean Room A works if Room B has an issue. Each side has its own Microsoft resource account, its own Teams licence, its own independent meeting capability. In the combined configuration, Yealink's official divisible merge links them through the AP08 and AVHub — but the independence when divided is built in from the start.
What happens when the wall is partially open — not fully open, not fully closed?
A real site condition that standard sensor setups can handle imperfectly. If the YPS20 sensitivity is calibrated for a binary closed/open position and the wall stops at an intermediate point, the sensor may give an ambiguous reading. At survey we document the partition's actual stop positions — full closed, full open, and any intermediate position used in practice — and calibrate the sensor sensitivity and AP08 presets against all of them. At a venue we built in the UAE, the partition opened to a partial passage rather than the full room width. This changed the combined-venue camera geometry entirely. We caught it at survey.
Does the system work with both Teams and Zoom?
Each room side is built for one platform — MVC for Teams, ZVC for Zoom. Both architectures use the same AP08, YPS20 and ceiling audio components. If both halves need the same platform, the design is symmetric. If one half needs Teams and the other Zoom, two different MVC and ZVC kits serve each side, with the AP08 handling audio routing for both. Mixed-platform divisible rooms are a survey conversation — the design is possible and we have specified them.
How many cameras does a divisible room need?
It depends on each half's dimensions. Yealink's UVC86 deployment rule: standard quality to 8 metres, optical zoom quality to 10 metres. A room divided at 8 metres typically needs one UVC86 per side for the divided configuration. In the combined configuration, both cameras serve the AVHub as a multi-camera system, with director logic coordinating between them. Where side dimensions extend past 10 metres, additional cameras may be required. Camera count is a calculated output of the survey — not an estimate.
Can you supply the AP08, YPS20 and cameras separately for integrators?
Yes. As an authorized Yealink distributor we supply AP08 processors, YPS20 sensors, UVC86 cameras, CM20 and CS10-D ceiling audio, MCore 4 engines and MTouch Plus consoles to integrators from Dubai stock. AP08 orders include the GPIO wiring guide, USB-B port assignment reference and the Room Designer preset structure for divided and combined states — the documentation that prevents the on-site diagnosis call. Staging before dispatch, with both presets verified, is available on request.
What are the six survey questions for a divisible room?
Partition track type and stop position (full-width or partial opening); each room's dimensions separately — depth, width and ceiling height; ceiling type (concrete, tile or open structure); acoustic partition rating; which side's console commands combined mode; and any secondary displays, trolley screens or overflow zones on site. These six inputs produce the design. The design produces the named-line quotation. Getting one of these wrong creates the problem the automation was meant to prevent.
What does a Yealink divisible room system cost in Dubai?
Single-partition training rooms and smaller corporate venues run AED 80,000–120,000 fully installed — two MVC systems, YPS20 sensor, AP08 automation, ceiling audio per side, BYOD extenders and consoles with licensing. Hotel ballrooms and multi-use event spaces with BYOD, WPP30 pods and overflow display switching run AED 120,000–200,000+. ProAV and council chamber builds with Dante integration are scoped per venue after survey. Every quotation states both camera counts, the AP08, both MCore engines, both consoles, both licences, installation and commissioning as separate named lines.
Which areas of the UAE do you cover for divisible room installations?
Vector Digital Systems designs, supplies, installs and supports Yealink divisible room systems across all seven UAE emirates — Dubai, Abu Dhabi, Sharjah, Ajman, Ras Al Khaimah, Fujairah and Umm Al Quwain. Within Dubai, active client sites include Business Bay, DIFC, Jumeirah Lake Towers (DMCC), Barsha Heights (TECOM), Dubai Internet City, Dubai Media City, Dubai Silicon Oasis, Downtown Dubai, Sheikh Zayed Road, Jebel Ali Free Zone (JAFZA), Dubai Investment Park (DIP), Dubai World Trade Centre, Dubai Healthcare City, Al Quoz, Deira, Bur Dubai, Al Barsha, Dubai Marina and Dubai South. Across Abu Dhabi and the Northern Emirates: Musaffah Industrial City (ICAD), Khalifa Industrial Zone (KIZAD), Masdar City, Al Ain, SAIF Zone (Sharjah), Hamriyah Free Zone, Sharjah Industrial Area, RAKEZ, Fujairah Free Zone and Ajman Free Zone.
Do you export Yealink divisible room systems from Dubai?
Yes. We export complete divisible room kits — both MVC systems, AP08, YPS20, ceiling audio, engines and consoles — from Dubai stock to 45 countries: Saudi Arabia, Oman, Qatar, Kuwait, Bahrain, Iraq, Jordan, Kenya, Ethiopia, Tanzania, Uganda, Rwanda, Burundi, Djibouti, South Africa, Mozambique, Zimbabwe, Zambia, Mauritius, Seychelles, Nigeria, Ghana, Senegal, Côte d'Ivoire, Cameroon, Angola, Togo, Benin, Congo DR, Gabon, Egypt, Morocco, Algeria, Tunisia, Pakistan, Bangladesh, Sri Lanka, Kazakhstan, Uzbekistan, Turkmenistan, Kyrgyzstan, Tajikistan, Georgia, Azerbaijan and Armenia — staged and preset-verified before dispatch, with per-room engineering documentation included.

The venue runs three configurations. The AV follows all of them — without a technician.

Partition type, both room dimensions, ceiling height. The AP08 preset design, camera positions per side, audio zone map, and a complete named-line quotation. Staged and preset-verified in Dubai before installation day.

💬 WhatsApp our divisible room team — reply within 30 min