Configuring Cisco MediaSense for Verba integration
- Kiss, Mate
In order to take advantage of Cisco MediaSense and Verba integration, the configuration of the Cisco Unified Communication Manager and the recorded devices is required.
We recommend that you keep this page open while you are configuring Cisco UCM and open each step in a new window.
Cisco UCM configuration
The initial Cisco UCM configuration includes the following steps:
Step 1 - Activate and start Cisco AXL web service. MediaSense uses AXL for administration and configuration tasks
Step 2 - Create or modify an application super user to grant AXL access permission. Application user should have Standard CCM Super Users group rights
Step 3 - Create Media Sense API user (standard End user, no special rights required), Verba is going to use the user to connect MediaSense
Step 4 - Create and configure the SIP trunk pointing to the MediaSense server(s). Default listening port is 5060, SIP over TLS, and encrypted call recording is not supported currently by Media Sense.
Step 5 - Create a recording profile used by the recorded lines / extensions
Step 6 - Configure call routing that let the Cisco UCM to direct calls to the MediaSense cluster
Step 7 - Create an application user for the JTAPI connection that provides recording control and detailed CDR information. Verba is extending available CDR information for real-time calls via JTAPI
Step 8 - Disable the unsupported iSAC and G.722 codec if you use devices supporting iSAC (89xx, 99xx family) or G.722 (only applicable above CUCM 8.5(1)SU1)
Step 9 - Verify if transcoding is required and available (recommended)
Step 10 - Configure a recording notification tone (optional)
Cisco MediaSense configuration
The inital Cisco MediaSense configuration includes the following steps:
Step 1 - In the configuration wizard or Administration/Unified CM configuration menu provide the AXL service provider. It should be the primary node in your CUCM cluster, and user should be an application super user having AXL API access role
Step 2 - In the configuration wizard or Administration/MediaSense API user configuration menu add the end user to be used for API access
Step 3 - In the configuration wizard or Administration/Prune policy menu configure the desired data pruning policy
After these steps you can start adding extensions.
The codec configuration in UCM is important for recording, since Cisco phones do not support codec changes of the secondary recording call. You might have to deploy transcoding resources to handle all scenarios, for more information read Codec guidelines for Cisco Central Recording.
Adding and removing extensions
Follow the steps below to add and remove extensions to/from central recording in Cisco UCM:
- Add new extensions to central recording (follow these steps to add extensions with Extension Mobility)
- Remove extensions from central recording
When you use RTP-forking based Cisco central recording, the system can record only those extensions that are properly configured in the Cisco UCM. It is not enough to add extensions in the Verba Recording System.