Nov 05

Cisco Mediasense 11.5(1) – Role Based Access for Finesse Agents

Mediasense 11.5(1) has introduced the long awaited role based access for Finesse Agent and Supervisors. Finesse Supervisors can monitor the recordings of only their assigned Teams, while Finesse Agents can only view their own recordings. Recordings include active recordings, associated recordings and archived recordings.

For the above to work, the Finesse AgentInfo gadget is required to be active for both Agents and Supervisors. This feature only applies to Finesse Integrated Contact Centres.

To reference additional 11.5(1) features for Mediasense, please use the below link.

May 04

Finesse Call Recording with Cisco Medisense 11

I’ll be going through the process to configure Call Recording using Cisco Mediasense with the UCCX Finesse Agent. The Mediasense Server itself requires a server license plus Media Port licenses, the port licenses can be either Audio Only or Audio/Video. As it stands the previously mentioned licenses are a ‘right use’ license. Cisco is trusting partners and customers to apply the correct amount of licenses for their installed instances. The Contact Centre though is different story. Additional Call Recording licenses need to be purchased as the Contact Centre product controls the call recording streams. These licenses must be uploaded to the Contact Centre server. We’ll discuss this further below.

Mediasense seems to work as expected and can record calls in a variety of ways (Phone, Gateway, CUBE) which gives flexibility to various customer requirements. The feature set however needs some more work. I found the Authorisation/Security component of Mediasense Call Recording is very basic compared to other products on the market. Hopefully Cisco is looking at RBAC for future releases.

Lets get to the configuration part, we’ll start with CUCM.

Create an End User either directly on CUCM or via Active Directory. Mediasense requires its API Users to be End Users in CUCM and not Application Users. When deploying Mediasense the initial wizard will ask for this Users details.

Cisco Call Recording

The End Use in my case ‘mediasense’ is required to have the AXL Role and be a member of the Standard CCM Admin Users group

Cisco Call RecordingCUCM communicates with the Mediasense server via a SIP Trunk, even with gateway recording it’s the CUCM Server that will send the INVITES to the Mediasense server.

So go ahead and setup the SIP Trunk configuration. We’ll start with the SIP Profile.

I always find it easier to copy the Standard SIP Profile then make any changes necessary, that way all SIP Profiles are isolated from each other making future changes easier with less impact to other SIP services.

In the Mediasense SIP Profile, I’ve enabled SIP Options. If I was to have more than one Mediasense server, this is where SIP Options would come in useful. CUCM polls each Mediasense server to determine if its down or up, and will only send INVITES to a Mediasense server in an operational state.

Cisco Call RecordingThe default SIP Trunk Security is good enough for Mediasense. The main field to take not is the Outgoing Transport Type.. This must be TCP. So worth to check this setting. If its been set to UDP, then create a new SIP Trunk Security Profile.

Cisco Call RecordingCreate a new SIP Trunk with the basic settings. Provide good descriptions and select the SIP Profile and SIP Trunk Security profile as created above. Can use either the IP Address or FQDN for the Destination. Port is SIP standard 5060.

Cisco Call RecordingCisco Call RecordingCreate a Route Pattern for the Call Recording profile to match. I’ve just selected the Mediasense_Recording SIP Trunk as the destination. You can also use Route Lists and Route Groups. Ive also placed this route pattern in the Global SYSTEM partition. You can create a new partition for Call Recording and place the pattern into this, then just allocate the Call Recording profile the CSS that has access to the specific partition.

Cisco Call RecordingCreate a Recording Profile selecting the pattern defined above in the Route Pattern step. Also select the appropriate CSS that has access to the partition the call recording pattern is in.

Cisco Call RecordingNow we jump across to the Phones. In this blog I’ll be using the Phone Preferred architecture, hence the phones will be forking media to the Mediasense server. For this to happen the phones need to have the ‘Built In Bridge’ enabled. This is also a global setting if wish to blanket all phones.

Repeat the below steps for each phone/line that will have recording enabled in the Contact Centre.

Enable the Built In Bridge. Save and Apply Config.

Cisco Call RecordingGo to the Line of the Phone (or for the Device Profile). Navigate to the Line Settings for this Device area and select the Recording Option, Recording Profile and the Recording Media Source. In my case, I’ve enabled recording with Selective Call Recording enabled. The alternate option is automatic call recording. (Always On). In this blog, I want to control the Call Recording via UCCX Workflows.

Cisco Call RecordingOptional is to have a beep play to let the call party’s know the conversation is being recorded. Default is set to off.

Cisco Call RecordingAlso optional is to assign a Call Recording Softkey to the phone or device profile. If pressed during a conversation, the CUCM actions to the call recording and not UCCX/Finesse.

Cisco Call RecordingMediasense Configuration

The install for Mediasense is fairly straight forward. After deploying the correct OVA for your environment size and going through the initial CLI configuration wizard configuring IP Address details, DNS Servers etc Its time to browse to the Web GUI.

Log into the Web GUI using the user credentials configured in the CLI wizard. The first couple of screens are more or less notifications and information about mediasense. Click next through these.

Cisco Call RecordingCisco Call RecordingThe AXL Service Provider is the End User created during the CUCM configuration phase. The AXL provide IP Address is of course your CUCM Server (ensure you have the AXL Service activated)

Cisco Call RecordingThe Mediasense will discover all the Call processing Servers in the environment. Funny enough, it also discovers the Presence Servers?

Cisco Call RecordingClick next through the summary page and you will end up at the Administration Console of the Mediasense server.

Cisco Call Recording

Cisco Call RecordingNavigate to the Cisco Finesse Configuration window and enter the UCCX Servers is the appropriate field. Ensure to FQDN for the UCCX Servers.

Cisco Call RecordingNavigate to the Mediasense API User Configuration window and search for the End User created in the CUCM phase. In my case its mediasense. Add the End User to the Mediasense API Users. Also, from the screen, add the users in that shall have GUI access to the search and play browser.

Cisco Call RecordingUCCX Configuration

Start by uploading the Call Recording Count Licenses for CCX. **NOTE Part Number required is “INCREMENT CRS_REC_PORT”

After uploading the licenses, the License Display Screen should look similar to the below.

Cisco Call Recording

Add the Mediasense Recording Server and API User to the CCX Server. This user was added to the Mediasense API User list in the Mediasense configuration phase.

Cisco Call Recording

UCCX Script

Now seeing that I’m going a step further with this configuration due to the customer requirements. I’ll add it all in for you to see. In this particular case the customer required to have an ‘opt-out’ menu for call recording. Hence the caller could select IVR Option ’9′ and essentially opt-out of call recording. For this to happen, we need to first create some script variables. I created a variable called ‘Do_Not_Record’ with a value of ‘Do Not Record’ and linked this String to Call Variable 5. I could’ve created an ECC Variable, however, Im working with UCCX 10.6 at the moment.. And there is a current bug preventing ECC Variables from being used in the Finesse Workflow filters.

I have also create a script variable called ‘Record_Call’ with a value of ‘Record Call’ and linked to Call Variable 2.

See below for Call Variable image along with script insertion.

Cisco Call RecordingCisco Call RecordingFinesse Administration

We need to now create a workflow and utilise the variables created in the previous step. First step is to create a workflow action. See below for the workflow action created, this follows the standard procedure for invoking Mediasense.

Cisco Call RecordingWe then need to create a Workflow filter or match condition. I’ve created a filter or match condition for Call Variable 2 (value = Record Call).

Hence the match condition is when the ‘Record Call’ is presented via Call Variable 2. Relating this to the above script, is when a caller does not press IVR option ’9′ to opt-out, the value ‘Record Call’ is inserted into Call Variable 2.

Add the workflow action and click SAVE.

Cisco Call RecordingNo we can add the Workflow to a Team. Navigate to the Team configuration page and select the appropriate team. Now click the Workflow menu (lower right).

Click the Add button and browse or select the Workflow required.

Cisco Call RecordingAlso worth mentioning is the MS AgentInfo gadget. This gadget inserts/passes metadata to the Mediasense engine. I’ve given two examples below, the first example is a call recording without the AgentInfo gadget, and the second example being with the MS AgentInfo gadget.

To apply the MS AgentInfo gadget, navigate to the Desktop layout configuration page (either Global or Team based). Add the below lines to the Agent Desktop layout. Agents then need to log out of Finesse then back in.

Cisco Call Recording

Cisco Call RecordingNOTE: Mediasense Play Back requires Java 1.7+.

Without the MS AgentInfo Gadget deployed in Finesse

Cisco Call RecordingWith the MS AgentInfo Gadget deployed in Finesse

Cisco Call RecordingOPTIONAL: Unhide the Mediasense gadget for the Supervisor to allow the Supervisor to search and play call recordngs from the Finesse Agent window.

Cisco Call Recording

Apr 15

UCCX – Agents Stuck in Reserved State

UCCX Agents being stuck in a Reserved can be quite frustrating to both the customer and the Agent. An Agent is placed into a Reserved state when the UCCX Engine essentially reserves a inbound call to an Agent. Now that the Agent and the Inbound call are a ‘pair’ the system will try and push the call to the Agents phone.

To allow a customer to be pushed to an Agent immediately, the queue announcements, menu’s or timers must have the radio button “Interruptible” set to Yes. If this is set to No, the Customer will be forced to wait for the current announcement, menu prompt or timer to expire before being be connected with an Agent, this includes MoH.

Screen images or where you can find this parameter in the UCCX Script.


Jan 30


Agent receives the below error message while attempting to log into Finesse Agent. Agent has been configured to use an 8851 IP Phone. Same Agent can log onto the Finesse Agent using 7945/75 IP Phones.


The Remote Agent User requires CTI Access to the Agents phone. With the new 8851 IP Phone two extra user roles are required (same as the 9971 IP Phone) The roles required are: “Standard CTI Allow Control of Phones supporting Connect xfer and conf” and the “Standard CTI Allow Control of Phones supporting Rollover mode”

Sep 20

UCCX – Login Failed Due to Configuration Error

UCCX Agent receives the below error ” Login failed due to a configuration error with your phone and JTAPI or Unified CM. Contact your Administrator” when logging into UCCX.


All CUCM and UCCX configuration looks to be correct, the user was successfully logged into CAD the day before. The Agents phone is currently logged in and registered.

Collect the MIVR Logs using RTMT. To do this open RTMT Tool against the UCCX Server and Select Traces and Alerts. Then select Collect Traces. Select the ‘CCX Engine’ for the log type and ‘All UCCX Server’. Click Next twice and select an appropriate location to download the logs too.

Unzip the .gz log files using 7zip application. Then open the MIVR Logs using Notepad++. Search for the Agent’s username. You should see similar output to the below. (username is bdodd)




This is caused by an Agent moving between phones. The DEVICE NAME is the above trace output is not the phone the Agent is logged onto today. The CTI or JTAPI caches the Device the Agent successfully logged onto last. If the Agent is an Extension Mobility user, its best to only add the Device Profile to the RMCM Application User’s CTI Controlled Device list.

To Resolve:

Remove the old device from the RMCM Application user. You may also have to resync JTAPI in UCCX and restart the CTI Manager to force the change if the problem continues.

Aug 15

UCCX – Finesse Monitoring / Barge Features

Just like the CAD Agent Desktop software the Finesse Agent allows the Supervisor to silent monitor Agents in their Team. The audio though flows through the IP Phone and not the computer. From a silent monitor session, the Supervisor can then Barge into the call between the Agent and the Customer. The Agent will hear a beep to let them know the Supervisor has Barged in. The Customer will not hear the beep.

Barge is essentially a three way conference. From a Barge session, the Supervisor can then intercept the call and drop the Agent from the call. Therefore the Customer is now talking directly to the Supervisor, this is great for call escalation.

A couple to things to note about the setup.

- Built-in Bridge must be enabled on Agent Phones
- Supervisor DN must have the Monitor CSS populated with a CSS that has access to the Agents DN.
- For a Supervisor to Silent Monitor an Agent, the Supervisor must be in a Not Ready State. If the Supervisor is in a Ready State, the Silent Monitor will be greyed out.