Summary of Unified Mobile Agent system configuration tasks

This section describes the configuration tasks specific to Unified Mobile Agent configuration. It does not describe Unified CCE/Unified CCH. The following table describes system configuration tasks for Unified Mobile Agent.

Note

For more information about installing and configuring Unified CCE/Unified CCH, see the Installation and Configuration Guide for Cisco Unified Contact Center Enterprise & Hosted.

This section describes the CTI Port Pool configuration tasks specific to Mobile Agent Option configuration. It does not discuss installation or configuration of Unified CCE.

Note

For more information about installing and configuring Unified CM with Unified CCE, see Installation and Configuration Guide for Cisco Unified Contact Center Enterprise & Hosted.

Unified Mobile Agent needs two CTI ports configured on Unified CM:

A local CTI port, which Unified Mobile Agent uses as the agent's virtual extension

A remote CTI port, which Unified Mobile Agent uses to initiate a call to the Mobile Agent's phone

Naming Conventions for Local and Network Ports

The local port must begin with the string LCP.

The remote port must begin with the string RCP.

Although not required, for best practices, use the following naming convention:

For a local CTI Port pool name, configure a name in the format LCPxxxxFyyyy, where LCP identifies a local CTI Port Pool, xxxx is the peripheral ID for the Unified CM PIM, and yyyy is the number of local CTI Port. Example: LCP5000F0000 represents CTI Port: 0 in a local CTI Port pool for the Unified CM PIM with the peripheral ID 5000.

For a network CTI Port pool name, use the same format, except substitute RCP as the first three characters.

Note

While you do not require a naming convention, the substrings identifying the Unified CM PIM peripheral ID and the CTI Port must match for each local/network pair.

CTI Port configuration consists of the following steps:

Add the CTI port as you would for an IP Phone.

Use the naming convention described above to map the local and network CTI ports.

Note

Each local CTI port must have a corresponding network CTI port.

Add a directory number for the local CTI port (that is, the agent's virtual extension).

Music on Hold Design

If a caller must hear music when a Mobile Agent places the caller on hold, you must assign Music on Hold (MoH) resources to the ingress voice gateway or trunk that is connected to the caller (as you do with traditional agents). In this case, the user or network audio source is specified on the local CTI port configuration. Similarly, if a Mobile Agent must hear music when the agent is put on hold, you must assign MoH resources to the ingress voice gateway or trunk that is connected to the Mobile Agent. In this case, the user or network audio source is specified on the remote CTI port configuration.

Note

Cisco recommends that you do not assign MoH resources to local ports and remote CTI ports, as it might affect the system performance. If you have Agent Greeting for Mobile Agents, Cisco strongly recommends that you do not assign MoH resources to local and remote CTI ports.

If a remote Mobile Agent calls over a nailed connection and if there is no active call to the agent, the agent is put on hold. In general, Cisco recommends enabling MoH to the Mobile Agent phone for nailed connection calls. If MoH resources are an issue, consider multicast MoH services.

If a remote Mobile Agent calls over a nailed connection, and if MoH is disabled, the hold tone plays to the agent phone during the hold time. This depends on the call processing agent that controls the Mobile Agent remote phone. For Unified CM, the hold tone is enabled by default (it is similar to the Mobile Agent connect tone). With the hold tone enabled, it is difficult for the agent to identify if a call arrived from listening to the Mobile Agent connect tone. Therefore, Cisco recommends that you disable the hold tone for Unified CM. To do this, change the setting of the Tone on Hold Timer service parameter. For more information about setting this parameter, see the Unified CM product documentation available at: http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html.

Configure Unified CM CTI Port Pools for Unified Mobile Agent

Perform the following steps to configure CTI Ports.

Procedure

Step 1

In Unified CM Administration, select Device > Phone.

Step 2

Click Add a New Phone.

Step 3

From Phone Type, select CTI Port.

Step 4

Click Next.

Step 5

In Device Name, enter a unique name for the local CTI Port pool name; click OK when finished.

Using the example naming convention format LCPxxxxFyyyy:

LCP identifies the CTI Port as a local device.

xxxx is the peripheral ID for the Unified CM PIM.

yyyy is the local CTI Port.

The name LCP5000F0000 would represent CTI Port: 0 in a local CTI Port pool for the Unified CM PIM with the peripheral ID 5000.

Step 6

In Description, enter text identifying the local CTI Port pool.

Step 7

Use the Device Pool drop-down list to choose the device pool to which you want to assign the network CTI Port pool. (The device pool defines sets of common characteristics for devices.)

The name RCP5000F0000 represents CTI Port: 0 in a network CTI Port pool for the Unified CM PIM with the peripheral ID 5000.

Step 15

In Description, enter text identifying the network CTI Port pool.

Step 16

Use the Device Pool drop-down list to choose the device pool to which you want to assign the network CTI Port pool. (The device pool defines sets of common characteristics for devices.)

Step 17

Click Save.

Step 18

Highlight a record and select Add a New DN.

Step 19

Add a unique directory number for the CTI port you just created.

Step 20

When finished, click Save, and click Close.

Map local and remote CTI ports with PG user

After you define the CTI Port pool, you must associate the CTI Ports with PG users.

Procedure

Step 1

In Unified CM Administration, select Application User.

Step 2

Select a username and associate ports with it.

Step 3

When finished, click Save, and then click Close.

Note

If CTI ports for Unified Mobile Agent are disassociated at the Unified CM while a Mobile Agent is on an active call, the call can drop.

Maximum Call Duration Timer configuration

By default, Mobile Agents in nailed connection mode log out after 12 hours. This happens because a Unified CM Service Parameter—the Maximum Call Duration Timer—determines the amount of time an agent phone can remain in the Connected state after login.

If you anticipate that nailed connection agents in your Unified Mobile Agent deployment will be logged on longer than 12 hours, use the following instructions to either:

Configure Maximum Call Duration Timer

Note

This procedure applies only to Unified Mobile Agent deployments where agents logged in to nailed connection mode are to remain connected longer than 12 hours. Also, if your Mobile Agent deployment uses intercluster trunks, you must perform the following steps on both local and network Unified CM clusters.

Device target configuration for Unified Mobile Agent

Unified CCE systems require that you configure a device target for each IP telephone that might be used by an agent. The only difference between configuring a device target for a local agent and a remote agent is that Unified Mobile Agent uses the agent's local CTI port instead of the agent's extension.

Name. An enterprise name for the target. This name must be unique among all device targets in the enterprise.

Global Address. The global address for the device. Must be set to a value that is unique from all other device targets in the enterprise. Cisco recommends that you use the same value that you entered in the Enterprise Name field.

Config Parameters. Use this field to enter any specific configuration parameters that might be required:

/devtype (CiscoPhone)

/dn (Line number of the LCP port)

The system software sends this string to the Unified CM to initialize the device.

Description. Enter a description of the device. This is an optional field used to provide additional information about the device.

CTI OS installation and Unified Mobile Agent

Note

Running the CTI OS 7.x server installer is not the same as running CTI OS 7.x installer from the CTI OS bin directory.

To configure Mobile Agent, first run the CTI OS 7.x server installer. Then run the CTI OS installer from the CTI OS bin directory. The first installer updates CTI OS server while the second installer allows you to configure Mobile Agent. Use this procedure to configure any new feature made available in a maintenance release.

During the peripheral identification step of CTI OS Server installation:

Call delivery mode and agent profiles

The call delivery mode selected during CTI OS Server installation enables CTI OS to send an agent profile to each desktop client for that mode.

The call delivery mode the agent uses at login must match the mode configured for the agent in the Agent Desk Setting.

Rerunning the CTI OS installation and selecting a different Mobile Agent mode overwrites the existing profile.

You can add profiles manually using the CTI OS registry.

Prevent Duplicate logins to the Same AgentID

In the default Installation, the CTI OS system does not prevent duplicate logins. If you want to change the default, you must make the following change in the Windows Registry for the key RejectIfAlreadyLoggedIn.

Media termination points configuration

If you use SIP trunks, you must configure Media Termination Points (MTPs). This also applies if you use TDM trunks to interface with service providers.

MTPs are available in the following forms, but not all are supported in Mobile Agent environments:

Software-based MTPs in Cisco IOS gateways—It is recommended that you use these MTPs for Mobile Agent as they provide codec flexibility and better scalability compared to other MTP options. The following is a sample configuration on a gateway.

Because Unified CM-based software MTPs are used implicitly, you must add a special configuration to avoid using them. Create a new Media Resource Group (MRG) as a place holder, and place the software MTPs in that MRG.

Configure Media Termination Points

If you use SIP trunks, you must configure MTPs. This also applies if you use TDM trunks to interact with service providers.

Mobile Agent cannot use an MTP with codec pass through. When you configure the MTP, you must select No pass through.

KPML is not supported with Mobile Agent.

Procedure

Option

Description

If you want to always insert MTPs for inbound and outbound calls through a given trunk

In the Trunk Group Configuration settings, select the Media Termination Point Required check box.

If you want to dynamically insert MTPs when Unified ICM detects media or signaling incompatibility between the caller and called endpoints

In the Trunk Group Configuration settings, in DTMF Signaling Mode, select RFC2833.

If you configure Trunk Groups to dynamically insert MTPs, only the calls that require MTPs use them.

Enable Call Progress Tones for Agent Initiated Calls

In order for an agent to hear call progress tones for agent initiated calls, additional configuration is required if MTP Required is not enabled. If instead you have dynamic MTP allocation by forcing mismatched DTMF settings, then the Unified CM should be configured to enable Early Offer.

Ringback and other call progress tones are not generated by the Cisco Announciator, as is the case for regular phones and softphones. Instead, Mobile Agent relies on these tones being generated by the called party (and the early offer setting triggers these tones to be sent to the agent).

Enabled Connect Tone feature

In a nailed connection, the system can play a tone to the Mobile Agent via the agent's headset to let the agent know when a new call is connected. In the default Installation, the Mobile Agent Connect Tone feature is disabled.

Enable Mobile Agent Connect Tone

If you require Unified Mobile Agent Connect Tone, you must make the following change in the Windows Registry for the key PlayMAConnectTone under the JTAPI GW PG registry entries.

Perform the following procedure to allow a Mobile Agent in the nailed connection mode to hear a tone when a new call is connected.