Video Dial Plan Architecture
Technically, there is a lot of overlap between the configuration of voice and video
on the network.The following sections are written to explain some of the differences,
but keep in mind that topics discussed earlier within the chapter still need
to be considered when implementing a video dial plan.
When corporate videoconferencing was first introduced in the 1980s, people
saw it as a way to help connect people located in different cities so they could
communicate more effectively and efficiently, and at a greater savings in cost.
www.syngress.com
Figure 9.7 Configuration of a Group with Cisco CallManager
320 Chapter 9 • AVVID Dial Plans
With this in mind, there came the creation of standards that would allow these
remote locations to connect to each other.These first-generation solutions were
based upon the International Telecommunications Union (ITU) H.320 standards
defining Integrated Switched Digital Network (ISDN) connection-based videoconferencing.
Not long after this, second-generation solutions were created, bringing videoconferencing
to computer desktops.The main drawback to this more refined
technology was that it was still dependent upon ISDN and expensive CODEC
devices, so it wasn’t feasible to offer it to most users for normal business needs. In
the mid-1990s, the creation of the third-generation, LAN-based solutions,
became more prevalent in many organizations. Accessible desktop videoconferencing
applications multiplied, but until recently, these had remained proprietary,
and quite often, very expensive.
Because of compatibility issues between different device and software solutions,
widespread deployment up to this time has been severely limited.With
recent changes in world travel, however, you may begin to see videoconferencing
become more prevalent in the next few years; a trend that should, in turn, lead to
increased attempts at standardization as more companies try to corner the market.
You have to remember that when H.323 and H.324 standards were created,
they gave software and hardware vendors the ability to create videoconferencing
packages that were more manageable and affordable.This isn’t to say they solved
all problems are associated with videoconferencing (circuits are not always cheap,
and do not necessarily offer the uptime and dedicated bandwidth necessary to
support every organization).
The H.323 standard was able to define videoconferencing technologies and
enabled multivendor interoperability for the first time. Meanwhile, the H.324
standard was defined as a solution for videoconferencing using POTS lines.When
Cisco Systems started to deploy AVVID, they were able to enable end-to-end,
global desktop videoconferencing,VoIP, multilocation collaboration, and electronic
whiteboard applications.
As more and more applications based upon H.323 become available, and the
cost of digital video cameras continues to decline, there will be a more ubiquitous
implementation of desktop video conferencing. Also, as companies become
more and more economically savvy, you will see many accountants wanting to
leverage existing technologies and add one time costs (such as the digital camera)
to help with the bottom line and maintain cash flow.
Cisco introduced its Multimedia Conference Manager in February of 2001.
It is an H.323-compliant software that enables its users to create policy-based
www.syngress.com
AVVID Dial Plans • Chapter 9 321
management for H.323 applications, and is one of the first multifunctional, scalable
solutions available for a large market. It allows you to control and manage
voice and video connections with much more efficiency given your network
resources.