The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Plugins are used to open network ports and allow the runtime environment to communicate with devices on the network. This chapter includes these topics:
•Cisco Unified Application Environment Plugins
•Enabling or Disabling a Plugin
The following plugins ship with the Cisco Unified Application Environment.
The Cisco DeviceListX Provider communicates with Cisco Unified Communications Manager to retrieve and cache real-time device information for application use. The Cisco DeviceListX (3.X, 4.X) Provider and SNMP (5.X, 6X) protocols are used to gather this information. Table 6-1 lists the provider parameters.
The Cisco DeviceListX Provider supports the following extension, which you can invoke on the Cisco DeviceListX Provider page:
Metreos.Providers.CiscoDeviceListX.Refresh—Forces the application server to reinitialize the real-time cache. This is recommended if phone device IP addresses have been changed during high usage of an application that uses the Cisco DeviceListX Provider.
The H.323 provider can make and receive H.323 phone calls with call processing nodes within a Cisco Unified Communications Manager cluster. To use the H.323 provider, there must be an H.323 gateway configured on the Cisco Unified Application Environment that points to the IP address of the Cisco Unified Communications Manager. Table 6-2 lists the provider parameters.
The HTTP provider receives HTTP requests over port 8000. These requests are then routed to the appropriate application for processing. Table 6-3 lists the provider parameters.
|
|
---|---|
Log Level |
Filters all debug output below the specified level |
Session Expiration Minutes |
Number of minutes before HTTP sessions expire |
The Java Telephony API (JTAPI) provider abstracts the protocol details of JTAPI calls. JTAPI provider provides the functionality to handle first-party JTAPI call control and third-party JTAPI call control. The provider supports CTI ports, CTI route points and monitored devices. The JTAPI provider communicates with multiple JTAPI services belonging to different Cisco Unified Communications Manager versions. Table 6-4 lists the provider parameters.
The Media Engine provider manages Cisco Unified Media Engines for providing media capabilities to applications. Table 6-5 lists the provider parameters.
The Media Engine provider supports these extensions:
Note You should invoke these extensions only under the direction of a Cisco technical support engineer.
•Metreos.MediaControl.RefreshMediaServers—Forces the application server to reinitialize control of the media engines.
•Metreos.MediaControl.ClearMRGCache—Forces the application server to reinitialize the media engine's internal storage.
•Metreos.MediaControl.PrintServerTable—Forces the application server to write a summary of all configured media engines to the application server log.
•Metreos.MediaControl.PrintDiags—Forces the application server to write diagnostic information about currently connected media engines to the application server log.
The Presence provider uses SIP and SIMPLE (SIP for Instant Messaging and Presence Leveraging Extensions) to communicate with outside systems that support these protocols. This allows applications to receive notification of presence changes in real-time for a user or a group of users. Table 6-6 lists the provider parameters.
Note While the Presence provider can interface with any SIP- or SIMPLE-capable application, the provider has only been tested with and supported on Cisco Unified Presence, Release 6.0.
The Presence provider supports these extensions:
•Metreos.Providers.Presence.PrintSubscriptions
•Metreos.Providers.Presence.ClearSubscriptions
The SCCP provider uses the SCCP protocol to create, receive, and control IP telephony calls. The SCCP provider registers as an SCCP 7960 device in Cisco Unified Communications Manager. Table 6-7 lists the basic SCCP parameters.
Note The table below does not list the advanced parameters. They should be allowed to default.
The SIP provider uses the SIP protocol to create, receive, and control IP telephony calls between Cisco Unified Communications Manager nodes. The SIP provider either behaves as a SIP trunk or registers as SIP 7961G-GE devices in Cisco Unified Communications Manager. Table 6-8 lists the provider parameters.
The Timer provider makes timers available for use by applications. It does not communicate with any other system. Table 6-9 lists the provider parameters.
To view the list of plugins, follow these steps:
Procedure
Step 1 Log in to the Cisco Unified Application Environment Administration.
Step 2 Choose Plugins > List Plugins. The List Plugins page displays as described in Table 6-10.
|
|
---|---|
Name |
Plugin name |
Description |
Plugin description |
Version |
Plugin version |
Status |
Plugin status |
To install a plugin, follow these steps:
Procedure
Step 1 Log in to the Cisco Unified Application Environment Administration.
Step 2 Choose Plugins > List Plugins. The List Plugins page appears.
Step 3 Under Install a Plugin, click Browse...
Step 4 Highlight the file you want to upload (with a .dll extension), then click Open.
Step 5 Click Upload.
To enable or disable a plugin, follow these steps:
Procedure
Step 1 Log in to the Cisco Unified Application Environment Administration.
Step 2 Choose Plugins > List Plugins. The List Plugins page appears.
Step 3 Select the check box next to the plugin name.
•To enable the plugin, click Enable.
•To disable the plugin, click Disable.
To uninstall a plugin, follow these steps:
Note Before you uninstall a plugin, you must disable it and stop the application service. See Enabling or Disabling a Plugin and Managing Services, page 8-3 for more information. Remember to restart the application service after you uninstall the plugin.
Procedure
Step 1 Log in to the Cisco Unified Application Environment Administration.
Step 2 Choose Plugins > List Plugins. The List Plugins page appears.
Step 3 Select the check box next to the plugin name, then click Uninstall.
To modify or apply configurations to a plugin, follow these steps:
Procedure
Step 1 Log in to the Cisco Unified Application Environment Administration.
Step 2 Choose Plugins > List Plugins. The List Plugins page appears.
Step 3 Select the plugin name. The Provider page appears.
Step 4 Enter or change values as needed, then click Apply.
For information about the plugins that ship with the Cisco Unified Application Environment, see Cisco Unified Application Environment Plugins.
Step 5 Click Done to return to the List Plugins page.
To invoke a an extension, follow these steps:
Procedure
Step 1 Log in to the Cisco Unified Application Environment Administration.
Step 2 Choose Plugins > List Plugins. The List Plugins page appears.
Step 3 Select the plugin name. The Provider page appears.
Step 4 Under Extensions, locate the extension you want to invoke, then click Invoke Extension.
Step 5 Click Done to return to the List Plugins page.