Like Rob said, you can do this...it will work. Often times companies will reserve "vanity" numbers for future use and delegate other things out. One thing to consider though is scalability and overlap. Let's say that this works great now but in a year or two (take your pick), Company XYZ grows and picks up another office location down the street and want to centralize on the existing cluster. Let's say they also "insist" on 4-digit dialing at the new site or between offices and all or even part of the DID range purchased for the new location overlaps with the existing dial plan. Granted, this may never happen but I point it out because I've seen it before and, in fact, my company is often called upon to clean up dial plans that have issues or just don't scale. So, you could consider a multi-tenant design and base the root of the system configurations on a full 10-digit dial plan. What does this do for you? Well, if done right - you can offer the best of both worlds now and simplify things in the future. With a single translation pattern, all users could dial 4 digits now while the system handles the full NANP number in the background. When Company XYZ expands, the new office users can dial 4-digit as "insisted" within their buidling as well. For inter-tenant calling, you could use a site code (or digit) + 4-digits or just treat calls as 7-digit or 10-digit local (based on local dialing plan) but with calls traversing the WAN/MAN as opposed to the PSTN (which could be used as a backup).
Just some thoughts...
Hailey
Please rate helpful posts!
