Table Of Contents
Introducing Cisco IPICS and the PMC Application
Overview of Cisco IPICS
Introduction
Cisco IPICS System Components
Cisco IPICS User Roles
About the PMC Application
Browser Support
Work Flow Activities
PMC Application Usage Caveats
Architecture/Deployment
System Requirements for the PMC Application
Hardware Requirements
Software Requirements
System Interactions
Server Interactions
User Interactions
Introducing Cisco IPICS and the PMC Application
This chapter provides an overview of the components that are used in the Cisco IPICS solution. It also documents system requirements for the PMC application and important information that you need to know about server and user interactions.
This chapter includes the following topics:
•
Overview of Cisco IPICS
•
System Requirements for the PMC Application
•
System Interactions
Overview of Cisco IPICS
This section provides an overview of Cisco IPICS and the PMC application; it includes the following topics:
•
Introduction
•
Cisco IPICS System Components
•
About the PMC Application
•
Architecture/Deployment
Introduction
The Cisco IPICS solution provides a cost-effective and highly-efficient IP standards-based solution to enable voice interoperability among disparate systems. By interconnecting voice channels, talk groups, and virtual talk groups (VTGs), Cisco IPICS bridges communications from radio networks to the Cisco IPICS Push-to-Talk Management Center (PMC) PC application and supported models of Cisco Unified IP Phones.
To provide this functionality, Cisco IPICS uses new components, such as the Cisco IPICS server and the PMC, and existing technologies, such as Land Mobile Radio (LMR), Cisco gateways, and Voice over IP (VoIP) technology, along with new applications of existing technologies, such as the use of the router media services (RMS) functionality for channel mixing.
Through the use of integrated web-based system management software, the Cisco IPICS solution facilitates the tasks that are associated with operations and command and control to extend the reach of push-to-talk (PTT) voice technology from the LMR environment to the IP network.
The following examples portray typical customers who use disparate networks:
•
PTT radio networks (analog or digital at different frequencies)—These networks are used for voice communications within groups. Communications are usually restricted within a specified group or network.
•
VoIP networks—These networks are used for voice on wired or wireless IP phones or other IP clients, such as personal data assistants and laptop PCs.
Benefits of Cisco IPICS
For these customers, the Cisco IPICS solution provides the following benefits:
•
By incorporating an incident management framework graphical user interface (GUI), Cisco IPICS provides a cost-effective solution that allows you to streamline operations and command and control while protecting your investment in deployed radio networks and applications.
•
Through easy-to-use installation, management, and operational features, the Cisco IPICS solution enables rapid deployment and management of disparate audio communications systems and it provides a migration path to more robust IP applications and devices to cost-effectively achieve greater operational efficiencies.
Related Topics
•
Cisco IPICS System Components
•
Cisco IPICS User Roles
Cisco IPICS System Components
The Cisco IPICS solution comprises the following major components, as described in Table 1-1:
Table 1-1 Cisco IPICS System Components
Component
|
Description
|
Cisco IPICS Server
|
This component provides the core functionality of the Cisco IPICS system. The Cisco IPICS server software runs on the Cisco Linux operating system on selected Cisco Media Convergence Server (MCS) platforms. (Refer to the Cisco IPICS Compatibility Matrix for information about the servers that Cisco IPICS supports.)
The Cisco IPICS server software includes the Cisco IPICS Administration Console, which is an incident management framework administration GUI that enables dynamic resource management for users, channels, and VTGs. (In Cisco IPICS, VTGs combine one or more channels and/or users.) By using this GUI, authorized Cisco IPICS users can manage the system configuration and authentication and security services, policies and privileges, and database information.
The server also enables control of the configuration of the media resources that are installed in the router and which are used for audio mixing capabilities.
In addition, the server includes the Cisco IPICS policy engine (hereafter referred to as policy engine), which enables telephony dial functionality and is responsible for the management and execution of policies and user notifications.
For more information about the role of the Cisco IPICS server, see the "The Role of the Cisco IPICS Server" section.
For more information about the various user roles that Cisco IPICS supports, see the "Cisco IPICS User Roles" section.
|
Push-to-Talk Management Center (PMC)
|
The PMC is a PC-based software application that comprises a stand-alone PTT audio application that connects end-users, dispatch personnel, and administrators via an IP network. This connection enables participation in one or more talk groups or VTGs at the same time. (VTGs are the voice channels that users connect to based on specific incidents.)
PMC users may change the appearance of the PMC user interface by choosing another Cisco-provided or custom skin.
The PMC runs on the Microsoft Windows 2000 and Windows XP operating system. See the "System Requirements for the PMC Application" section for information about PMC hardware and software requirements.
|
Gateways
|
This component includes LMR gateways, which functionality is usually installed as an additional feature in a supported Cisco router. LMR gateways provide voice interoperability between radio and non-radio networks by bridging radio frequencies to IP multicast streams.
Cisco IPICS leverages the Cisco Hoot 'n' Holler feature, which is enabled in specific Cisco IOS versions, to provide radio integration into the Cisco IPICS solution. LMR is integrated by providing an ear and mouth (E&M) interface to a radio or other PTT devices, such as Nextel phones. Configured as a voice port, this interface provides the appropriate electrical interface to the radio. You configure this voice port with a connection trunk entry that corresponds to a voip dial peer, which in turn associates the connection to a multicast address. This configuration allows you to configure a corresponding channel in Cisco IPICS, using the same multicast address, which enables Cisco IPICS to provide communication paths between the desired endpoints.
|
Router Media Service
|
The Router Media Service (RMS) component enables the PMC to remotely attach to a VTG. It also provides support for remotely attaching (combining) two or more VTGs through its loopback functionality. (The RMS mixes multicast channels in support of VTGs as well as PMC SIP-based (unicast) connections to a multicast channel or VTG.) The RMS can be installed as a stand-alone component (RMS router) or as an additional feature that is installed in the LMR gateway.
For a list of Cisco IOS versions that Cisco IPICS supports for use as an RMS, refer to the Cisco IPICS Compatibility Matrix. (Each supported Cisco IOS version includes the Cisco Hoot `n' Holler feature.)
|
Networking Components
|
The Cisco IPICS solution may include some or all of the following network components, depending on the functionality that you require: routers, switches, firewalls, mobile access routers, wireless access points, and bridges.
|
Cisco Unified CallManager and VoIP Services
|
Cisco IPICS provides support for SIP-based interoperability with supported versions of Cisco Unified CallManager and Cisco IOS, with optional Cisco Unified CallManager Express, and VoIP services, such as the Cisco Unified IP Phone services, to help extend the reach of PTT technology to the IP network. These services allow participation in channels and/or VTGs through the use of supported models of Cisco Unified IP Phones by enabling these phones to work with Cisco IPICS as IP phone multicast client devices.
|

Note
For detailed information about supported hardware and software that is compatible for use with Cisco IPICS, refer to the Cisco IPICS
Compatibility Matrix.
Cisco IPICS User Roles
The Cisco IPICS solution authorizes access to different features based on the role that is assigned to each user. Cisco IPICS users may have one or more roles, such as system administrator, ops view administrator, operator, dispatcher, or user.
Table 1-2 describes the user roles that Cisco IPICS supports. For more information about how these roles interact, see the "Cisco IPICS Server-PMC Interaction Scenario" section.
Table 1-2 Cisco IPICS User Roles
User Role
|
Description
|
System Administrator
|
The system administrator is responsible for installing and setting up Cisco IPICS resources, such as servers, routers, multicast addresses, locations, and PTT channels. The system administrator also creates ops views, manages the Cisco IPICS licenses and PMC versions, and monitors the status of the system and its users via the activity log files. The system administrator has the ability to administer all resources in the Cisco IPICS system.
|
Ops View Administrator
|
The ops view administrator capabilities include managing and monitoring the activity logs that are filtered by ops views and accessible in the Administration Console (Administration > Activity Log Management) window.
|
Operator
|
The operator is responsible for setting up and managing users and policies, configuring access privileges, and assigning user roles, and ops views. Policy management activities include create/modify/delete policies, view policies, execute policies, and activate privileges.
|
Dispatcher
|
The dispatcher is responsible for setting up the VTG templates, activating the VTGs to begin conferences, and adding and/or removing participants in VTG templates and active VTGs. The dispatcher also monitors the active VTGs and events, can mute and unmute PMC users, as necessary, and manages policies, which activate/deactivate VTGs based on specific criteria and designated intervals. Policy management activities include create/modify/delete policies, view policies, execute policies, and activate privileges.
|
User
|
The Cisco IPICS user may set up personal login information, download the PMC application, configure the PMC skin to select the PMC display mode and other options, and specify communication preferences that are used to configure audio devices. By using a predefined user ID and profile, the user can participate in PTT channels and VTGs by using the PMC, supported models of Cisco Unified IP Phones, and the Public Switched Telephone Network (PSTN) via the telephony dial functionality of the policy engine.
|
Related Topics
•
About the PMC Application
•
PMC Application Usage Caveats
•
Architecture/Deployment
•
System Requirements for the PMC Application
•
System Interactions
•
Cisco IPICS Server-PMC Interaction Scenario
About the PMC Application
This section contains information about the PMC application and it includes the following topics:
•
Browser Support
•
Work Flow Activities
•
PMC Application Usage Caveats
The PMC application provides the interface that enables push-to-talk audio communications. By using a simplified GUI, the PMC allows simultaneous monitoring and participation in one or more talk groups or VTGs at the same time.
The Cisco IPICS operator enables your user profile for access to the PMC application.
After you have been authorized to use the system, you can download the PMC software from the Cisco IPICS server and install it on your PMC client machine. For more information, see the "Downloading and Installing the PMC Application" section.
See Figure 1-1 for an illustration of the PMC application. This example shows a partial illustration of the PMC that has been configured for mouse-based use with the 18-channel advanced feature console.
Figure 1-1 PMC with Partially-Displayed 18-Channel Advanced Console Skin

1
|
Activation/ Deactivation Button
|
Click this button to activate a channel; click again to deactivate. The activation button highlights and changes orientation when you activate it.
For more information about the PMC buttons, see the "Activating the PMC Buttons" section.
|
2
|
PTT Channel Button with Receive Indicator and Latch Indicator
PTT Channel with Warning Indicator
|
Click the PTT channel button with your mouse, or push, and hold it to talk. When you are done talking, release the left mouse button to return to listen-only mode.
The PTT channel button highlights in a different color when the PMC is in transmission mode. (The touch screen skins include a transmit indicator that blinks red when the PMC is transmitting traffic; for more information about caveats that pertain to the touch screen skins, see the "Touch Screen Skin Caveats" section.)
The PTT channel button includes a receive indicator, which blinks green when the PMC is receiving traffic. For more information about traffic activity indicators, see the "Traffic Activity" section.
This button may include a latch indicator. If you have permission to use the latch functionality, you can latch this channel to talk on one or more channels at the same time. To latch, or lock in, the PTT channel, click the latch indicator that displays to the right of the PTT channel button. To clear the latch, click the latch indicator or click the PTT button to release and return to listen-only mode. For more information about using the latch functionality, see the "Using the Latch Functionality" section.
Note If you encounter a SIP-based remote connection failure, the PMC displays a warning indicator in the form of a yellow triangle next to the specific channel, as shown in the column to the left. For more information, see the "Support for Cisco IPICS Recovery" section and the "Identifying Channel Activation Issues" section.
|
3
|
Channel Select Check Box
|
Check or uncheck this check box to select or deselect the channel for PTT communications. For more information about using the channel select check box, see the "Selecting One or More Channels and Using the All Talk Channel" section.
|
4
|
Voice Replay Controls
|
Use the voice replay functionality to play back buffered voice transmissions and to view graphical representation of this functionality.
Note You must click the jump back, or rewind, button to enter voice replay mode and play out the available, recorded audio.
For more information about the voice replay feature, see the "Using the Voice Replay Feature" section.
|
5
|
Volume Up Button
|
Click this button to increase the volume on the channel.
|
6
|
Volume Down Button
|
Click this button to decrease the volume on the channel.
|
7
|
Volume Level Indicator Bar
|
This bar shows the current volume level on the channel in a graphical format. This indicator represents the changes that you make by clicking the volume up and volume down buttons.
|
8
|
Server Status Connectivity Indicator
|
This connectivity indicator specifies your connectivity status with the server.
• When your PMC is connected to the server, a green connectivity indicator displays.
• When your PMC is not connected to the server, a red connectivity indicator and an alert icon display, as shown in the graphic.
Note The PMC updates this connectivity status dynamically based on the status of its connectivity with the server. For more information, see the "Using the Status Menu" section.
|
9
|
Menu Button
|
Click the menu button to access the PMC settings menus and online help.
|
10
|
All Talk Channel Button
|
Click the All Talk channel to simultaneously talk on all of the channels that you selected. For more information, see the "End-user Features and Interactions" section.
|
11
|
Select All and Deselect All Buttons
|
Click the Select All (multiselect) button to select all channels that are assigned to you; click the Deselect All button deselect all channels. For more information about selecting multiple channels, see the "Selecting One or More Channels and Using the All Talk Channel" section.
|
12
|
Alert Tone Buttons
|
Use these buttons to play out alert tones on one or more channels on the PMC. The PMC plays out alert tones only on the channel(s) that you select. For more information, see the "Playing out Alert Tones" section.
|

Tip
You can change the appearance of the PMC user interface by choosing another Cisco-provided or custom skin. For more information, see the "Configuring the PMC End-User Interface" section.
Note
Your ability to use some of the PMC advanced features depend on specific user permissions that are configured in the server. For more information about user privileges, see the "User Privileges" section.
The PMC GUI includes buttons that allow you to interact with the Cisco IPICS server. It also includes various indicators to enable visibility of the connection status of the server and inform you about activities such as transmission status, channel states and activity, and volume level indicators.
The PMC GUI includes the PTT channel button, and other buttons, such as the activation button and buttons to control the volume level. The advanced skin may also include additional functionality, such as voice replay, alert tone buttons, the All Talk button, and multiselect channel check boxes; be aware that you must have permission to use some of these features.
The GUI also includes an indicator that blinks when you receive traffic; when you transmit traffic, the PTT channel button highlights and changes color to indicate transmission. (The touch screen skins also include an indicator that blinks when you transmit.) See the "Traffic Activity" section for more information about these indicators.
Note
The PMC modifies the channel behavior when you use the touch screen skins; for more information, see the "Touch Screen Skin Caveats" section.
When a channel has been activated, the PTT button displays on the PMC in a highlighted color that is based on the configuration in the Cisco IPICS server.
Note
If your ability to transmit on a channel has been disabled by the server, the PTT button will not highlight on the PMC.
Because the Cisco IPICS server controls the configuration of the PMC application, PMC users have limited access to the configuration parameters; however, Cisco IPICS includes the ability for PMC users to modify some of the configuration elements, such as the PMC GUI skins for mouse-based or touch screen-based display and key mapping. For additional information about configuring the end-user interface, see "Configuring the PMC Application."
Browser Support
You install the PMC application on your local PC by downloading the software from the Cisco IPICS server upon successful user authentication. Cisco IPICS supports secure Internet access to the server by providing support for the following browser:
•
Internet Explorer 6.0.2
After successful software download and installation, you log in to the PMC application on your PC. See "Installing and Upgrading the PMC Application," for additional information about installing and launching the PMC application.
Work Flow Activities
The following activities occur when you use the Cisco IPICS system:
1.
The Cisco IPICS operator sets up the necessary channel and VTG definitions on the server.
2.
The PMC then retrieves the personalized list of channels and/or VTGs from the server.
3.
You can join VTG(s) by selecting the channel(s) that the dispatcher associates with the VTG(s) and assigns to your user ID. (Only active channels and VTGs display on your PMC.)
4.
When the dispatcher deactivates one or more VTG(s), you will no longer have access to the channel(s) that were created to support these VTG(s).
Note
Cisco IPICS enables the dispatcher to dynamically add or remove PTT channels.
PMC Application Usage Caveats
Be aware of the following caveats when you use the PMC application with this release of Cisco IPICS:
•
Only one instance of the PMC application can be open on a given PC at a time.
•
A running PMC supports only one active user ID login on a given PC at a time.
•
Any number of valid Cisco IPICS users can use the same PMC application, but not concurrently, based on PMC licensing requirements. See the "License Information" section for more information about these licensing requirements.
•
Each PMC application connects to only one Cisco IPICS server. If the primary server becomes unavailable, you can connect to an alternate server by entering the alternate server IP address or host name or by choosing the IP address for an alternate server from the Cisco IPICS login dialog box. For more information about logging in to alternate servers, see the "PMC Login Procedure" section and the "Support for Cisco IPICS Recovery" section.
•
The dispatcher assigns the voice channels that you can use on your PMC application, as they are needed. The dispatcher also activates and deactivates the channels that support the VTGs.
•
The PMC retrieves, from the server, the channel name that displays on an assigned channel on your PMC application. This name may change based on the configuration in the server.
•
When the dispatcher deactivates one or more VTG(s), you will no longer have access to the VTG(s) and the VTG(s) are removed from your PMC.

Tip
You have the ability to simultaneously listen in on multiple voice channels that are activated on the PMC application. You can also talk on multiple channels at the same time by using the PTT latch functionality, if you have user permissions configured in the server. To latch, or lock in, the PTT button, click the latch indicator or position your cursor over the PTT button and then press the Shift key while you click the left mouse button. Follow this procedure for each channel that you want to talk on. To clear the latch, click the PTT button without holding the Shift key. Alternatively, and if you have user permissions, you can select the channels that you want to talk on and click and hold the All Talk channel. For more information about using the All Talk channel, see the "Selecting One or More Channels and Using the All Talk Channel" section.

Caution 
Be aware that when you latch the PTT button, this action blocks transmissions from half-duplex radios when these devices are attached to the channel or VTG via an LMR gateway.
For detailed information about using and configuring the PMC application, See "Using the PMC Application" and "Configuring the PMC Application."
Related Topics
•
Installing the PMC Application
•
Launching the PMC Application
•
Maintaining and Upgrading the PMC Application
•
Logging In to the PMC Application
•
License Information
•
Using the PMC Application
•
Configuring the PMC End-User Interface
Architecture/Deployment
A Cisco IPICS server-client deployment consists of a Cisco IPICS server and multiple PMC client systems. The PMC client systems connect to the Cisco IPICS server through a wired or wireless network. Additional components, such as routers and gateways, enable interoperability and additional capabilities. (See Figure 3-1 for an illustration of this interoperability.)
The PMC is a network-installable application that is remotely managed by the Cisco IPICS server. An authenticated and authorized user can perform the PMC installation via a secure Web login to the Cisco IPICS server. After the PMC is installed, any valid and authorized Cisco IPICS user can log in to the PMC application. The server validates the user login credentials.
As a part of the login process, all user configuration information is downloaded and stored in conjunction with the login credentials. If the PMC becomes disconnected from the Cisco IPICS server, a user with a valid login may continue to use the application in offline mode.
The Cisco IPICS architecture includes centralized management of the PMC application, and specifically, the centralized (role-based) definition of the VTGs in the server. (This model compares to other PTT end-device models where the end-user defines the VTGs or uses a point-to-point session establishment mechanism.)
The fundamental design of the PMC is to present the end-user with channels, as managed by the Cisco IPICS dispatcher, and to provide users with the tools that they need to use these channels in an efficient manner.
Figure 1-2 shows a simplified version of a Cisco IPICS deployment by illustrating the interaction between the Cisco IPICS server and the PMC components.
Figure 1-2 Cisco IPICS Deployment
The following example represents a simplified flow that occurs between the Cisco IPICS server, the PMC, and other associated components:
1.
The Cisco IPICS dispatcher creates a voice channel, or VTG, that correlates to a specific incident and assigns the necessary channels to the users.
2.
By using the Cisco IPICS server GUI, the dispatcher includes the relevant users, channels, and other resources in the VTG.
3.
Based upon this configuration, and after the dispatcher has activated the VTG, the server automatically refreshes the PMC so that it displays the VTG on the PMC client machine. (This voice channel contains the associated configuration to interwork as defined by the server; see 5. below.)
4.
To directly join the channel, the PMC user clicks the Activate button on the PMC application. The Activate button highlights and the system attempts to connect to the channel or VTG. After the connection has been established, the remaining PMC buttons, including the PTT channel button, highlight to indicate that they are in an active state. (If your ability to transmit on a channel has been disabled by the server, the PTT button will not highlight.) See Figure 1-1 for an illustration of the PMC application.
5.
Depending on the configuration that the PMC retrieves from the Cisco IPICS server, the PMC directly joins the channel by using one of the following connection types, which are based on the defined location:
a.
Remote connection—This type of connection uses SIP-based trunking into the RMS component, which is directly tuned into the multicast channel.
b.
Multicast address/port—This type of connection enables the PMC to directly tune in to the multicast channel.
For more information about locations and types of connections, see the "Location Support" section.
6.
The PMC user communicates with other members of the VTG by using push-to-talk capabilities.
7.
When the incident has ended, the dispatcher deactivates the VTG; the server automatically refreshes the PMC and removes the VTG from the PMC application.
Related Topics
•
Scenarios for Using the PMC Application
•
Location Support
System Requirements for the PMC Application
This section includes information about hardware and software requirements for the PMC application, as well as pertinent caveats.
•
Hardware Requirements
•
Software Requirements
Hardware Requirements
The PMC application requires the following minimum hardware, as shown in Table 1-3. These requirements are dependent on the number of active PMC channels that you use.
Note
Make sure that you install the PMC application on a PC that has the required Windows operating system installed. Cisco IPICS supports Windows 2000 Professional SP4 and Windows XP Professional SP2 for use with the PMC.
Table 1-3 PMC Minimum Hardware Requirements
Number of PMC Channels
|
PMC Hardware Requirements
|
Up to 4 active channels
|
• 800 MHz Pentium III class, including Mobile Pentium
• 512 MB RAM
• 1 GB free space
• Network interface card
|
Up to 6 active channels
|
• 1.5 GHz Pentium IV class, including Mobile Pentium
• 512 MB RAM
• 1 GB free space
• Network interface card
|
Up to 18 active channels
|
• 3.2 GHz Pentium IV class, including Mobile Pentium
• 2 GB RAM
• 1 GB free space
• Network interface card
|
Software Requirements
Table 1-4 includes reference information about the software and applications that you install on your PMC system.
Table 1-4 PMC Systems Software
Software
|
Description
|
Reference
|
Windows operating system
|
• Windows 2000 Professional SP4, or
• Windows XP Professional SP2
|
Refer to your Microsoft Windows documentation for installation and configuration instructions.
|
PMC application
|
Provides access to the PMC features
|
See "Installing and Upgrading the PMC Application."
|
System Interactions
This section includes information about some of the system interactions that occur when you use Cisco IPICS, and includes the following topics:
•
Server Interactions
•
User Interactions
Server Interactions
The following section provides information about server-level interactions with Cisco IPICS.
Configuration Management
The Cisco IPICS server manages the configuration of the PMC and provides regular updates to the PMC. The server controls activities such as user profile management, user authentication, enabling/disabling/muting/unmuting users, enabling/disabling channels, activating/deactivating VTGs, updating the PMC configuration, and managing the PMC logs.
Session Management
The Cisco IPICS server manages the sessions on each of the PMC client machines.
•
For each PMC, the server generates a unique PMC ID to track requests between the PMC and the server.
•
After a PMC session is authenticated and initiated, the server begins a periodic check with the PMC to execute commands or to update the configuration on the PMC.
These updates can include activities such as refreshing the PMC application based on new channel assignments or VTG activations/deactivations and notifying the PMC about new updates to ensure version compatibility.
See the "Maintaining and Upgrading the PMC Application" section and "Dynamic Configuration" section for more information.
Login Authentication
The Cisco IPICS server manages the login requests from PMC users. Initial login to the PMC application includes logging through the PMC application in to the Cisco IPICS server. The server then creates a session and identifies the PMC by the unique PMC ID.
If the server goes offline, the PMC user may be able to continue to use the PMC in offline mode as long as the user has made one successful login to the server.
Channel Management
The Cisco IPICS server downloads all of the currently available channels that can be displayed for a particular user based on each PMC session. When the dispatcher adds a user to a particular VTG, the server notifies the PMC of that updated channel availability.
•
If a name, or label, has been configured in the server for a PMC PTT channel button, that name displays in the channel area as part of the PTT button on the PMC.
•
The name may change, based on the configuration in the Cisco IPICS server.
•
The channel may also include a channel type, such as VTG or 2-way, for quick identification of the channel.
•
The channel may also display other attributes, such as specific background text colors that uniquely identify the channels for added prominence.
For more information, see the "Channel Information" section.
•
The server may also download a designated channel (such as a dispatcher channel) to the PMC by setting up a policy. See the "Implementing Policies" section for more information.
User Interactions
This section provides information about user-level interactions with Cisco IPICS.
End-User Application Interaction
The Cisco IPICS server provides the list of PMC skins that are available to the PMC application. The server also defines a default skin for the PMC. The PMC stores the skins locally on the PMC user client machine.
The PMC user may choose a different skin by accessing the Settings > Skin menu in the PMC application. The functionality that is available may vary based on the skin that you choose.
See Table 5-1 for a list of the PMC skins that Cisco IPICS supports.
For more information about configuring the PMC skins, see the "Configuring the PMC Skins" section.
End-User Channel Interaction
Channels and VTGs display in various states on the PMC. See Table 4-1 for a description of the states that Cisco IPICS supports for user interaction.
For more information about using the PMC application, see "Using the PMC Application."
Related Topics
•
PMC-Server Interactions
•
Maintaining and Upgrading the PMC Application
•
Implementing Policies
•
Dynamic Configuration
•
Using the PMC Application
•
Channel Interactions
•
Configuring the PMC Skins
Where to Find More Information
•
Cisco IPICS Server Administration Guide