Clarification

Article

Clarification

Errors in a recent SearchITChannel.com story about a large-scale PBX-to-IPTelephony migration at Navigant Consulting, Inc. led to several misattributed

To continue reading for free, register below or login

Requires Membership to View

To gain access to this and all member only content, please provide the following information:

By submitting your registration information to SearchITChannel.com you agree to receive email communications from the TechTarget network of sites, and/or third party content providers that have relationships with TechTarget, based on your topic interests and activity, including updates on new content, event notifications, new site launches and market research surveys. Please verify all information and selections above. You may unsubscribe at any time from one or more of the services you have selected by editing your profile, unsubscribing via email or by contacting us here

  • Your use of SearchITChannel.com is governed by our Terms of Use
  • We designed our Privacy Policy to provide you with important disclosures about how we collect and use your registration and other information. We encourage you to read the Privacy Policy, and to use it to help make informed decisions.
  • If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States.

quotes and one erroneous description of a new piece of networking infrastructure.

  • In How to unify a network when the company keeps expanding, which was posted Jan. 19, it was Joe Kennedy, of Navigant's network operations and service desk who said: "When [we're] asked what PBXes did we have, our CIO likes to say 'all of them.'"

  • It was Mike Dongvillo, Navigant's network architect who said about the installation and replacement of a WAN backbone: "It has worked -- knock on wood—solid as a rock, for the most part. But [the experience] was a forest fire."

  • Dongvillo asked SearchITChannel.com to clarify that the network infrastructure piece supplied by Sprint was an IP-based virtual private network, which went into place without enough testing to reveal that it couldn't deliver the quality of service required for the VoIP network.

    Sprint acknowledge the error and replaced it at no charge with its higher-performing MultiProtocol Label Switching VPN service. The switch delayed the project several months.

  • A cost analysis was done on the project, but the estimates were "about 20% inaccurate," Dongvillo said, because of the variability and unknown configurations of networks in remote or newly acquired business units.