PAGE TITLEDate Last Modified
PAGE TITLEDate Last Modified
The Cisco built-in bridge (BIB) is a functionality for monitoring and recording available with Cisco's Unified Call Manager (UCM) version 6.0 and higher. This call recording method does not require a mirror or span port on the network switch for network sniffing. BIB (built-in bridge) functionality is available on some of the Cisco's 3rd generation VoIP Phones (Phone 7911G, 7931G, 7941G, 7941G-GE, 7961G, 7961G-GE, 7970G, and 7971G-GE models) and supported by Cisco's UCM version 6.0 and higher. To describe the process in few words:
Refer to CUCM recording and monitoring reference for more information about this type of the call recording (e.g. Cisco BIB Reference )
Step 1. Create and configure SIP trunk that points to recorder
Select System / Security Profile / SIP Trunk Security Profile menu item. Click on the Add New button
Select Device / Trunk menu item. Click on the Add New button
In SIP information view
Step 2. disable unsupported codecs
Step 3. Create and configure recording profile
Step 4 Configure call routing
Step 5. Configure transcoder resources (if needed)
Step 6. Configure a recording notification tone
BIB does not provide call direction or Calling Party Name to the recorder with signaling.
To get this information and apply to recordings, JTAPI integration is recommended, see JTAPI CTI link configuration
Cause: built-in bridge used for recording in Cisco phones has a limitation. When the phone starts a recording session using a certain codec, it gets "locked" into that codec.
During recording, an action that would otherwise require a simple codec change will instead request a transcoder from UCM. If a transcoder can not be provided, the action will fail. Therefore if your UCM network is properly configured for transcoding between regions, this will not be a problem.
Solution: Configure UCM to:
VSLogger supports following Cisco supported voice codecs (G.711, G.722, G.729). iLBC and iSAC not supported. It is recommended to disable codecs, which are not supported by VSLogger Recording System and/or you do no have transcoder support.
JTAPI connector is part of the Adutante server functionality, which allows collecting Call information and signaling events from configured JTAI providers.
Currently following JTAPI interfaces/providers supported and tested:
To enable CTI Service
Step 1 - Navigate to User Management / Application User / Add New menu item.
Step 2 - Create a user account for CTI link. Fill out all necessary fields and make a note of the User ID and Password fields, because you will have to set them in the Adutante CTI Module
Step 3 - Add from "Available Devices" list to "Controlled Devices" all recorded devices.
Step 4 - Navigate to User Management / User Group menu item.
Step 5 - Put the user to the following groups by selecting this group from the list, then clicking Add Application Users to Group and selecting our CTI user:
Step 6 - Apply settings
Step 1 Log in to the computer where you want to install the Cisco JTAPI client software (The same PC where Adutante server is installed).
Step 2 Close all Windows programs.
Step 3 Open a web browser.
Step 4 Go to the Cisco CallManager administration windows:
where: Name specifies the name or IP address of the Cisco CallManager
Step 5 Choose Application > Install Plugins.
Step 6 Choose the 32 Cisco JTAPI Client for Windows link.
Step 7 Save the file on your desktop.
Step 8 Follow the instructions in the popup windows.
Attention!!! After installation
copy jtapi.jar (Default location: C:\Windows\Java\lib) to C:\Adutante\applications\adutante\lib\external\
copy jtapi.ini (Default location: C:\Windows\Java\lib) to C:\Adutante\
To enable jtapi cti link on Adutante open cti.properties file (C:\Adutante\applications\adutante\config\) with notepad.exe and add following parameters:
// jtapi settings
// Cisco JTAPI
cti.jtapi.cisco.cucm=x.x.x.x(,[x.x.x.x]) // ip address of CUCM(s)
cti.jtapi.cisco.user=cti // CTI Application user
cti.jtapi.cisco.password=cti // CTI Application password
cti.jtapi.cisco.dn = 1000,1001,.... // monitoring/controlling extensions (DNs) , add list of recorded extensions (comma separated)
cti.jtapi.cisco.providerId =10010 // subscriber ID for JTAPI events (vslogger provider id, see Adutante/Administration/PRecordings/Providers )
Save and restart Adutante service