HP Poly Rove B4 multicell DECT base

Turn headline scale into a surveyed system design

HP publishes three different system quantities: up to 254 B4 bases, up to 1,000 SIP registrations and up to 2,000 concurrent calls. They measure different objects and do not establish a deployable site by multiplication. Record buildings, floors, users, handsets, call concurrency, codecs, coverage zones, synchronization paths, repeaters, PBX and trunk capacity before choosing a base count.

Treat every maximum as a manufacturer boundary. A large registration total does not prove radio capacity at one cell, and a call total does not prove sufficient PBX, network or carrier capacity. Use the current site-planning guide and a physical survey to produce base locations, overlap, synchronization and busy-hour acceptance cases.

Keep radio coverage and synchronization observable

The published indoor and outdoor range values are environment-dependent planning inputs, not a radius to draw on a floor plan. Survey with doors, lifts, walls, shelving, machinery, people and interference represented. Preserve each base identity, radio band, synchronization source, RSSI or other documented measure, neighbor relationship and intended handover path.

Test a controlled call through each required movement path and repeat at the busy-hour concurrency expected for that zone. A handset associated with a nearby base does not prove that the base has a healthy synchronization path, that handover occurred, or that both media directions remained usable.

Design network, subnet and failure behavior deliberately

Inventory switch port, PoE source, VLAN, addressing, multicast or broadcast dependency, routing and management ownership for every base. Current HP release notes retain a boundary for group paging across subnets: multi-subnet base systems still require the switching design to carry the necessary multicast traffic. Do not treat general IP reachability as proof that paging or every multicell function crosses the same boundary.

Test loss and restoration of one base, switch path and power source with provider-approved traffic. Separate established-call survival, new-call routing, handset re-association, SIP registration and return to the preferred cell. A running secondary cell is not proof that all calls, identities or features survived.

Control firmware, backup and protection as separate layers

Record the exact firmware on every base and handset, configuration owner, backup scope, release notes, staged upgrade order and rollback package. Current HP release notes warn that a B4 backup with Include Running Status selected can reboot the base. Treat backup as a controlled change with an outage plan rather than as a harmless read.

DECT radio encryption, HTTPS management, SIP TLS, certificate validation and SRTP are different paths. Prove the configured and negotiated state of each required path; do not infer PBX-facing protection from DECT certification. No Rove B4 base, handset, repeater, survey, synchronization path, network, PBX, credential, registration, firmware, protection control, availability, compatibility, price, emergency route, audio path or live call was inspected or tested for this reference.

Diagnose a roaming failure from one recorded walk

When a Rove call drops or audio fails while the handset moves, use the B4 roaming diagnostic. It separates serving-cell RSSI, synchronization chain, DECT handover, SIP state, codec capacity and both media directions.