Review addressing and name resolution for voice devices
Check whether voice VLAN, DHCP, DNS and route records still match the working network.
From the blog
Practical observations from planning, deploying, testing, monitoring, and operating business phone systems.
Check whether voice VLAN, DHCP, DNS and route records still match the working network.
Compare a failing phone with a working one across addressing, name resolution, routing and call traffic.
Record addressing, VLAN, DHCP, DNS and routing dependencies before changing a voice network.
Use a short monthly audit to catch stale carrier contacts, number routes, firmware standards, recovery steps and undocumented phone-system changes.
Confirm that the PBX discovers, selects and recovers between SIP SRV targets without waiting for a carrier server to fail in production.
Give the carrier timestamps, direction, call identifiers and measured media evidence so an intermittent voice fault can be traced quickly.
A carrier access migration and a PBX hosting migration are separate projects. Keep the existing PBX while replacing PRI with SIP when the boundaries support it.
Router phones can remove a separate branch appliance, but they also combine a user endpoint and a network dependency. Use this decision test.