Current Location ：
Office Moves and Relocations: A Voice Infrastructure Checklist
An office move looks like a facilities project and turns into a voice project, usually a few weeks later when someone tries to plug a phone into a socket that carries data only. Voice has requirements that data networking does not: Power over Ethernet at every port, defined voice VLANs, tested uplink capacity for call traffic, and trunk provisioning that can be moved without losing the existing numbers. Planning voice early removes most of the friction.
Start With Number Continuity
The hardest constraint in a relocation is usually the telephone numbers, not the equipment. Numbers are tied to the incumbent carrier's serving infrastructure and cannot always move with the hardware. Establish early whether numbers can be retained, what the porting lead time is, and whether a new interim arrangement is needed. Every day this is unresolved is a day of risk at move day.
What to confirm with the carrier
- Whether existing numbers port to the new provider and the realistic lead time
- Whether the current trunk numbers are portable given the new address registration
- Whether emergency calling and registered addresses need updating for the new location
- Whether the move requires new provisioning or can be a configuration change
- Whether a temporary arrangement is acceptable if porting cannot complete by move day
The Physical Layer Checklist
| Item | Requirement | Why it matters |
|---|---|---|
| Power over Ethernet | PoE at every intended phone position | Phones without PoE need local power; adapters fail in clusters |
| Voice VLAN | Separate VLAN with configured access ports | Keeps voice traffic isolated and simplifies QoS |
| Switch capacity | Uplink sized for concurrent call streams | Under-provisioned uplinks cause voice degradation under load |
| Cable certification | Certified cabling with correct wiring at each outlet | Most first-day faults are cabling, not telephony |
| Outlet labelling | Every outlet labelled to match the floor plan | Moves and adds become guesswork otherwise |
| Power and UPS | Backed-up power at the comms room and any rack | A move often reveals an unprotected power dependency |
| Rack and cooling | Rack space and cooling for platform and gateways | Equipment arrives before rack space is ready |
Platform and Trunk Cutover
- Take a full configuration backup from the existing platform before any change
- Confirm the new site has the platform model and license count required
- Pre-stage trunk provisioning so cutover is a configuration change, not a carrier project
- Schedule the cutover outside business hours with a defined rollback path
- Verify outbound and inbound calls, then transfer quality, then recording
- Confirm emergency calling from the new site before declaring the move complete
Endpoint and Asset Planning
Moves are a natural point to refresh endpoints. Handsets that have been in service for several years are the most likely source of user complaints after a move, because old cabling and old power adapters get reconnected in new positions. Planning a partial handset refresh during the move is usually cheaper than handling failures afterwards.
A Two-Week Countdown
- Day 1 — Carrier port confirmed and paperwork submitted; cabling contractor mobilised
- Day 3 — Voice VLAN and PoE validated at every outlet, not just sampled
- Day 5 — Platform installed, licensed, and configured offline with a config backup taken
- Day 7 — Trunk provisioning complete and tested to the new site
- Day 9 — Endpoints distributed and labelled; numbering plan loaded
- Day 11 — Emergency calling tested; recording and voicemail verified per site
- Day 13 — Cutover window; rollback plan confirmed and staffed
- Day 14 — Hypercare: on-site support for the first full working week
Redstone Approach
Redstone provides relocation planning support including platform configuration backup, numbering plan design for the new floor layout, trunk provisioning coordination, and a cutover test plan. Redstone can also advise on handset refresh timing so endpoints are not the weak point in week one of a new site.
Redstone supports office relocation projects with voice infrastructure checklists, configuration backup and restore, and per-site verification of calling, recording, and emergency routing.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
