- Bank Web sites full of security holes
- SCO Group: Its future is all used up
- Maligned feature being added to IPv6
- I returned my iPhone 3G after six days!
- VPNs: Six burning questions
News | Newsletters | Podcasts | Chats | Opinions | RSS Feeds | This Week In Print | IT Careers | Community | Reports | Downloads | Slideshows | New Data Center
Partner Sites:App Performance | On Demand Security | Networking Solution | SOA | Value of WDS
Last time, we discussed how the SMB office and the branch office both need IPT systems that offer affordability, usability, and manageability. Today, we’d like to highlight how the two environments are different.
First, because the branch office is part of a larger corporate network it needs to offer scalability that doesn’t adversely affect affordability, usability, and manageability. In traditional PBX systems, to add another office onto the corporate network typically required more trunk lines and changes to every onsite PBX located in the branches. An IPT system can overcome most of this complexity, especially when the system architecture supports distributed processing of call control and when it supports plug-and-play moves, adds, and changes.
Second, the branch office needs to offer remote management so the centralized IT staff back at headquarters can monitor and control the many branch office systems while the SMB office typically needs simple onsite configuration management capability.
Third, the remote branch office benefits from presence management across a larger enterprise. For example, a bank may offer mortgage services in every branch, but the mortgage experts may be physically sitting in another central location or they may travel between branches. Easily and quickly reaching the right person regardless of their physical location can be especially important to the branch operations.
In summary, while the small office and remote branch office have many similar needs, they also have needs that are different. So our advice: when selecting an IPT system for branch locations, large enterprise IT managers need to remember that the remote office is both a “small business” office AND part of a larger enterprise network.
Our thanks to Steve Hardy, Avaya’s Director for Global Product Marketing for his insights for this week’s topic.
If the IT manager is knowledgeable regarding Cisco technology, he would have 2 options. Option 1 - Consult...- Anonymous
Partner Content
The Foundry Enterprise Advantage
Foundry Networks, Inc. (NASDAQ: FDRY) is a leading provider of high-performance enterprise and service provider switching, routing, security and Web traffic management solutions. Foundry's customers include the world's premier ISPs, metro service providers, and enterprises.
For further information on Foundry Networks please click here.
Leveraging the Advantages
of a Multi-vendor Network Strategy
Today's enterprise network provides more than simply a technology infrastructure. It's an enabler for the enterprise, supporting mission critical applications, creating operational efficiencies and increasing productivity gains. Foundry Networks provides the ideal foundation for a multi-vendor network.
Click here to view whitepaper!
Comments (3)
D.O. is not what you think...By Anonymous on June 8, 2007, 4:21 pmI guess I'm curious why this product exists and what's wrong with IP Office that it needed to be created? Also, while this new Distributed Office sounds good...
Reply | Read entire comment
Also see ...By Adam Gaffin on June 6, 2007, 1:33 pmThe discussion on part 1.
Reply | Read entire comment
Nothing unique about Avaya's IP telephony systemBy Anonymous on June 6, 2007, 9:43 amNone of these are benefits of Avaya's system - just of IP telephony in general. Much cheaper and easier to deploy solutions have the same or better functionality. Re:...
Reply | Read entire comment
View all comments