Cisco Unified Communications Media Display Design and Implementation Guide
Available Languages
Table Of Contents
Cisco Unified Communications Media Display Design and Implementation Guide
Unified Communications Media Display Solution—Overview
Solution Features and Benefits
Unified Communications Media Display Solution Architecture
Intelligent Retail Network and the SONA Framework
Integrated Network Services Layer
Intelligent Retail Network Store Architectures
LiteScape OnCast Deployment Models and the Intelligent Retail Network
Unified Communications Media Display Solution—Components and Services
Designing the Unified Communications Media Display Solution
Cisco Unified Communications Media Display Solution Components
Survivable Remote Site Telephony
Implementing and Configuring the Solution
Cisco Unified Communication Manager Server
LiteScape OnCast Directory Server Configuration
OnCast Directory Broadcast Server
Implementation Lessons Learned
Quality of Service Implementation
Survivable Remote Site Telephony Implementation
Sending Media using OnCast Web Client
Survivable Remote Site Telephony
Cisco Unified Communications Media Display Design and Implementation Guide
July 19, 2008
This guide describes how to implement the Cisco Unified Communications Media Display solution using the LiteScape OnCast product and Cisco Unified Communication technologies. It provides a proof of concept via interoperability testing using multiple retail reference architectures. This enables a retailer to expedite their implementation of media displays within their environment.
The Unified Communications Media Display target audience is sales engineers that have retail accounts interested in using an IP telephony environment as a method for digital media displays. It is assumed that administrators of the Unified Communications Media Display have experience with installation and acceptance of the products covered by this network design. In addition, it is assumed that the administrators understand the procedures required to upgrade and troubleshoot networks at a basic level.
Other users of this guide include the following groups:
•
Marketing personnel familiar with content creation and distribution
•
•
•
Unified Communications Media Display Solution—Overview
The Unified Communications Media Display (a feature of LiteScape OnCast) represents an innovative approach for delivering multimedia content to both customers and sales associates on the store floor. A variety of capabilities, such as two-way communications, dynamic content management, and interactive control, expand the possibilities compared to more expensive and restrictive kiosks. Combined with the flexibility of the Cisco Unified Communication environment, retailers expand the utility of their existing infrastructure.
The following are Unified Communications Media Display solution core components:
•
•
•
•
This solution was validated using Cisco Intelligent Retail Network architectures as the foundation representing an actual retailer.
Solution Description
Retailers are challenged to send consistent and clear messaging to both customers and employees in hundreds if not thousands of store locations. Current methods rely on printed signage/postings or a relay of information from store management to communicate price promotions, product information, corporate branding, store operational targets, and leadership updates. Each manager needs to read and then interpret the information before sharing with the customer/store staff, which can lead to messaging inconsistency from store-to-store locations. The method for sending this information is typically postal (received weekly), e-mail to store management (checked daily), and voicemail to store management (checked daily). This process cannot be provided real-time, because management is typically on the store floor, where they do not have computer access or notification of new voicemails.
This traditional method of communication is pushed down (one-way) from corporate, and does not provide the means for valuable collaboration (two-way) between customers, employees, store management, and corporate. The latency of communication impacts the quality of service and the time it takes for a customer service agent to respond to a customer request. These factors contribute to an unsatisfactory customer experience and potential "abandoned cart", where customers walk away from retail stores because of the lack of the personal touch or customer attention.
Using Cisco Unified Communications and LiteScape OnCast, retailers can broadcast advertising, branding, and other content to affordable color IP phones throughout each store. Content can be customized to different audiences, changed in real time, and can include text, text-to-speech, images, pre-recorded audio, live audio, configurable softkeys, and surveys. IP phones enable users to have pushbutton control for calling a help desk, playing back prerecorded messages, displaying related product information of interest, or filling out a survey.
By replacing a single kiosk with multiple always-on, interactive, communication-enabled display devices, retailers benefit both customers and employees. Customers can make better informed purchases and enjoy faster service. Using OnCast, store employees gain a much-needed connection to company headquarters; the executive team can affordably deliver personalized audio and visual content to individual departments or the entire company. Urgent product or emergency procedure information can instantly reach store employees when recalls and other public safety issues arise. As a powerful work flow management tool, the Unified Communications Media Display solution improves productivity.
Target Market
The target market of the Unified Communications Media Display is retailers interested in deploying IP telephony and/or digital media displays throughout their enterprise.
Solution Features and Benefits
The Unified Communications Media Display allows store communications personnel to send images, audio/text messages, and surveys to any phone or group of phones within one or many stores.
Benefits to the store employee include the following:
•
•
•
•
•
Benefits to the customer include the following:
•
•
•
Benefits to the retailer include the following:
•
•
•
Scope of the Solution
The tests that were performed by Cisco and LiteScape (as described in Testing) demonstrate a proof of concept that specific services of LiteScape OnCast will perform in a Cisco IP telephony environment. The LiteScape OnCast Server provides a wide variety of services. Cisco did not test every service that is available on the OnCast Server, but only services related to the digital media display needs of retailers.
The Unified Communications Media Display solution was deployed and tested within three retail network environments: small, medium, and large stores. These three store models were constructed using Cisco Intelligent Retail Network reference architectures. Each store model has varying degrees of redundancy and resiliency. The Unified Communications Media Display solution was tested at the Cisco lab in San Jose, CA.
The Unified Communications Media Display solution is a Cisco Validated Design, level 1 (CVD1), and as such, scale performance testing is not within the scope of this document. For more information, see the following URL: http://www.cisco.com/en/US/netsol/ns741/networking_solutions_program_home.html.
Unified Communications Media Display Solution Architecture
Intelligent Retail Network and the SONA Framework
The framework for the Unified Communications Media Display solution is based on the Cisco Service Oriented Network Architecture (SONA), as shown in Figure 1. Using a SONA framework, the Intelligent Retail Network (IRN) reference architectures serve as the foundation of the network systems layer. These network architectures exhibit best practices for retail networks and provide the robust foundation for the higher-level services and applications. For more information about IRN, see the following URL: http://www.cisco.com/web/strategy/retail/irn.html.
Figure 1 Unified Communications Media Display Solution Framework
Application Layer
Business and collaboration applications connect users and business processes to the infrastructure. The application layer of the framework includes the combined business and collaboration applications from Cisco and LiteScape.
LiteScape OnCast integrates with a Cisco Unified Communications IP telephony system to deliver multi-modal communications (data, voice, and visual content) to any connected IP device. OnCast enables timely content in many formats. Content can be quickly collected from a variety of sources, filtered for important details, and broadcast immediately or automatically to the people who need it.
The Cisco Unified Communications suite enables collaboration through XML-based applications.
The Cisco 7970 Series color IP phones have touchscreen-enabled displays. Users have pushbutton control for calling a help desk, playing back prerecorded messages, displaying related product information of interest, or filling out a survey.
Combined, retailers can broadcast advertising, branding, and other content to affordable IP phones throughout each store. Content can be customized to different audiences, changed in real time, and can include text, text-to-speech, images, pre-recorded audio, live audio, surveys, and RSS feeds.
Application services are the connection from the applications to the shared services of the infrastructure services layer. This is where filtering, caching, and protocol optimization interact with applications or application middleware services to optimize the performance from the network to the end user.
Integrated Network Services Layer
Process control is simplified by using common infrastructure services such as collaboration, security, and identity. These are key advantages that aid in operational reporting and security policy enforcements. Fewer services that are shared across more intelligent devices increases the operational efficiency of the whole system.
•
•
•
•
Note
Intelligent Retail Network Store Architectures
Small Store
The small store reference architecture (see Figure 2) is a powerful platform for running an enterprise retail business that requires simplicity and a compact form factor. This combination appeals to many different retail formats that can include the following:
•
•
•
•
•
This network architecture is widely used, and consolidates many services into fewer infrastructure components. The small store also supports a variety of retail business application models because an integrated Ethernet switch supports high-speed LAN services.
Figure 2 Small Store Network Design
Primary Design Requirements
Primary design requirements are as follows:
•
•
•
•
Advantages
Advantages are as follows:
•
•
•
•
Limitations
Limitations are as follows:
•
•
Medium Store
The medium retail store reference architecture (see Figure 3) is designed for enterprise retailers who require network resilience and increased levels of application availability over the small store architecture and its simple, single-threaded approach. As more mission-critical applications and services converge onto the IP infrastructure, network uptime and application availability are more important. The dual-router and dual-LAN switch design of the medium store supports these requirements. Each of the ISR routers can run Cisco IOS security services and other store communication services simultaneously. Each of the ISR routers is connected to a dedicated WAN connection. Hot-Standby Routing Protocol (HSRP) is used to ensure network resilience in the event that the network connection fails.
The access layer of the network offers enhanced levels of flexibility and more access ports compared to the small store. The distributed Cisco Catalyst switches can support a combination of larger physical buildings or a larger number of endpoints than the small store.
Figure 3 Medium Store Network Design
Primary Design Requirements
Primary design requirements are as follows:
•
•
•
The medium retail store reference architecture is designed for enterprise retailers that require network resilience and increased levels of application availability over the small store architecture and its single-threaded, simple approach. As more mission-critical applications and services converge onto the IP infrastructure, network uptime and application availability are more important. The dual-router and dual-LAN switch design of the medium store supports these requirements. Each of the ISR routers can run IOS security services and other store communication services simultaneously. Each of the ISR routers is connected to a dedicated WAN connection. Hot Standby Routing Protocol (HSRP) is used to ensure network resilience in the event that the network connection fails.
Advantages
Advantages are as follows:
•
•
•
•
Limitations
The limitation is as follows:
•
Large Store
The large retail store reference architecture (see Figure 4) takes some of the elements of Cisco campus network architecture recommendations and adapts them to a large retail store environment. Network traffic can be better segmented (logically and physically) to meet business requirements. The distribution layer of the large store architecture can greatly improve LAN performance while offering enhanced physical media connections. A larger number of endpoints can be added to the network to meet business requirements. This type of architecture is widely used by large-format retailers globally. Dual routers and distribution layer media flexibility greatly improve network serviceability because the network is highly available and scales to support the large retail store requirements. Routine maintenance and upgrades can be scheduled and performed more frequently or during normal business hours through this parallel path design.
Figure 4 Large Store Network Design
Primary Design Requirements
Primary design requirements are as follows:
•
•
•
•
•
Advantages
Advantages are as follows:
•
•
•
•
Limitations
The limitation is as follows:
•
OnCast Architecture Framework
OnCast provides unified access to traditionally disparate business applications, collaboration tools, and communications devices. OnCast directly ties together user IP phones with their desktops and allows them to move seamlessly between these disparate devices. With OnCast, the tasks that users perform on their IP phones directly complement and enhance tasks they perform on their PC, and vice versa. Figure 5 shows how OnCast brings together users and services.
Figure 5 OnCast Services
OnCast is composed of various components. The solution is based on a distributed, service-oriented architecture and is composed of a collection of Windows services and Simple Object Access Protocol (SOAP)-based web services.
The independence of the modules enables administrators to configure and distribute various components independently. In addition, the service based approach provides integration/customization and simplifies troubleshooting and pinpointing points of failure and bottlenecks.
Figure 6 shows the various OnCast components.
Figure 6 OnCast Components
The OnCast system connects IP-enabled phones with the following:
•
•
•
•
Figure 7 illustrates how the web administration interface is used to make configuration changes to the OnCast system. These configuration changes are recorded in an XML file named OnCastConfiguration.xml. You can edit this file directly, but LiteScape does not recommend doing so.
Figure 7 Architecture Connections
Figure 8 shows how Active Directory is linked to OnCast within the Unified Communication Media Display solution.
Figure 8 Directory Connection Architecture
LiteScape OnCast Deployment Models and the Intelligent Retail Network
Each of the following OnCast deployment models can be implemented as desired across the three Intelligent Retail Network architectures. The solution uses the centralized model for the small and medium stores, and the distributed model for the large store. A retailer that has a variety of store sizes or regional technical challenges can implement a hybrid approach with both central and distributed OnCast Servers. All three deployment models have been tested within this solution.
Figure 9 shows the LiteScape OnCast centralized deployment model.
Figure 9 LiteScape OnCast Centralized Deployment Model
The centralized model operates as follows:
•
•
•
Figure 10 shows the LiteScape OnCast distributed deployment model.
Figure 10 LiteScape OnCast—Distributed Deployment Scenario
The distributed model operates as follows:
•
•
•
Figure 11 shows the LiteScape OnCast hybrid deployment model.
Figure 11 LiteScape OnCast—Hybrid Deployment Scenario
The hybrid model operates as follows:
•
•
•
Note
Unified Communications Media Display Solution—Components and Services
Solution Components
The following components are required to implement the Unified Communications Media Display solution:
•
•
•
•
•
Hardware/Software
Table 1 lists the hardware/software products installed for the Unified Communications Media Display solution.
For planning purposes, the software requirements for OnCast Client and OnCast Composer are as follows:
•
•
•
Services and Functionality
Table 2 lists the services that were enabled to optimize OnCast within the Cisco network environment.
Limitations and Caveats
There are no known caveats or limitations.
Designing the Unified Communications Media Display Solution
The Unified Communications Media Display solution provides a proof of concept implementation of OnCast within a Cisco Unified Communication Manager and VoIP network. The small, medium, and large Intelligent Retail Network reference architectures provide a "real world" retail contextual backdrop for this solution. Each IRN store is centrally connected to a data center with traditional data center services such as DNS and NTP, as well as Cisco Unified Communication Manager and the OnCast Directory Server. This is a cost-effective implementation that leverages a highly available data center staffed with trained personnel and minimizes the number of additional servers required throughout the network. For very large locations where edge web caching is not available, it is advantageous to implement a distributed OnCast Directory Server. This synchronizes with the central server, reducing the amount of bandwidth needed because media is served up locally to those local devices once scheduled. This distributed model is used in the large store architecture in contrast to the centralized model used in the small and medium stores.
A number of servers and workstations were implemented as VMware Server virtual machines. This allowed greater flexibility within the lab environment and aligns with industry trending towards greater virtualization. Dedicated hardware and increased resources may be required for more consistent performance in larger implementations.
LiteScape
LiteScape OnCast is a feature-rich product with many capabilities beyond the subset of items that comprise the Unified Communications Media Display solution. Implementation of the solution requires a full installation of OnCast Directory Server and OnCast Composer. OnCast Composer is a desktop application that integrates with Microsoft Outlook.
OnCast Directory Server enables end users to invoke various communication features from the user interface on Cisco IP phones. The product provides integration with existing corporate and personal directories. Using customizable search criteria to find users and groups across the enterprise directory or within personal address books, OnCast also enables dialing, teleconferencing, and broadcasting to users and groups from the search results. OnCast enables retrieval of detailed information about directory members, as well as attributes such as alternative phone numbers, group members, presence, and availability indicators, and so on. The OnCast Directory web interface enables users to quickly create and send content-rich broadcasts across the enterprise to these targeted recipients.
OnCast Composer is used to create and send voice, text, and image broadcast messages from Outlook to VoIP phones. Advanced content such as surveys, RSS, or stock tickers can be sent.
LiteScape OnCast Directory Server has been evaluated under the Cisco Technology Developers Program (CTDP), where mid-scale and interoperability testing has been performed. Partner information and product status can be found on the Cisco website at the following URL: http://www.cisco-partners.info/showpart.asp?i=76.
OnCast Directory Server
OnCast Directory Server is installed with a complete set of components to integrate functions between a variety of services and devices. OnCast was configured to communicate with the Microsoft Active Directory server for retrieving usernames, authentication, and user phone extension information. This allows for centralized user administration and security.
OnCast Directory Server version 4.3 interoperates with Cisco Unified Communication Manager using Simple Network Management Protocol (SNMP), computer-telephony integration (CTI), and the web management interface. The solution uses a default installation of a single Cisco Unified Communication Manager 5.1.1 server with Service Package 5.1.2 applied.
Table 3 describes the various OnCast Directory components.
OnCast can access the following directory services:
•
•
•
•
•
•
The minimum hardware requirements for an OnCast Directory Server are as follows:
•
•
•
•
The software requirements are as follows:
•
•
•
•
The checklist in the OnCast Directory Administration Guide provides an easy way to record all the information you need for installation and customization/configuration. Management is performed using the web administration interfaces shown in Figure 12.
Note
Figure 12 LiteScape OnCast Web Administration Interface
OnCast Composer
OnCast Composer (see Figure 13) allows you to create and send a variety of message types to VoIP phones from your PC.
Figure 13 OnCast Composer
Message types include the following:
•
•
•
•
•
•
•
•
•
Any message type can be designated as an emergency message, which is played even if the recipient phone is in use.
A "workflow" consists of one or more keys (that is, "buttons") that appear with a broadcast message on recipient phone screens. Each workflow button consists of at least two elements: a name and an action. You can create custom keys for use in any type of broadcast, or use the modifiable, predefined default workflow templates.
Cisco Unified Communications Media Display Solution Components
The Unified Communications Media Display solution consists of LiteScape OnCast servers and Cisco Unified Communication Manager and IP phones. To facilitate the testing of this solution, additional Cisco components were used to provide a retail network infrastructure context. A simulated retailer was created, complete with a data center and three stores; small, medium, and large. This environment provided the services and enhancements described in the following sections that contributed to the performance, security, and management of the solution.
Intelligent Retail Network
The small, medium, and large stores were built to the specifications of the IP telephony designations of the Intelligent Retail Network reference architectures. Each store consists of access routing, switching, and security services. For additional information on the Intelligent Retail Network, see the following URL: http://www.cisco.com/web/strategy/retail/irn.html.
Unified Communications
The following components were used:
•
The Unified Communications implementation was a default installation of Cisco Unified Communication Manager 5.1. It is assumed that an actual retailer would implement a clustered implementation of Cisco Unified Communication Manager. For additional guidance on installing Unified Communications, see the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guide09186a0080792e5e.html.
•
The solution used G7.29a as the compression protocol for phone calls, and Skinny Call Control Protocol (SCCP) as the telephony control protocol. For the use of streaming media, the only currently supported phone compression codec is G7.11. This restriction is based on current OnCast Server processing capabilities. SCCP is required because the firmware image is smaller than the SIP firmware image. Current phones lack sufficient memory to support XML applications in the larger SIP image.
Dial Plan
The Unified Communication Media Display solution works with any existing dialing plan. The dialing plan is important because the Litescape application uses these dial numbers to identify unique endpoints when distributing media to specific departments.
Store standardization allows retailers to efficiently engineer, support, and maintain the enterprise network. Typically, retail stores are hierarchically organized by store number, department number, and extension number. A preferred dialing plan would align with existing enterprise information. Several large retailers were interviewed on how they would engineer a green field dialing plan. The Unified Communication Media Display solution utilized this logic in Cisco's labs for solution testing (see Figure 14):
Access number- store number- department number- extension number
Figure 14 Dial Plan Logic
This creates a simple 9-digit dialing plan as follows:
x-xxxx-xxx-x (for example, 7-1100-797-0 for access number, store #1100, department 797, and extension 0).
This logic provides globally unique phone numbers for each line and phone and avoids overlapping dial patterns within partitions. Using unique phone extension numbers simplifies the sending of media display information to each VoIP device without having to create additional user accounts or use an extensive naming system for each device.
For more examples of dial plan recommendations, see the Cisco Unified Communications SRND:
Multicasting
The Unified Communications Media Display solution uses several types of communication. Multicast is used to send audio messaging. It is assumed that certain retailers are not willing or able to deploy multicast across the enterprise. Therefore, the Unified Communications Media Display solution has been tested using several OnCast server deployment scenarios:
•
•
Note
Multicast is a complex topic with varying degrees of design concerns for individual retailers. This document provides configuration examples that were used to provide multicast functionality within the lab. For additional multicast design guidance, see the following URL: http://www.cisco.com/en/US/tech/tk828/tech_design_guides_list.html.
Quality of Service
The Unified Communication Media Display solution can potentially be a disruptive technology if not provisioned correctly because the application and media is bandwidth consumptive (see Performance). The use quality-of-service (QoS) protects the retailer's enterprise POS, voice, and media traffic from being disturbed by other forms of consumptive traffic.
QoS in this solution is implemented as Class-Based Weighted Fair Queueing (CBWFQ) with priority express forwarding for the voice traffic. Policy maps are used to classify traffic inbound on LAN interfaces and to queue traffic outbound on WAN interfaces.
Common performance issues today are often the result of misbehaving applications generating excessive traffic. By properly classifying and queuing network traffic, performance can be greatly improved. Through the use of QoS and multicast, retailers can remain extremely conservative on their WAN bandwidth provisioning.
The method of QoS used in the lab testing was based on the Cisco Enterprise Quality of Service reference design (see Table 4).
For more information on QoS, see the following URL: http://www.cisco.com/en/US/products/ps6558/prod_white_papers_list.html.
Survivable Remote Site Telephony
Survivable Remote Site Telephony (SRST) is configured in each store environment. SRST provides the central Cisco Unified Communication Manager functionality within the local store router in the event that the router loses communication with the Cisco Unified Communication Manager. Typically, this occurs during a WAN outage at the store. It is unlikely that the Cisco Unified Communication Manager itself will be unavailable because it is usually a clustered deployment.
The following two implementation scenarios of Unified Communications Media Display are specified:
•
•
Security
Security is an integral component of all retail networks requiring adherence to industry regulations such as the Sarbanes-Oxley Act of 2002 (SOX) and Payment Card Industry (PCI). Additional retail-focused security recommendations are located the PCI Solution for Retail Design and Implementation Guide at the following URL: http://www.cisco.com/web/strategy/retail/pci.html.
Segmentation for security purposes occurs in all locations. Within each store, retail traffic is segmented by type, such as point-of-sale, wireless, voice, and so on, and assigned an appropriate VLAN. The store ISR protects these segments with integrated Cisco IOS security features, such as packet filtering, stateful inspection firewall, NAT, IPS, and other services, applied as appropriate. Within the data center, segmentation and firewalling is implemented between data center services such as OnCast Directory, Cisco Unified Communication Manager, DNS, NTP, and so on. Management of network devices is secured using Access Control Server and Active Directory. This guide identifies the ports and protocols used by IP telephony with Cisco Unified Communication Manager, LiteScape OnCast Directory, and the Desktop Composer application. These services can then be accommodated in specific implementations as needed. Multicast addressing is filtered on the WAN connections to allow only the appropriate ranges used by this solution.
High Availability
Availability of telephony is a business necessity. To ensure high availability of the telephony system, the Cisco Unified Communication Manager installation used voice software in the store routers configured in SRST mode. In the event of a WAN failure, this allows the continued use of station-to-station dialing within the store as well as external calls when using local gateways to the PSTN.
LiteScape OnCast Directory operates on typical installations of Windows 2003 server; standard high availability techniques may be implemented and desired if using other available features within the product. For more details, see the OnCast Administration Guide at the following URL: https://www.sharemethods.net/nepal/servlet/category3?cid=75450&csubid=75488&c3id=75661&main_only=.
Design Considerations
Calculating Solution Traffic
Calculating the traffic characteristics of the Unified Communications Media Display solution includes factors such as media file size, number of phones, circuit size (including average utilization), and deployment method. For example, a store with a 256 kbps circuit (average utilization of 30%, maximum utilization of 80%) sending a 50 KB image to five phones would require 16 seconds to send images to the phone:
IMAGE ONLY5 phones x 50 KB image x 8 bits/Byte 2000 bits------------------------------------- = ---------------- = ~16 seconds to transfer images256 kbps x (80% max util- 30% avg util) 128 kbps AvailableIn another example, a store with a 512 kbps circuit (average utilization of 30%, maximum utilization of 80%) sending a 50 KB image to five phones would require 8 seconds to send images to the phone and continue to use an additional 92 kps for the duration of the audio file (see Performance):
IMAGE with AUDIO5 phones x 50 KB image x 8 bits/Byte 2000 bits------------------------------------- = ----------- = ~8 seconds to transfer images512 kbps x (80% max util- 30% avg util) 256 kbps AvailableFigure 15 Circuit Utilization
See the multicast and QoS sections for optimization services that mitigate the traffic impact of the solution.
Implementing and Configuring the Solution
The Unified Communications Media Display solution was implemented and validated as a proof of concept. Testing involved the validation of functionality across a variety of Cisco IP phones within a Cisco Unified Communication Manager 5.1.2 environment. Using the three store reference architectures, each store included three phone models (7970, 7960, and 7940s) in combination with an ISR router performing SRST functionality.
Two LiteScape OnCast Directory servers were deployed. One is located centrally in the data center location, sending media to the small and medium stores. The second server, located in the large store, synchronizes with the data center server, minimizing WAN utilization.
The goal of the testing was to articulate the functionality of the media display features of OnCast. It provides guidance on how to build various types of media messaging and distribute them to different phones in an enterprise.
Topology
The small, medium, and large Intelligent Retail Network reference architectures provide a "real world" retail contextual backdrop for this solution. Each IRN store was centrally connected to a data center with traditional data center services such as domain name service (DNS) and Network Time Protocol (NTP), as well as Cisco Unified Communication Manager and the OnCast Directory Server. The logical topology of the validation lab is represented in Figure 16. For specific places in the network details, see Appendix B—Network Diagrams.
Figure 16 Logical Topology
Testing Tools
Table 5 lists and describes the testing tools used.
Configuration Task Lists
Cisco Unified Communication Manager Server
Cisco Unified Communication Manager was installed using the current implementation guide available at the following URL: http://www.cisco.com/en/US/products/sw/voicesw/ps556/prod_installation_guide09186a0080792e5e.html.
The following steps outline the setup of Cisco Unified Communication Manager:
1.
2.
3.
4.
5.
6.
–
–
–
–
7.
8.
9.
10.
OnCast Directory Server
The LiteScape OnCast Directory server was installed using the current version of the administration guide provided with the installation software CD, and available via the LiteScape Partner Portal: https://www.sharemethods.net/nepal/servlet/category3?cid=75450&csubid=75488&c3id=75661&main_only=. Note that you need a Cisco Partner login to access this LiteScape ShareMethods products manual page.
The following steps outline the setup of the OnCast Server:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Figure 17 IIS Application Pools
15.
16.
17.
–
–
–
Microsoft SQL Server
The following steps outline the setup of the Microsoft SQL Server:
1.
2.
3.
4.
OnCast Composer System
The following steps outline the setup of OnCast Composer:
1.
2.
3.
4.
5.
Existing Resources
The following resources were existing:
•
•
LiteScape OnCast Directory Server Configuration
The following steps describe how LiteScape OnCast Directory Server was configured.
1.
Figure 18 OnCast Installer
2.
In the Select Installation Folder screen for each module, the default folder path was used and the "Everyone" radio button was selected, as shown in Figure 19.
Figure 19 Service Installation
3.
Figure 20 Security Credentials
4.
•
•
•
•
After entering the required information, the Test buttons were used to verify proper functionality.
Figure 21 PBX Information and Test Buttons
Each module installation followed these steps, and information from the pre-installation checklist was entered as appropriate. At the end of the module installation, the installation program requests a valid license file, after which the License Information screen appears, as shown in Figure 22.
Figure 22 License Screen
Troubleshooting Configuration
The OnCast Directory Server is a complex product with many configuration options. LiteScape professional services are required to properly install and integrate this solution.
The following file locations were helpful in troubleshooting issues on the OnCast Server:
1.
C:\Documents and Settings\All Users\Application Data\Litescape\OnCast
2.
C:\Documents and Settings\All Users\Application Data\Litescape\OnCast\Logs
3.
C:\Documents and Settings\All Users\Application Data\Litescape\OnCast\AppData
For OnCast Composer:
1.
C:\Documents and Settings\bmcgloth\Application Data\Litescape\OnCast
2.
C:\Documents and Settings\bmcgloth\Application Data\Litescape\OnCast\Logs
Ethereal was extremely helpful for monitoring traffic on the wire, and for validating ports and protocols used by the devices and services. An example is streaming audio being sent via unicast or multicast from the OnCast Directory Server.
IPerf was used to generate multicast, FTP, and web traffic. These flows helped identify proper queue sizing and access restrictions for QoS and multicast configurations.
Implementation Guidance
The following product components needed additional configuration after installation.
OnCast Composer
The installation of OnCast Composer required the application of an updated OIDS.xml file in support of the latest Cisco Unified Communications Manager version 5.1 SNMP MIB (this was not part of the default installer). The patch additionally required updating registry settings in support of the latest CM 5.1 locale settings. All updates are part of an updated OnCast Composer installer.
OnCast Directory Broadcast Server
The installation guide did not cover the following configuration changes that were needed:
•
•
•
•
•
Licensing Issue Encountered
To overcome a third-party (/nsoftware ™) embedded component licensing issue that was discovered, a temporary license was applied to the lab server installation. This issue could not been replicated with a new OCD 4.3.4 SP3 install.
SQL Server
When installing the MS-SQL optional calendaring schema for the web client interface, the automatic installer did not work properly, possibly because of security issues. If the retailer uses only MS-Outlook/Exchange calendaring for scheduling, this database feature is not required.
Implementation Lessons Learned
The following items are solution details that were documented during implementation:
•
To avoid losing this information, re-enter all the desired phone extensions before re-saving film strip set.
•
•
•
•
•
The workaround is to open Outlook and add an event with the .SET file attached.
•
The workaround is to manually edit the PBXDataCombo.xml file and set the file properties to read only.
Cisco Services Configuration
Multicast Implementation
Two types of multicast implementations were deployed: centralized and distributed.
Centralized Deployment Model of OnCast
Enabling multicast across the enterprise allows retailers to minimize the impact of bandwidth-consuming applications such as OnCast. The multicast service allows OnCast to send a multicast stream to the desired stores rather than unicasting an audio stream to each individual phone at each individual store.
For example, assume a retailer wants to deploy the Unified Communications Media Display solution within its stores. The retailer has 100 stores with 10 phones in each store. Without multicast enabled, 1000 audio streams (100x10) would be sent from the central OnCast server. With multicast enabled, the central OnCast server multicasts a single audio stream to each store router (100 audio streams total in this example) and allows the local store router to replicate the streams to the phones. This avoids taxing the valuable WAN bandwidth.
1.
ip multicast-routing Enables the router to route multicast traffic
2.
ip pim rp-address 192.168.1.10 192.168.1.10 is the loopback 0 interface of RCORE-1
3.
!interface Vlan45description VOICE SERVICESip pim sparse-dense-mode Enables interface to receive/send multicast traffic!On the WAN interfaces of the WAN-facing routers, a multicast filter was applied to protect the enterprise from rogue multicast applications consuming valuable WAN bandwidth.!ip access-list standard BlockMLocalpermit 239.192.0.0 0.0.0.255 Creates a standard access list that only permits the multicast addressing allowed for the OnCast Directory Server.interface Serial1/0.1 point-to-pointip pim sparse-dense-modeip multicast boundary BlockMLocal Filters unauthorized multicast traffic from traversing the WAN. This statement stops bi directional traffic and needs to be applied on both sides of the WAN connection.!Configurations are available in Appendix A—Configurations.
Distributed Deployment Model of OnCast
Some retailers are unable or unwilling to enable multicast across the enterprise because of management, security, or performance reasons. The Unified Communications Media Display solution supports a deployment model where the centralized OnCast directory server communicates via unicast with a distributed OnCast Directory server located within the store. This distributed local server of the store then performs the OnCast functions locally after synchronizing with the central server. This model avoids the use of multicast across the WAN and avoids the unnecessary replication of OnCast traffic across the valuable WAN bandwidth. However, the cost and management of the solution increases.
In this model, enterprise-wide multicast is not enabled; only the LAN of the local store router is enabled for multicast. The lab used the large store to test this deployment model.
1.
ip multicast-routing Enables the router to route multicast traffic
2.
ip pim rp-address 10.10.62.1 10.10.62.1 is the loopback 0 interface of RLRG-1
3.
!interface GigabitEthernet0/0.13description VOICEencapsulation dot1Q 13ip address 10.10.50.2 255.255.255.0ip helper-address 192.168.42.130ip pim sparse-dense-mode Enables GigabitEthernet0/0.13 interface to receive/send multicast trafficstandby 13 ip 10.10.50.1standby 13 priority 101standby 13 preempt!4.
Quality of Service Implementation
The Unified Communication Media Display solution can potentially be a disruptive technology if not provisioned correctly because the application and media is bandwidth consumptive (see Performance).
The use of QoS protects the retailer's enterprise POS, voice, and media traffic from being disturbed by other forms of consumptive traffic. The following configurations were used consistently across the small, medium and large stores:
ip access-list extended MISSION-CRITICAL-SERVERSremark ---POS Applications---permit ip 192.168.52.0 0.0.0.255 anypermit ip any 192.168.52.0 0.0.0.255ip access-list extended TRANSACTIONAL-DATA-APPSremark ---LiteScape Application---permit ip host 192.168.46.82 anypermit ip 239.192.0.0 0.0.0.255 anypermit ip host 239.255.255.250 anypermit ip any host 192.168.46.82permit ip any 239.192.0.0 0.0.0.255permit ip any host 239.255.255.250remark ---Remote Desktop---permit tcp any any eq 3389permit tcp any eq 3389 anyip access-list extended BULK-DATA-APPSremark ---File Transfer---permit tcp any eq ftp anypermit tcp any eq ftp-data anypermit tcp any any eq ftppermit tcp any any eq ftp-dataremark ---E-mail traffic---permit tcp any any eq smtppermit tcp any any eq pop3permit tcp any any eq 143permit tcp any eq smtp anypermit tcp any eq pop3 anypermit tcp any eq 143 anyremark ---other EDM app protocols---permit tcp any any range 3460 3466permit tcp any range 3460 3466 anyremark ---messaging services---permit tcp any any eq 2980permit tcp any eq 2980 anyremark ---Microsoft file services---permit tcp any any range 137 139permit tcp any range 137 139 anyip access-list extended NET-MGMT-APPSremark - Router user Authentication - Identifies TACACS Control trafficpermit tcp any any eq tacacspermit tcp any eq tacacs anyclass-map match-all VOICEmatch ip dscp ef ! IP Phones mark Voice to EFclass-map match-all INTERACTIVE-VIDEOmatch ip dscp af41 af42 ! Recommended markings for IP/VCclass-map match-any CALL-SIGNALINGmatch ip dscp cs3 ! Call-Signaling markingclass-map match-all ROUTINGmatch ip dscp cs6 ! Routers mark Routing traffic to CS6class-map match-all NET-MGMTmatch ip dscp cs2 ! Recommended marking for Network Managementclass-map match-all MISSION-CRITICAL-DATAmatch ip dscp 25 ! Interim marking for Mission-Critical Dataclass-map match-all TRANSACTIONAL-DATAmatch ip dscp af21 af22 ! Recommended markings for Transactional Dataclass-map match-all BULK-DATAmatch ip dscp af11 af12 ! Recommended markings for Bulk Dataclass-map match-all SCAVENGERmatch ip dscp cs1 ! Recommended marking for Scavenger trafficclass-map match-all BRANCH-MISSION-CRITICALmatch access-group name MISSION-CRITICAL-SERVERSclass-map match-any BRANCH-BULK-DATAmatch protocol tftp ! Identifies TFTP traffic - Retailersmatch protocol nfs ! Identifies NFS traffic - Retailersmatch access-group name BULK-DATA-APPS ! ACL to referenceclass-map match-any BRANCH-TRANSACTIONAL-DATA ! Must use "match-any"match protocol citrix ! Identifies Citrix trafficmatch protocol ldap ! Identifies LDAP trafficmatch protocol telnet ! Identifies Telnet trafficmatch protocol sqlnet ! Identifies Oracle SQL*NET trafficmatch protocol http url "*SalesReport*" ! Identifies "SalesReport" URLsmatch access-group name TRANSACTIONAL-DATA-APPS ! Other Appsclass-map match-any BRANCH-NET-MGMTmatch protocol snmp ! Identifies SNMP trafficmatch protocol syslog ! Identifies Syslog trafficmatch protocol dns ! Identifies DNS trafficmatch protocol icmp ! Identifies ICMP trafficmatch protocol ssh ! Identifies SSH trafficmatch access-group name NET-MGMT-APPS ! Other Network Management Appsclass-map match-any BRANCH-SCAVENGERmatch protocol napster ! Identifies Napster trafficmatch protocol gnutella ! Identifies Gnutella trafficmatch protocol fasttrack ! Identifies KaZaa (v1) trafficmatch protocol kazaa2 ! Identifies KaZaa (v2) traffic!policy-map BRANCH-LAN-EDGE-INclass BRANCH-MISSION-CRITICALset ip dscp 25class BRANCH-TRANSACTIONAL-DATAset ip dscp af21 ! Transactional Data apps are marked to DSCP AF21class BRANCH-NET-MGMTset ip dscp cs2 ! Network Management apps are marked to DSCP CS2class BRANCH-BULK-DATAset ip dscp af11 ! Bulk data apps are marked to AF11class BRANCH-SCAVENGERset ip dscp cs1 ! Scavenger apps are marked to DSCP CS1policy-map BRANCH-WAN-EDGEclass VOICEpriority percent 18 ! Voice gets 552 kbps of LLQclass INTERACTIVE-VIDEOpriority percent 15 ! 384 kbps IP/VC needs 460 kbps of LLQclass CALL-SIGNALINGbandwidth percent 5 ! Minimal BW guarantee for Call-Signalingclass ROUTINGbandwidth percent 3 ! Routing class gets 3% explicit BW guaranteeclass NET-MGMTbandwidth percent 2 ! Net-Mgmt class gets 2% explicit BW guaranteeclass MISSION-CRITICAL-DATAbandwidth percent 15 ! Mission-Critical class gets min 15% BW guaranteerandom-detect ! Enables WRED on Mission-Critical Data classclass TRANSACTIONAL-DATAbandwidth percent 12 ! Transactional-Data class gets min 12% BW guaranteerandom-detect dscp-based ! Enables DSCP-WRED on Transactional-Data classclass BULK-DATAbandwidth percent 4 ! Bulk Data class gets 4% BW guaranteerandom-detect dscp-based ! Enables DSCP-WRED on Bulk-Data classclass SCAVENGERbandwidth percent 1 ! Scavenger class is throttledclass class-defaultbandwidth percent 25 ! Default class gets min 25% BW guaranteerandom-detect ! Enables WRED on the default classpolicy-map BRANCH-LAN-EDGE-OUTclass class-defaultinterface Serial0/0/1:0description T1 to SERVICE PROVIDERframe-relay traffic-shapingmax-reserved-bandwidth 100 ! overrides the default 75% BW limitinterface Serial0/0/1:0.1 point-to-pointdescription PVC CONNECTION TO DATACENTERframe-relay interface-dlci 201class fr_qosmap-class frame-relay fr_qosframe-relay fragment 160frame-relay traffic-rate 1536000 1536000frame-relay adaptive-shaping becnservice-policy output BRANCH-WAN-EDGEinterface VlanXXdescription POSno service-policy input set_priorityservice-policy output BRANCH-LAN-EDGE-OUTservice-policy input BRANCH-LAN-EDGE-INSurvivable Remote Site Telephony Implementation
In the event that the store WAN goes down or if the store router loses connection to the central Cisco Unified Communication Manager, SRST allows the store router to perform the Cisco Unified Communication Manager functions during its absence. This not only allows the store voice services to remain functional but within the context of the Unified Communications Media Display, it allows the OnCast Directory Services to remain functional. This feature is available only in the distributed model of OnCast deployment; for example, where the large store architecture has a server deployed onsite.
Security
Table 6 lists the ports and protocols used by the Unified Communications Media Display Solution.
Multicast
Multicast routing can be a potential security/performance risk. The nature of multicast is dynamic and pervasive throughout the enterprise. Cisco recommends that filters be placed on the WAN routers, both central at the data center and local to the store edge, that specifically allow approved address ranges. The Oncast Directory server uses multicast addressing with in the range of 239.192.0.0 /24.
Testing
Test Plan
Testing included creating several types of media and sending them to various phones using the several methods available. Some methods of sending content were not able to support all of the desired tests. The sending methods used are as follows:
•
•
•
•
•
The following tests were performed (test results are listed in Figure 30):
1.
Store alert: "POS systems have gone down and the issue will be resolved in 15 minutes"
2.
3.
4.
5.
6.
7.
How was our service? 1. Great, 2. Good, and 3. Needs improvement
Receive survey results from e-mail, and send to the summary to the Exchange server group account media—display@cisco-irn.com
8.
9.
Testing Steps
Many of the tests used OnCast Composer to create the media that was sent to the phones.
The following steps describe one of the tests where an image and audio track were sent to a group of phones using the Film Strip feature.
Sending Media Using Composer
1.
Figure 23 Selecting Broadcast Option
2.
Figure 24 Creating Image and Audio Set
3.
4.
Each of the entered phone numbers is translated into the appropriate device IP address based on information retrieved from the Cisco Unified Communication Manager server using SNMP.
Figure 25 Media Transmission
5.
Figure 26 Film Strip
6.
Figure 27 Destination Device Address Entry
7.
Figure 28 Active Strip Sets
8.
Sending Media using OnCast Web Client
Much of the same functionality available in OnCast Composer is available by using the OnCast Directory Server web client interface. An example of this interface is shown in Figure 29.Figure 29 OnCast Directory Server Web Interface
Test Results
Figure 30 summarizes the results achieved from the tests performed as outlined in Testing Steps.
Figure 30 OnCast Testing Results
Performance
The following data characterizes the traffic generated by the media sent to a single phone during testing. Figure 31 shows the utilization as captured on the network. This transmission uses G7.11. Future codec support will include G7.29a.
•
–
–
–
–
–
•
–
–
–
–
–
–
–
Figure 31 Traffic Utilization for Single Phone—Image and Audio Clip Stream
Testing Lessons Learned
The following items were documented during testing:
•
–
–
–
•
–
•
–
•
–
All sets sent using Film Strip were set to 30 seconds each and to loop for two minutes.
Summary and Recommendations
The Cisco Unified Communications Media Display solution successfully delivers a variety of capabilities, including the delivery of multimedia content (kiosk replacement), corporate messaging, and two-way communications.
The Cisco VoIP phones perform well as a substitute to a media kiosk for customer-facing deployments. The Cisco 7970 phone is the recommended phone to display images and messaging, because the color display provides a higher fidelity for photos and images. The monochrome 7960 and 7940 phone displays are not as clear when showing color source images (see Figure 32). Media content should be carefully reviewed before delivery to these phones.
Figure 32 Comparison of Phone Images
Surveys and voice communication enable immediate responses from end users. Survey results are easily collected through e-mail messages delivered from each phone.
A deployment model leveraging multicast and QoS are critical to the successful implementation of streaming media across a retail network. Because the media stream uses the G.711 codec, a substantial amount of bandwidth is consumed (over 100 kbps). If multicast is not used, several phones at a store could easily overwhelm the WAN link. For stores with a large number of phones, there is a significant value in deploying a distributed media server or some form of caching engine to reduce impact to the store WAN link.
The LiteScape OnCast application used in the Unified Communications Media Display solution demonstrates the additional value that can be achieved with an IP phone deployment in contrast to traditional PBX systems.
Appendix A—Configurations
QoS
Data Center
WAN Routers
ip access-list extended MISSION-CRITICAL-SERVERSremark ---POS Applications---permit ip 192.168.52.0 0.0.0.255 anypermit ip any 192.168.52.0 0.0.0.255ip access-list extended TRANSACTIONAL-DATA-APPSremark ---LiteScape Application---permit ip host 192.168.46.82 anypermit ip 239.192.0.0 0.0.0.255 anypermit ip host 239.255.255.250 anypermit ip any host 192.168.46.82permit ip any 239.192.0.0 0.0.0.255permit ip any host 239.255.255.250remark ---Remote Desktop---permit tcp any any eq 3389permit tcp any eq 3389 anyip access-list extended BULK-DATA-APPSremark ---File Transfer---permit tcp any eq ftp anypermit tcp any eq ftp-data anypermit tcp any any eq ftppermit tcp any any eq ftp-dataremark ---E-mail traffic---permit tcp any any eq smtppermit tcp any any eq pop3permit tcp any any eq 143permit tcp any eq smtp anypermit tcp any eq pop3 anypermit tcp any eq 143 anyremark ---other EDM app protocols---permit tcp any any range 3460 3466permit tcp any range 3460 3466 anyremark ---messaging services---permit tcp any any eq 2980permit tcp any eq 2980 anyremark ---Microsoft file services---permit tcp any any range 137 139permit tcp any range 137 139 anyip access-list extended NET-MGMT-APPSremark - Router user Authentication - Identifies TACACS Control trafficpermit tcp any any eq tacacspermit tcp any eq tacacs anyclass-map match-any DATACENTER-MISSION-CRITICALmatch access-group name MISSION-CRITICAL-SERVERSclass-map match-any DATACENTER-BULK-DATAmatch protocol tftp ! Identifies TFTP traffic - Retailersmatch protocol nfs ! Identifies NFS traffic - Retailersmatch access-group name BULK-DATA-APPS ! ACL to referenceclass-map match-any DATACENTER-TRANSACTIONAL-DATA ! Must use "match-any"match protocol citrix ! Identifies Citrix trafficmatch protocol ldap ! Identifies LDAP trafficmatch protocol telnet ! Identifies Telnet trafficmatch protocol sqlnet ! Identifies Oracle SQL*NET trafficmatch protocol http url "*SalesReport*" ! Identifies "SalesReport" URLsmatch access-group name TRANSACTIONAL-DATA-APPS ! Other Appsclass-map match-any DATACENTER-NET-MGMTmatch protocol snmp ! Identifies SNMP trafficmatch protocol syslog ! Identifies Syslog trafficmatch protocol dns ! Identifies DNS trafficmatch protocol icmp ! Identifies ICMP trafficmatch protocol ssh ! Identifies SSH trafficmatch access-group name NET-MGMT-APPS ! Other Network Management Appsclass-map match-any DATACENTER-SCAVENGERmatch protocol napster ! Identifies Napster trafficmatch protocol gnutella ! Identifies Gnutella trafficmatch protocol fasttrack ! Identifies KaZaa (v1) trafficmatch protocol kazaa2 ! Identifies KaZaa (v2) traffic!policy-map DATACENTER-LAN-EDGE-INclass DATACENTER-MISSION-CRITICALset ip dscp 25class DATACENTER-TRANSACTIONAL-DATAset ip dscp af21 ! Transactional Data apps are marked to DSCP AF21class DATACENTER-NET-MGMTset ip dscp cs2 ! Network Management apps are marked to DSCP CS2class DATACENTER-BULK-DATAset ip dscp af11 ! Bulk data apps are marked to AF11class DATACENTER-SCAVENGERset ip dscp cs1 ! Scavenger apps are marked to DSCP CS1class-map match-all VOICEmatch ip dscp ef ! IP Phones mark Voice to EFclass-map match-all INTERACTIVE-VIDEOmatch ip dscp af41 af42 ! Recommended markings for IP/VCclass-map match-all STREAMING-VIDEOmatch ip dscp cs4 ! Recommended marking for Streaming-Videoclass-map match-any CALL-SIGNALINGmatch ip dscp cs3 ! Call-Signaling markingclass-map match-all ROUTINGmatch ip dscp cs6 ! Routers mark Routing traffic to CS6class-map match-all NET-MGMTmatch ip dscp cs2 ! Recommended marking for Network Managementclass-map match-all MISSION-CRITICAL-DATAmatch ip dscp 25 ! Interim marking for Mission-Critical Dataclass-map match-all TRANSACTIONAL-DATAmatch ip dscp af21 af22 ! Recommended markings for Transactional Dataclass-map match-all BULK-DATAmatch ip dscp af11 af12 ! Recommended markings for Bulk Dataclass-map match-all SCAVENGERmatch ip dscp cs1 ! Recommended marking for Scavenger trafficpolicy-map WAN-EDGEclass VOICEpriority percent 18 ! Voice gets 552 kbps of LLQclass INTERACTIVE-VIDEOpriority percent 15 ! 384 kbps IP/VC needs 460 kbps of LLQclass CALL-SIGNALINGbandwidth percent 5 ! BW guarantee for Call-Signalingclass ROUTINGbandwidth percent 3 ! Routing class gets explicit BW guaranteeclass NET-MGMTbandwidth percent 2 ! Net-Mgmt class gets explicit BW guaranteeclass MISSION-CRITICAL-DATAbandwidth percent 10 ! Mission-Critical class gets 10% BW guaranteerandom-detect ! Enables WRED for Mission-Critical Data classclass TRANSACTIONAL-DATAbandwidth percent 7 ! Transactional-Data class gets 7% BW guaranteerandom-detect dscp-based ! Enables DSCP-WRED for Transactional-Data classclass BULK-DATAbandwidth percent 4 ! Bulk Data remains at 4% BW guaranteerandom-detect dscp-based ! Enables DSCP-WRED for Bulk-Data classclass STREAMING-VIDEObandwidth percent 10 ! Streaming-Video class gets 10% BW guaranteeclass SCAVENGERbandwidth percent 1 ! Scavenger class is throttledclass class-defaultbandwidth percent 25 ! Class-Default gets 25% min BW guaranteerandom-detect ! Enables WRED on class-defaultpolicy-map DATACENTER-LAN-EDGE-OUTclass class-defaultset cos dscpinterface GigabitEthernet0/0description ALL interfacesservice-policy input DATACENTER-LAN-EDGE-IN ! Marks Data on ingressinterface GigabitEthernet0/1description ALL interfacesservice-policy input DATACENTER-LAN-EDGE-IN ! Marks Data on ingressinterface serial 1/0description T3 to SERVICE PROVIDERframe-relay traffic-shapingmax-reserved-bandwidth 100 ! overrides the default 75% BW limitinterface Serial1/0.3 point-to-pointdescription PVC to STOREframe-relay interface-dlci 1003class fr_qosmap-class frame-relay fr_qosframe-relay fragment 160frame-relay traffic-rate 1536000 1536000frame-relay adaptive-shaping becnservice-policy output WAN-EDGEAll Stores
ip access-list extended MISSION-CRITICAL-SERVERSremark ---POS Applications---permit ip 192.168.52.0 0.0.0.255 anypermit ip any 192.168.52.0 0.0.0.255ip access-list extended TRANSACTIONAL-DATA-APPSremark ---LiteScape Application---permit ip host 192.168.46.82 anypermit ip 239.192.0.0 0.0.0.255 anypermit ip host 239.255.255.250 anypermit ip any host 192.168.46.82permit ip any 239.192.0.0 0.0.0.255permit ip any host 239.255.255.250remark ---Remote Desktop---permit tcp any any eq 3389permit tcp any eq 3389 anyip access-list extended BULK-DATA-APPSremark ---File Transfer---permit tcp any eq ftp anypermit tcp any eq ftp-data anypermit tcp any any eq ftppermit tcp any any eq ftp-dataremark ---E-mail traffic---permit tcp any any eq smtppermit tcp any any eq pop3permit tcp any any eq 143permit tcp any eq smtp anypermit tcp any eq pop3 anypermit tcp any eq 143 anyremark ---other EDM app protocols---permit tcp any any range 3460 3466permit tcp any range 3460 3466 anyremark ---messaging services---permit tcp any any eq 2980permit tcp any eq 2980 anyremark ---Microsoft file services---permit tcp any any range 137 139permit tcp any range 137 139 anyip access-list extended NET-MGMT-APPSremark - Router user Authentication - Identifies TACACS Control trafficpermit tcp any any eq tacacspermit tcp any eq tacacs anyclass-map match-all VOICEmatch ip dscp ef ! IP Phones mark Voice to EFclass-map match-all INTERACTIVE-VIDEOmatch ip dscp af41 af42 ! Recommended markings for IP/VCclass-map match-any CALL-SIGNALINGmatch ip dscp cs3 ! Call-Signaling markingclass-map match-all ROUTINGmatch ip dscp cs6 ! Routers mark Routing traffic to CS6class-map match-all NET-MGMTmatch ip dscp cs2 ! Recommended marking for Network Managementclass-map match-all MISSION-CRITICAL-DATAmatch ip dscp 25 ! Interim marking for Mission-Critical Dataclass-map match-all TRANSACTIONAL-DATAmatch ip dscp af21 af22 ! Recommended markings for Transactional Dataclass-map match-all BULK-DATAmatch ip dscp af11 af12 ! Recommended markings for Bulk Dataclass-map match-all SCAVENGERmatch ip dscp cs1 ! Recommended marking for Scavenger trafficclass-map match-all BRANCH-MISSION-CRITICALmatch access-group name MISSION-CRITICAL-SERVERSclass-map match-any BRANCH-BULK-DATAmatch protocol tftp ! Identifies TFTP traffic - Retailersmatch protocol nfs ! Identifies NFS traffic - Retailersmatch access-group name BULK-DATA-APPS ! ACL to referenceclass-map match-any BRANCH-TRANSACTIONAL-DATA! Must use "match-any"match protocol citrix ! Identifies Citrix trafficmatch protocol ldap ! Identifies LDAP trafficmatch protocol telnet ! Identifies Telnet trafficmatch protocol sqlnet ! Identifies Oracle SQL*NET trafficmatch protocol http url "*SalesReport*" ! Identifies "SalesReport" URLsmatch access-group name TRANSACTIONAL-DATA-APPS ! Other Appsclass-map match-any BRANCH-NET-MGMTmatch protocol snmp ! Identifies SNMP trafficmatch protocol syslog ! Identifies Syslog trafficmatch protocol dns ! Identifies DNS trafficmatch protocol icmp ! Identifies ICMP trafficmatch protocol ssh ! Identifies SSH trafficmatch access-group name NET-MGMT-APPS ! Other Network Management Appsclass-map match-any BRANCH-SCAVENGERmatch protocol napster ! Identifies Napster trafficmatch protocol gnutella ! Identifies Gnutella trafficmatch protocol fasttrack ! Identifies KaZaa (v1) trafficmatch protocol kazaa2 ! Identifies KaZaa (v2) traffic!policy-map BRANCH-LAN-EDGE-INclass BRANCH-MISSION-CRITICALset ip dscp 25class BRANCH-TRANSACTIONAL-DATAset ip dscp af21 ! Transactional Data apps are marked to DSCP AF21class BRANCH-NET-MGMTset ip dscp cs2 ! Network Management apps are marked to DSCP CS2class BRANCH-BULK-DATAset ip dscp af11 ! Bulk data apps are marked to AF11class BRANCH-SCAVENGERset ip dscp cs1 ! Scavenger apps are marked to DSCP CS1policy-map BRANCH-WAN-EDGEclass VOICEpriority percent 18 ! Voice gets 552 kbps of LLQclass INTERACTIVE-VIDEOpriority percent 15 ! 384 kbps IP/VC needs 460 kbps of LLQclass CALL-SIGNALINGbandwidth percent 5 ! Minimal BW guarantee for Call-Signalingclass ROUTINGbandwidth percent 3 ! Routing class gets 3% explicit BW guaranteeclass NET-MGMTbandwidth percent 2 ! Net-Mgmt class gets 2% explicit BW guaranteeclass MISSION-CRITICAL-DATAbandwidth percent 15 ! Mission-Critical class gets min 15% BW guaranteerandom-detect ! Enables WRED on Mission-Critical Data classclass TRANSACTIONAL-DATAbandwidth percent 12 ! Transactional-Data class gets min 12% BW guaranteerandom-detect dscp-based ! Enables DSCP-WRED on Transactional-Data classclass BULK-DATAbandwidth percent 4 ! Bulk Data class gets 4% BW guaranteerandom-detect dscp-based ! Enables DSCP-WRED on Bulk-Data classclass SCAVENGERbandwidth percent 1 ! Scavenger class is throttledclass class-defaultbandwidth percent 25 ! Default class gets min 25% BW guaranteerandom-detect ! Enables WRED on the default classpolicy-map BRANCH-LAN-EDGE-OUTclass class-defaultmap-class frame-relay fr_qosframe-relay fragment 160frame-relay traffic-rate 1536000 1536000frame-relay adaptive-shaping becnservice-policy output BRANCH-WAN-EDGEinterface Serial0/0/1:0description T1 to SERVICE PROVIDERframe-relay traffic-shapingmax-reserved-bandwidth 100 ! overrides the default 75% BW limitinterface Serial0/0/1:0.1 point-to-pointdescription PVC CONNECTION TO DATACENTERframe-relay interface-dlci 201class fr_qosinterface VlanXXdescription POSno service-policy input set_priorityservice-policy output BRANCH-LAN-EDGE-OUTservice-policy input BRANCH-LAN-EDGE-INSurvivable Remote Site Telephony
RLRG-1
!voice-card 0dspfarmdsp services dspfarm!applicationglobalservice alternate default!call fallback active!ccm-manager fallback-mgcpccm-manager mgcp!mgcpmgcp call-agent 192.168.45.181 service-type mgcp version 0.1mgcp dtmf-relay voip codec all mode ciscomgcp rtp unreachable timeout 1000 action notifymgcp package-capability rtp-packagemgcp package-capability sst-packagemgcp sdp simplemgcp bind control source-interface loopback 0mgcp bind media source-interface loopback 0!mgcp profile default!dial-peer cor customname nr!dial-peer cor list nrmember nr!dial-peer voice 1 voip!dial-peer voice 2 pots!dial-peer voice 18 potsservice mgcpappdirect-inward-dialport 0/3/0!call-manager-fallbackmax-conferences 2 gain -6transfer-system full-consultip source-address 10.10.50.2 port 2000 strict-matchmax-ephones 10max-dn 20cor incoming nr 1 8001 - 8999!RLRG-2
!voice-card 0dspfarmdsp services dspfarm!applicationglobalservice alternate default!call fallback active!ccm-manager fallback-mgcpccm-manager mgcp!mgcpmgcp call-agent 192.168.45.181 service-type mgcp version 0.1mgcp dtmf-relay voip codec all mode ciscomgcp rtp unreachable timeout 1000 action notifymgcp package-capability rtp-packagemgcp package-capability sst-packagemgcp sdp simplemgcp bind control source-interface loopback 0mgcp bind media source-interface loopback 0!mgcp profile default!dial-peer cor customname nr!dial-peer cor list nrmember nr!dial-peer voice 1 voip!dial-peer voice 2 pots!dial-peer voice 18 potsservice mgcpappdirect-inward-dialport 0/3/0!call-manager-fallbackmax-conferences 2 gain -6transfer-system full-consultip source-address 10.10.50.2 port 2000 strict-matchmax-ephones 10max-dn 20cor incoming nr 1 8001 - 8999!Multicast
Data Center
RCORE-1
ip multicast-routingip pim bidir-enable!interface Loopback0ip pim sparse-dense-mode!interface Vlan42descriptionip pim sparse-dense-mode!interface Vlan45description Voice Servicesip pim sparse-dense-mode!interface Vlan46descriptionip pim sparse-dense-mode!interface Vlan101descriptionip pim sparse-dense-mode!interface Vlan104descriptionip pim sparse-dense-modeip pim bidir-enableip pim rp-address 192.168.1.10RCORE-2
ip multicast-routing!interface Vlan102descriptionip pim sparse-dense-mode!interface Vlan103descriptionip pim sparse-dense-mode!ip pim rp-address 192.168.1.10No active Sources on Core 2WAN Routers
RWAN-1
ip multicast-routinginterface GigabitEthernet0/0ip pim sparse-dense-mode!interface GigabitEthernet0/1ip pim sparse-dense-modeinterface Serial1/0.1 point-to-pointip pim sparse-dense-modeip multicast boundary BlockMLocal!!interface Serial1/0.2 point-to-pointip pim sparse-dense-modeip multicast boundary BlockMLocal!interface Serial1/0.3 point-to-point<none>ip pim rp-address 192.168.1.10ip access-list standard BlockMLocalpermit 239.192.0.0 0.0.0.255RWAN-2
ip multicast-routinginterface GigabitEthernet0/0ip pim sparse-dense-mode!interface GigabitEthernet0/1ip pim sparse-dense-modeinterface Serial1/0.1 point-to-pointip pim sparse-dense-modeip multicast boundary BlockMLocal!!interface Serial1/0.2 point-to-pointip pim sparse-dense-modeip multicast boundary BlockMLocal!interface Serial1/0.3 point-to-point<none>ip pim rp-address 192.168.1.10ip access-list standard BlockMLocalpermit 239.192.0.0 0.0.0.255Small Store
RSMALL-1
ip multicast-routing!interface Serial0/0/0:0.1 point-to-pointdescription RSMALL-1 CONNECTION RSP-1ip pim sparse-dense-modeip multicast boundary BlockMLocal!interface Serial0/0/1:0.1 point-to-pointdescription RSMALL-1 CONNECTION RSP-2ip pim sparse-dense-modeip multicast boundary BlockMLocal!interface Vlan11description POSip pim sparse-dense-mode!interface Vlan13description VOICEip pim sparse-dense-mode!ip pim rp-address 192.168.1.10ip access-list standard BlockMLocalpermit 239.192.0.0 0.0.0.255Medium Store
RMED-1
ip multicast-routing!interface GigabitEthernet0/0.11description POSip pim sparse-dense-mode!interface GigabitEthernet0/0.13description VOICEip pim sparse-dense-mode!interface GigabitEthernet0/0.102description ROUTER LINK TO RMED2 VIA SMED2ip pim sparse-dense-mode!interface GigabitEthernet0/1.101description ROUTER LINK TO RMED-2ip pim sparse-dense-mode!interface Serial0/0/0:0.1 point-to-pointdescription CONNECTION TO RWAN-1ip pim sparse-dense-modeip multicast boundary BlockMLocal!interface Vlan13description VOICEip pim sparse-dense-mode!ip pim rp-address 192.168.1.10ip access-list standard BlockMLocalpermit 239.192.0.0 0.0.0.255RMED-2
ip multicast-routing!interface GigabitEthernet0/0.11description POSip pim sparse-dense-mode!interface GigabitEthernet0/0.13description VOICEip pim sparse-dense-mode!interface GigabitEthernet0/0.102description ROUTER LINK TO RMED2 VIA SMED2ip pim sparse-dense-mode!interface GigabitEthernet0/1.101description ROUTER LINK TO RMED1 VIA SMED2ip pim sparse-dense-mode!interface Serial0/0/0:0.1 point-to-pointdescription CONNECTION TO RWAN-1ip pim sparse-dense-modeip multicast boundary BlockMLocal!interface Vlan13description VOICEip pim sparse-dense-mode!ip pim rp-address 192.168.1.10ip access-list standard BlockMLocalpermit 239.192.0.0 0.0.0.255Large Store
RLRG-1
ip multicast-routing!interface Loopback0description RP for Multicastip pim sparse-dense-mode!interface GigabitEthernet0/0.11description POSip pim sparse-dense-mode!interface GigabitEthernet0/0.12description DATAip pim sparse-dense-mode!interface GigabitEthernet0/0.13description VOICEip pim sparse-dense-mode!!interface GigabitEthernet0/0.102description ROUTER LINK TO RLRG-2 VIA SLRG-2ip pim sparse-dense-mode!interface GigabitEthernet0/1.101description ROUTER LINK TO RLRG-2 VIA SLRG-2ip pim sparse-dense-mode!RLRG-2
ip multicast-routing!interface GigabitEthernet0/1.11description POSip pim sparse-dense-mode!interface GigabitEthernet0/1.12description DATAip pim sparse-dense-mode!interface GigabitEthernet0/1.13description VOICEip pim sparse-dense-mode!interface GigabitEthernet0/0.102description ROUTER LINK TO RLRG-1 VIA SLRG-1ip pim sparse-dense-mode!interface GigabitEthernet0/1.101description ROUTER LINK TO RLRG-1 VIA SLRG-1ip pim sparse-dense-mode!Appendix B—Network Diagrams
Large Store
Figure 33 Large Store Topology
Medium Store
Figure 34 Medium Store Topology
Small Store
Figure 35 Small Store Topology
Data Center
Figure 36 Data Center Topology
Service Provider
Figure 37 Service Provider Topology
Cisco Validated Design
The Cisco Validated Design Program consists of systems and solutions designed, tested, and documented to facilitate faster, more reliable, and more predictable customer deployments. For more information visit www.cisco.com/go/validateddesigns.
ALL DESIGNS, SPECIFICATIONS, STATEMENTS, INFORMATION, AND RECOMMENDATIONS (COLLECTIVELY, "DESIGNS") IN THIS MANUAL ARE PRESENTED "AS IS," WITH ALL FAULTS. CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THE DESIGNS, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
THE DESIGNS ARE SUBJECT TO CHANGE WITHOUT NOTICE. USERS ARE SOLELY RESPONSIBLE FOR THEIR APPLICATION OF THE DESIGNS. THE DESIGNS DO NOT CONSTITUTE THE TECHNICAL OR OTHER PROFESSIONAL ADVICE OF CISCO, ITS SUPPLIERS OR PARTNERS. USERS SHOULD CONSULT THEIR OWN TECHNICAL ADVISORS BEFORE IMPLEMENTING THE DESIGNS. RESULTS MAY VARY DEPENDING ON FACTORS NOT TESTED BY CISCO.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0807R)
Feedback