Cisco IPICS Server Quick Start Guide, Release 2.1(1)
Cisco IPICS Server Administration
Downloads: This chapterpdf (PDF - 466.0KB) The complete bookPDF (PDF - 1.23MB) | Feedback

Cisco IPICS Server Administration

Table Of Contents

Cisco IPICS Server Administration

Managing Cisco IPICS Licenses

Logging In to and Out of Cisco IPICS

Accessing Online Help in the Administration Console

Important Cisco IPICS Concepts

Understanding Locations

Understanding VTGs

Understanding Ops Views

Ops View Port Allocation

Ops View Attributes

Ops View Considerations

Understanding Associations

Cisco IPICS Roles and Associated Tasks

System Administrator Tasks

Ops View Administrator Tasks

Operator Tasks

Dispatcher Tasks

User Tasks


Cisco IPICS Server Administration


This chapter describes the various administration tasks and concepts that are important to understand when you use Cisco IPICS and includes the following sections:

Managing Cisco IPICS Licenses

Logging In to and Out of Cisco IPICS

Accessing Online Help in the Administration Console

Important Cisco IPICS Concepts

Cisco IPICS Roles and Associated Tasks

You install the Cisco IPICS software on supported Cisco Media Convergence Servers (MCS). For information about hardware and software that is compatible for use with Cisco IPICS, refer to the Cisco IPICS Compatibility Matrix.

Before you can perform administration tasks in Cisco IPICS, you must first install the Cisco IPICS operating system and the Cisco IPICS server software. For detailed information about installing Cisco IPICS, refer to the Cisco IPICS Server Administration Guide, Release 2.1(1).

Managing Cisco IPICS Licenses

You must first purchase and upload the applicable Cisco IPICS server license file(s) to use any of the features that are available in Cisco IPICS or to use the Cisco IPICS Administration Console.

After you complete the Cisco IPICS installation, you use the Product Authorization Key (PAK) that was included in your Cisco IPICS product package to obtain the license file.

The license that you purchase is based on the total number of the following licensable features:

The concurrent number of land mobile radio (LMR) ports

The concurrent number of multicast ports

The concurrent number of PMC users

The concurrent number of Cisco Unified IP phone users

The concurrent number of dial users (this feature is dependent on the policy engine, which must be specifically licensed and enabled for use)

The total number of ops views


Tip The total number of licensable features cannot exceed the number that is specified in the license or licenses that you purchased. If you require additional licenses, contact your Cisco representative.



Note You may use valid Cisco IPICS release 2.0(x) license(s) for use with this release.


To purchase your Cisco IPICS license file(s), access the following URL:

http://www.cisco.com/go/license


Tip Be sure to register with Cisco.com before trying to process a license order.


After you have purchased your license file, you can upload the file(s) by accessing the Administration > License Management window in the Administration Console. Refer to the Cisco IPICS Server Administration Guide, Release 2.1(1) for information about how to upload and apply your Cisco IPICS licenses.

Cisco IPICS does not overwrite older license files with newer license files. As a best practice, Cisco recommends that you take the following action when license changes occur, such as when you replace a time-bound (demonstration or evaluation) license with a permanent license:

Make sure that you remove the old license file(s) from the directory where Cisco IPICS stores the license(s).

For more information about deleting time-bound licenses, refer to the Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1).

After you remove the old license(s), restart the server by entering the following command:

[root] service ipics restart

Logging In to and Out of Cisco IPICS

You must log in to the Cisco IPICS Administration Console to perform any administration functions. When you have finished using Cisco IPICS, you should log out of the Administration Console.

You must install the Cisco IPICS operating system and server software, and upload one or more license files before you can log in to Cisco IPICS. For detailed information about obtaining license file(s), refer to the "Managing Licenses" section in the Cisco IPICS Server Administration Guide, Release 2.1(1).

To log in to and out of Cisco IPICS, complete the following steps:


Step 1 To log in to Cisco IPICS, follow these steps:

a. Launch your browser and enter the IP address or host name of the Cisco IPICS server in the Address field.

b. Enter your user name and password.


Note Be aware that passwords are case-sensitive and must be entered exactly as they were configured by the Cisco IPICS operator.


c. Click Log In.

The Cisco IPICS Administration Console displays the My Profile window. You see only the information that relates to your user ID and the user role that has been assigned to you.

Step 2 To log out of Cisco IPICS, click the Logout button that displays in the menu at the top of the Administration Console window.

The Cisco IPICS window closes and displays the Cisco IPICS login window.


Accessing Online Help in the Administration Console

You can access the Cisco IPICS online help system from any window in the Administration Console by clicking Help link that displays at the top of the window. The help system provides online access to the information that is contained in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Important Cisco IPICS Concepts

The following sections include information about important concepts that you need to know when you use Cisco IPICS:

Understanding Locations

Understanding VTGs

Understanding Ops Views

Understanding Associations

Understanding Locations

In Cisco IPICS, locations are used to define multicast domains within a Cisco IPICS deployment. A multicast domain comprises a set of multicast addresses that are reachable within a multicast network boundary. This implementation enables the Cisco IPICS server to assign the appropriate multicast address based on a specific user location.

In addition to specifically assigning names to locations, Cisco IPICS includes two predefined locations: ALL and REMOTE.

The ALL location signifies no network boundaries; that is, a channel that is designated with the ALL location means that there are no network boundaries within the Cisco IPICS deployment for that associated multicast address.


Note The ALL location defines the scope or reachability or a multicast address. For this reason, the ALL location is applicable to channels and VTGs, which are associated with multicast addresses, but not applicable to IP phones and RMS components, which are not associated with multicast addresses.


Channels that are designated with the ALL location can be mixed on any RMS, including RMS components that are not configured with the ALL location, because any RMS can send packets to a multicast address that is associated with the ALL location.

VTGs are always associated with the ALL location because every VTG multicast address is dynamically-assigned and associated with the ALL location.

The REMOTE location is available only to PMC users. When a PMC user chooses the REMOTE location from the drop-down list box, connectivity is established with the appropriate RMS via a SIP-based unicast connection for each channel (should have at least one media connection of multicast type) or VTG that has been assigned to the user.

For each channel (should have at least one media connection of multicast type) that is associated with the user, the PMC establishes a SIP-based unicast connection with the RMS that is defined in the same location as the channel.

For each VTG that is associated with the user, the PMC can establish a SIP-based unicast connection with any RMS because VTGs always use a multicast address in the ALL location.

In all cases, the Cisco IPICS server allocates RMS resources upon successful PMC authentication. When additional channels or VTGs are assigned to a logged-in user, the server immediately allocates the necessary RMS resources for each channel or VTG. When the PMC user activates the channel or VTG, the PMC places the SIP call to the appropriate RMS.


Note Each RMS component that you configure for use with Cisco IPICS must be associated with a location. An RMS can host only those channel resources that are assigned to the same location as the RMS or to the ALL location. If the RMS is associated with the ALL location, it can host only those channels that are also assigned to the ALL location. Because of this implementation, Cisco recommends that you do not assign the ALL location to an RMS.



Tip Whenever possible, user access via multicast communications is preferable over SIP to minimize the use of RMS resources.


For more detailed information about configuring locations, refer to the Cisco IPICS Server Administration Guide, Release 2.1(1) and the Cisco IPICS PMC Installation and User Guide, Release 2.1(1).

Understanding VTGs

A VTG enables multiple participants on various channels to communicate by using a single multicast address. Participants in a VTG can include users, user groups, channels (PTT and radio), channel groups, and other VTGs. An active VTG is a VTG in which all the participants have live connections with each other.


Note To prevent audio loops from occurring, Cisco IPICS allows only one VTG to be active at a given time.


Cisco IPICS dispatchers can stage a VTG by creating an inactive VTG. The dispatcher uses an inactive VTG to arrange participants who can communicate when the VTG gets activated.

An inactive VTG allows the dispatcher to create various arrangements of members without committing network resources or affecting other VTGs that are in progress.

After the VTG is activated, the dispatcher can add and remove users, channels, and other VTGs, notify and dial out to VTG participants, and mute and unmute PMC users at any time; however, when the dispatcher makes changes to an active VTG, the original inactive VTG remains unchanged.


Note Activation or deactivation of a VTG requires that the Cisco IPICS server communicate with the RMS. If a VTG is deactivated during the time when the RMS becomes unavailable, the deactivation occurs in the Cisco IPICS database, but is not reflected in the RMS until the Cisco IPICS server is back in communication, and synchronizes with, the RMS.


For more detailed information about VTGs, refer to the Cisco IPICS Server Administration Guide, Release 2.1(1).

Understanding Ops Views

Cisco IPICS operational views (ops views) provide the ability to organize or segment different entities, such as agencies, companies, departments, jurisdictions, municipalities, or sites, into separate views that are isolated from each other, providing increased security by limiting operator and dispatcher access. While these views are maintained separately by the system administrator, this functionality also allows multiple entities to use one Cisco IPICS server to enable resource sharing across multiple ops views, according to business need. In other words, resources in separate ops views are not accessible to users in other ops views unless the users are granted permission to access them.


Note The use of ops views allows segmentation of resources that authorized Cisco IPICS users may see on the Administration Console. Ops views does not affect the way in which channels and VTGs display on the PMC or Cisco Unified IP Phone.


Ops View Port Allocation

When you purchase Cisco IPICS license(s), the license includes a specified number of ops views that you can configure. By default, Cisco IPICS includes the SYSTEM ops view with every installation. Cisco IPICS users who belong to the SYSTEM ops view can view all ops views, and their resources, that are configured on the system.

Each time the system administrator adds a new ops view, ports are reallocated from the SYSTEM ops view and distributed to the newly created ops view. The system administrator determines the number and types of ports, such as PMC ports, LMR ports, and dial ports that are needed for a particular ops view.


Note If the Cisco IPICS license contains the policy engine, the system administrator can configure dial port information per ops view.

When you add dial numbers (DNs) for ops views in a Cisco IPICS deployment that includes the policy engine, and if the new DNs fall outside of existing route patterns that are assigned to a session initiation protocol (SIP) trunk (in Cisco Unified Communications Manager) or outside of existing destination patterns that are assigned to a dial peer (in Cisco IOS), you must update the SIP provider configuration to include the new DNs. For detailed information, refer to the Cisco IPICS Server Administration Guide, Release 2.1(1).


When an ops view gets deleted, the system administrator has the option to reallocate the resources that were in the deleted ops view to other existing ops views in the system.

You must allocate dial ports for users to be able to dial in to Cisco IPICS, dial out to other users, or for the system to notify users. These dial ports are configured in the Dial Information and Dial Port Resources Allocation pane, in the Configuration > Ops Views > <ops view name> window.

Dial port containers (also referred to as dial pools) allow you to configure reserve dial ports that are used only for specific dial functions (such as dial-in/invite and notification). Reserved dial ports ensure that you always have ports that are configured specifically for this use and which cannot be used for any other purpose.

The following dial pools are used for reserving ports for dial-in/invite and notification:

Dial ports reserved for dial-in/invite—This dial pool contains dial ports that can be used only for the dial-in and invite features.

Dial ports reserved for notification—This dial pool contains dial ports that can be used only for the notification feature.

The Dial ports reserved for dial-in/invite or notifications field is a read-only field that displays ports that Cisco IPICS allocates for both dial-in/invite and notification actions. The ports that display in this field are the ports that remain after you have reserved dial ports for dial-in, invite, and notification. The remaining number are the dial ports that are reallocated from the total number of dial ports in the Dial Ports dial pool.


Note When you create a new ops view, dial port licenses are reallocated from the SYSTEM ops view to the new ops view, but there is no adjustment to the dial port numbers that were configured in the Dial ports reserved for dial-in/invite and Dial ports reserved for notification dial pools for the SYSTEM ops view. For the new ops view, if the dial port numbers that you configure in the reserved dial pools exceed the number of ports in the Dial Ports field, Cisco IPICS displays an error message to alert you. To resolve this issue, reduce the number of reserved ports in the SYSTEM ops view to an appropriate number and try again.


For more detailed information about dial port allocation, refer to the "Allocating Dial Ports for the Dial-In/Invite and Notification Features" section in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Ops View Attributes

Cisco IPICS ops views support the following attributes:

Belongs To

This attribute determines the ops view that the resource belongs to. In other words, the ops view that you specify for this attribute is the ops view that owns this resource.

A resource belongs to only one ops view.

For users, the Belongs To attribute determines the resources that users see when they log in to the Cisco IPICS system. A user can view only those resources that are accessible to the ops view to which they belong.

A VTG belongs to the same ops view as the dispatcher who created the VTG. A dispatcher who belongs to a specific ops view will always have visibility to the VTGs that belong to that same ops view.

A policy belongs to the same ops view as the dispatcher who created the policy. A dispatcher who belongs to a specific ops view will always have visibility to the policies that belong to that same ops view.


Note Only an operator or a dispatcher who belongs to a certain ops view should create, edit, or delete policies that are associated with that ops view. For more information, refer to the Cisco IPICS Server Administration Guide, Release 2.1(1).


When a user logs in to a PMC or a Cisco Unified IP Phone, that user uses a PMC or Cisco Unified IP Phone usage license. Cisco IPICS calculates this license usage against the license limit of the ops view that the user currently belongs to.

When a dispatcher activates a VTG, or when an enabled policy activates a VTG, that VTG uses a concurrent multicast port license. Cisco IPICS calculates this license usage against the license limit of the ops view that the dispatcher belongs to. When an enabled policy activates a VTG, the ops view that the policy belongs to is charged the license usage for activation of that VTG.

Cisco IPICS calculates license usage for a concurrent LMR port against the license limit of the ops view that a channel belongs to. This usage is calculated on a per-connection basis.

Accessible To

This attribute specifies that the resource is accessible to, or visible to, the ops view(s) that Cisco IPICS displays in this field.

Users have access only to the resources that are accessible to the ops view to which they belong.

A resource can be accessible to an unlimited number of ops views.

The SYSTEM ops view can always access all resources even if it does not explicitly appear in the list of accessible ops views.


NoteWhen you configure a resource to belong to a specific ops view, Cisco IPICS automatically adds that resource as being accessible to that ops view.

When you reconfigure the belongs to field for a resource to a different ops view, Cisco IPICS adds the newly-configured ops view to the accessible to list for that resource. However, Cisco IPICS does not remove the previously-configured ops view from the list of accessible ops views. The resource is accessible to the previous ops view, as well as the newly-configured ops view.


Ops View Considerations

When using ops views, considering the following caveats:

When you are logged in to Cisco IPICS as a user who belongs to the SYSTEM ops view, or when there are no ops views currently in use, the system does not perform any ops view filtering.

Users who do not belong to a specific ops view default to the SYSTEM ops view.

As a Cisco IPICS operator, the system allows you to view and modify only those users who either belong to or are accessible to your ops view. As a Cisco IPICS dispatcher, the system allows you to view and modify only those VTGs that contain resources that either belong to or are accessible to your ops view. You can view only those users and channels that either belong to or are accessible to your ops view.

VTGs and policies always belong to the ops view of the user who created the VTG or the policy.

The dispatcher can see all of the resources in a VTG as long as one of the VTG resources is in the same ops view as the dispatcher or if the VTG belongs to the same ops view as the dispatcher. If the remaining resources are not in the same ops view, the system does not display these resources in the Users or Channels windows.

The system displays only resources that either belong to or are accessible to your specific ops view.

Members of channel and user groups do not inherit accessibility from the groups; therefore, the system displays all of these resources whether or not they are individually accessible to the specific ops view.

When you search for a resource by using the search functionality in the Channels, Users, and VTG windows, the system displays only the resources that are accessible to the specific ops view.

The policies information that the system displays in the Ops Views window reflects the policies that belong to or are accessible to the specific ops view; that is, the policies that the system shows in this area are those policies that were created by someone who belongs to this ops view.

The Cisco IPICS implementation of ops view access for VTGs enables resource sharing among multiple ops views. The ops view functionality allows any dispatcher, who has access to shared resources within a VTG that belongs to a different ops view, to fully access that VTG.


Note When a dispatcher has access to shared resources within a VTG, Cisco IPICS also provides that dispatcher with full control over any of the shared resources in that VTG, such that resources that do not belong to the dispatcher can be modified or deleted.


As a general rule, VTGs inherit accessibility from the resource that it contains.

For detailed configuration information about Cisco IPICS ops views, refer to the Cisco IPICS Server Administration Guide, Release 2.1(1).

Understanding Associations

In Cisco IPICS, you can assign attributes to users that control their behavior. In some cases, attributes may have the same attribute behaviors, so when users are associated to channels or VTGs, the system determines the resulting PMC behaviors based on the attributes that are configured for each associated resource.

For example, a user may be allowed to perform a particular function, such as using the PMC latch feature. However, when the same user is associated to a channel that does not allow the latch feature, the user is not allowed to latch on that channel as long as the user is a part of that particular association. After the user is no longer associated to that channel, the attributes that were originally configured for the user become applicable; that is, the user is allowed to latch channels again.

Cisco IPICS allows values for attributes to be customized or overridden. When attributes of users or channels that are part of an association get modified, the resulting behavior depends on the attribute settings for those users within the association. When you attempt to override a customized value of an attribute in an association, Cisco IPICS prompts you with a message to inform you that the action will override the custom PMC setting for that specific attribute.


Note When you customize the values for attributes a superscript (1) displays next to the value in the appropriate attribute column in the Associations tab, for both the user and the channel. The superscript indicates a customized value.


For more detailed information about attribute association behaviors, refer to the Cisco IPICS Server Administration Guide, Release 2.1(1).

Cisco IPICS Roles and Associated Tasks

Each Cisco IPICS user is assigned one or more roles. Roles define the features that a user can access and the functions that the user can perform.

Cisco IPICS associates specific tasks with every role. Each Cisco IPICS user is assigned a role that determines the scope of user functionality and window accessibility.

The following sections provide brief descriptions of the tasks that Cisco IPICS associates with each role:

System Administrator Tasks

Ops View Administrator Tasks

Operator Tasks

Dispatcher Tasks

User Tasks

System Administrator Tasks

The Cisco IPICS system administrator performs the following tasks, as described in Table 2-1.

Table 2-1 System Administrator Tasks 

Task
Description and Reference

Install Cisco IPICS

Before you can perform any system administrator tasks, you must first install and configure the Cisco IPICS server. To install and configure Cisco IPICS, refer to the Cisco IPICS Server Installation and Upgrade Guide, Release 2.1(1).

Configure the Cisco IPICS server

Configure and manage the RMS component

You perform RMS management in the RMS window. Access this window from the Configuration drawer in the Administration Console. See the "Managing the RMS" section on page 3-1 for more information about the RMS.

For more detailed information about configuring the RMS component, refer to "Configuring the RMS Component" appendix in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Manage locations

You add and delete locations in the Locations window. Access this window from the Configuration drawer.

For more information about locations, see the "Understanding Locations" section. For detailed information, refer to the "Managing Locations" section in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Set up multicast addresses

You set up multicast IP addresses in the Multicast Pool window. Access this window from the Configuration drawer.

For detailed information, refer to the "Managing the Multicast Pool" section in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Configure PTT channels, channel groups, and radios, if applicable

You perform channel and channel group management in the Channels and Channel Groups windows. You perform radio management in the Radios windows. Access these windows from the Configuration drawer.

For more information about radios, see the "Managing Radios" section on page 3-3. For information about radio and tone descriptors, see the "Managing Radio and Tone Descriptors" section on page 3-5.

For detailed information about channel and channel group management, refer to the Cisco IPICS Server Administration Guide, Release 2.1(1).

Manage PMC versions

You upload PMC version packages to the server and configure the PMC installer, as well as manage PMC alert tones, skins, and PMC regions from the PMC Management drawer.

For more information about PMC management, see the "Managing the Cisco IPICS PMC" section on page 3-18. For more detailed information, refer to the "Managing PMC Versions" section in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Monitor system status

You can monitor system status, and view diagnostic and system log information, to use for troubleshooting and to monitor user activity, from the Serviceability drawer.

For more information about monitoring system status, log, and diagnostic information, see the "Cisco IPICS Serviceability" section on page 4-1. For more detailed information, refer to the Cisco IPICS Server Administration Guide, Release 2.1(1).

Review log files

You view log file activities that relate to VTGs, such as operational views (ops views) for each channel, user, and VTG, the creator of log entries, and the time that log activities occurred. You can also download archived log entries for historical reporting. You can perform log activities from the Administration drawer.

For more detailed information about log activities, refer to the "Managing Activity Logs" section in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Create and manage Cisco IPICS ops views

Ops views enable the use of resource sharing on one Cisco IPICS server. You perform ops view management in the Ops View window from the Configuration drawer.

For more information about ops views, see the "Understanding Ops Views" section. For more detailed information about ops views, refer to "Configuring and Managing Cisco IPICS Operational Views" in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Back up and restore the Cisco IPICS database

You can back up and restore the Cisco IPICS database, as well as download the backup and restore activity log files, in the Database Management window. Access this window from the Administration drawer.

For more information, see the "Cisco IPICS Database Management" section on page 4-8. For detailed information, refer to "Performing Cisco IPICS Backup and Restore Operations" in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Set up Cisco Unified IP Phones

You configure Cisco Unified IP Phones for phone service in conjunction with the Cisco Unified Communications Manager or for Cisco Unified Communications Manager Express.

For more information, see the "Using Cisco Unified IP Phones with Cisco IPICS" section on page 3-21. For detailed information, refer to the "Setting Up and Using a Cisco Unified IP Phone as a Cisco IPICS Push-To-Talk Device" appendix in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Create and manage policies

You create and manage policies by using the policy engine. Policies comprise one or more actions, which are discrete functions that perform when the policy executes, such as starting a VTG and inviting designated users to join the VTG. Some policies can also include one or more triggers , which cause the policy to execute automatically and, optionally, to repeat according to a specified schedule. You perform policy engine tasks by accessing the Policy Management drawer in the Policy Engine tab.

For more information, see the "Managing and Using the Cisco IPICS Policy Engine" section on page 3-8. For detailed information about the policy engine, refer to "Using the Cisco IPICS Policy Engine" in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Manage the dial engine

The Cisco IPICS dial engine enables the TUI and its associated features. You use the dial engine to manage system and custom script prompts that the TUI uses to handle incoming and outgoing calls, and configure the Cisco Unified Communications Manager or a Cisco router that is running a supported version of Cisco IOS as the SIP provider for use with the policy engine. You perform dial engine tasks by accessing the Dial Engine drawer in the Policy Engine tab.

For more information about the dial engine, see the "Managing and Using the Cisco IPICS Policy Engine" section on page 3-8. For detailed information, refer to "Configuring and Managing the Cisco IPICS Policy Engine" in the Cisco IPICS Server Administration Guide, Release 2.1(1).


Ops View Administrator Tasks

The ops view administrator can download and monitor the Cisco IPICS activity logs for the ops view to which the user belongs. This user can also specify which activity types Cisco IPICS should log, per the ops view of the user.

You perform the tasks that relate to activity logs in the Activity Log Management and Activity Log Options windows. You can access these windows from the Administration drawer in the Administration Console.

Refer to the Cisco IPICS Server Administration Guide, Release 2.1(1) for more detailed information about the specific tasks that users can perform depending on their Cisco IPICS roles.

Operator Tasks

The operator performs the following tasks:

Sets up users and user roles—The operator adds users and manages general user information, including user name, login credentials, and the default location of users. Operators can also manage the PMC attributes for users, assign channels, roles, and ops views, associate users with other users, phones, radios, and policies, and perform activities that relate to managing user spoken name prompts.

Sets up user groups—User groups are logical groupings of users. In addition to creating and deleting user groups, operators can add members to a user group, manage ops views for a user group, and view information about VTGs in which a user group is a participant.

Operators can perform operator activities by navigating to the User Management > Users and User Management > User Groups windows. Users who are assigned the operator role can also access the dial engine windows.

For detailed information about the Cisco IPICS operator tasks, refer to "Performing Cisco IPICS Operator Tasks" in the Cisco IPICS Server Administration Guide, Release 2.1(1).

Dispatcher Tasks

The dispatcher performs the following tasks:

Sets up and activates VTGs—The dispatcher creates VTGs and activates them to begin conferences, add participants to inactive and active VTGs, monitor active VTGs, notify participants about active VTGs, and mute and unmute PMC users. VTG management tasks are performed in the VTG Management > Virtual Talk Groups window in the Administration Console. See the "Understanding VTGs" section for more information about VTGs.

Manages policies—The dispatcher can view policies of users who belong to the same ops view as the dispatcher. Policy management can be performed by accessing the Policy Management windows in the Policy Engine tab. See the "Managing and Using the Cisco IPICS Policy Engine" section on page 3-8 for more information about policies. For more detailed information, refer to "Performing Cisco IPICS Dispatcher Tasks" in the Cisco IPICS Server Administration Guide, Release 2.1(1).

User Tasks

A user can perform the following tasks:

Manage User Profile—Each Cisco IPICS user is assigned the user role. Users can manage personal information by using the My Profile window in Cisco IPICS. The user profile includes information such as user name, password, default location, communication preferences, and other personal information.

View Associations—Users view the channels, users, phones, VTGs, and policies with which they are associated in the My Associations window.

Download the PMC—Users download the PMC installer to their client machines and install the most current version of the PMC, as configured in the server, in the Download PMC window.

Users can access the user windows from the Home drawer in the Administration Console. For more information about user tasks, refer to "Performing Cisco IPICS User Tasks" in the Cisco IPICS Server Administration Guide, Release 2.1(1).