Related models, part IDs, serial numbers typically fall into this category. What physical and virtual boxes we have: Voice and UC equipment, virtual machines, PRI and DSP modules, etc. You can typically find such files in most organizations. How it was designed and expected to work. Solution design documents and implementation summaries.To begin with, I would break the pieces of the information we are usually interested in and keeping track of as follows: “What is the problem with that?” you may ask. Dedicated domain-specific documenting solutions for Voice and UC are not that common in the enterprise sector. Based on discussions with other engineers, this is quite typical. It is a good question, how representative this sample is. However, regardless of the region and size, they all shared one thing in common: the documentation related to Voice and UC relied on Microsoft Office and PDF files stored in a more or less structured fashion. I’ve been managing and consulting on Voice and UC deployments serving thousands of users and consisting of hundreds of voice devices and circuits in total. I have seen many examples of how the documentation can be organized since 2011 when I started my career.
Using NetBox as Voice and UC Source of Truth might be a good idea. TLDR: I developed a new plugin for NetBox to manage phone numbers and more. Sounds painfully familiar? I have got something that might help. Do we have a spare phone number for a new service?.Which of these Excel files contains the information I need?.What phone number is that? Where it comes from?.Have you ever been struggling with an enterprise Voice and Unified Communications infrastructure
0 kommentar(er)
