Adutante
  • Infoshare
    • Infoshare
    • AduCRM
    • Recordings
    • Users
    • AduCRM
  • Signed in: Administrator
    • Change Password
    • Signoff
    • Online Documentation
    • Adutante ver. 5.0.1.0
  • Language
    • English
    • Spanish

PAGE TITLE

Date Last Modified
infoshare.htm
Infostore
    • Content
    • Test Groups
    • Comments
    • Revisions
  • Content
  • Comments
  • Test Groups
  • SSU
  • Attachments
  • Tools
  • Tags
  • Edit
  • English - About VSLogger Call Recording
    • Quick Guides
      • Quick Guide - Recorder system
      • Quick Guide - Backup and Archiving
      • Quick Guide - Call Recording kit installation
      • Quick Guide - Restore or Migration
      • Quick Guide - Upgrading
      • Quick Guide - User Interface
    • Adutante Server
      • General Administration
        • Guest Tab
        • Modules Tab
        • Tools Tab
        • Users Tab
      • Adutante - QC Modules
        • Evaluate Tab
        • Evaluation History Tab
        • QC Admin Module - Permissions Tab
        • QC Forms Tab
        • QC Reports Tab
        • Review Tab
      • Adutante - Recorders Modules
        • Call Center Seating Tab
        • Recorders Admin - Call Center Tab
        • Recorders Admin - Module Permissions Tab
        • Recorders Admin - Recorder Permissions Tab
        • Recorders Admin - Recorders Tab
        • Recorders Tab
        • Recordings Tab - Obsolete
      • How to Add VSLogger to Adutante
    • Tips, Best Practices, Troubleshooting
      • Authentication and Active directory Integration
      • About Screen Capture
      • Adutante vs. VSLogger
      • Frequently Asked Questions (FAQ)
      • Known Issues
      • Languages and Translations
      • SSL Certificates
      • Support plan has expired and License not activated messages
      • User Functionality Configuration Samples
      • Wireshark: How to Capture VoIP Traffic
    • VSLogger Server
      • Configure Hardware and Channels
        • Analog Channels
        • Common Parameters and VOX
        • D-Channel events
        • Digital PBX Channels
        • Passive VOIP
        • Passive VOIP Channels
        • T1, E1, ISDN PRI Channels
        • Terminating IPCAST Channels
        • Terminating IPCAST(Unicast/Multcast) HW
        • Terminating VOIP Channels
        • Terminating VOIP HW
        • VOIP Trunk Channels
        • Verification Channels
        • Virtual HW and Channels / Recordings Replication
      • VSLogger Monitor UI
        • VSLogger Monitor - Setup Tab
          • Desktop Assistant (DTA) Administration
          • Storage and Archives section
          • System/License Activation section
        • Dashboard Tab
        • Links Tab
        • Live Monitoring Tab
        • Recorder Reports Tab
        • Search and Playback Tab 4.7.1
        • Search and Playback Tab 4.7.2+
      • General Configuration
        • Adutante Registration
        • Alarms Configuration, rev. 4.9.1 and earlier
        • Alarms Configuration, rev. 4.9.2 and after
        • Connection Service / Netserver
        • Licensing Configuration
        • Logs Configuration
        • Recording Filters
        • SMDR Configuration
        • SMTP Settings
        • Storage and Archives
        • T1 E1 Signaling Schemes
        • Vaults and Encryption
      • VSLogger API
        • VSLogger Call Recording Engine
        • VSLogger HTML API
      • VSLogger CLI Tool Overview
        • DB Maintenance Utilities
        • File converter
      • Avaya TSAPI DMCC recording
      • Cisco BIB /JTAPI Configuration
      • Cisco BIB SIP/TLS SIP trunk configuration
      • Desktop Assistant
      • Hardware Drivers
      • Microsoft Teams Recording
      • Mitel SRC (Secure Recording Connector)/ Mitel OIG CTI Configuration
      • Voice Analytics features and providers
    • Supported Providers and PBX/Phone Models
  • Français (French) - A propos de VSLogger
    • Adutante Server
      • Adutante - Modules généraux
        • Administration Générale – L’Onglet Hôtes
        • Administration Générale – L’Onglet Modules
        • Administration Générale – L’Onglet Outils
        • Administration Générale – L’Onglet Utilisateurs
      • Adutante - Modules QC
        • Administration QC – L’Onglet Module des Autorisations
        • Les Formulaires QC
        • L’Anglet Examen
        • L’Onglet d’Evaluation QC
        • L’anglet Rapports
        • L’historique de l’évaluation
      • Adutante - Enregistreurs Modules
        • Admin. Enregistreurs | L’Onglet Enregistreurs
        • Admin. Enregistreurs | L’Onglet du Centre d’Appels
        • Admin. Enregistreurs | Onglet Autorisations Enregistreur
        • Admin. Enregistreurs | Onglet des Autorisations Module
        • L’Onglet des Enregistrements - Obsolète
        • L’Onglet des Enregistreurs
        • L’onglet Siège
      • Comment ajouter ou supprimer un Enregistreur
    • VSLogger Server
      • À propos de l'outil CLI de VSLogger
        • DB Maintenance Utilities
        • À propos du convertisseur de fichiers
      • config hw | Matériel
        • Virtual HW et canaux. Réplication d'enregistrements.
        • config channel | Paramètres communs
        • config channel | Canaux de ligne tronc SIP
        • config channel | Configuration de canal T1/E1/ISDN PRI
        • config channel | Configuration de canal analogique
        • config channel | La Configuration du canal PBX numérique
        • config channel | La Configuration du canal de VOIP Passif
        • config channel | Les Evènements D-Channel
        • config channel | Terminant(active) les canaux VOIP
        • config channel | canaux de Vérification
        • config hw siprec | VoIP (terminant) active
        • config hw voip | VOIP Passive
      • config general | Configuration générale
        • config adutante | Inscription avec Adutante
        • config alarms | Configuration des alarmes
        • config filters | Filtres d'enregistrement
        • config license | Configuration des licences
        • config logging | Configuration des journaux
        • config netserver | Service de connexion
        • config smdr | Configuration SMDR
        • config smtp | Paramètres SMTP
        • config storage | Stockage et archives
        • config t1e1 | Systèmes de signalisation T1 E1
      • À propos de l'API VSLogger (interface du programme d'application)
        • Moteur d'enregistrement d'appel VSLogger
        • VSLogger HTML API
      • A propos de VSLogger Monitor
        • Le Moniteur VSLogger – L’onglet de configuration
          • Administration Assistant de bureau (DTA)
          • Section Activation système et licence
          • Section Stockage et Archives
        • Le Moniteur VSLogger – L’Onglet Tableau de Bord
        • Le Moniteur VSLogger – L’Onglet de supervision en direct
        • Le Moniteur VSLogger – l’Onglet Rapports
        • Le Moniteur VSLogger- Les onglet Recherche et Lecture
        • Onglet Recherche et lecture (4.7.2+)
      • Enregistrement des téléphones Cisco BIB ( built-in-bridge)
      • Pilotes de matériel
      • Configuration du lien JTAPI
      • L’Assistant de Bureau
    • FAQ, meilleures pratiques, astuces, dépannage
      • A propos de la capture d'écran
      • Les Langues et Les Traductions
      • Les certificats SSL
      • Récapitulation de la différence entre Adultante et VSLogger
      • Utilisateur exemples de configuration de la fonctionnalité
    • Démarrage rapide - Kit de enregistrement
    • Démarrage rapide - Mise à niveau
    • Démarrage rapide - Système enregistreur
    • PBX et modèles de téléphone pris en charge par les enregistreurs d'appels Versadial
  • Español (Spanish) - Sobre VSLogger
    • Adutante Server
      • Adutante - Módulos generales
        • Administración General | Pestaña de Módulos
        • Pestaña de Herramientas
        • Pestaña de Invitado
        • Pestaña de Usuarios
      • Adutante - Módulos CC (control de calidad)
        • Formularios de Control de Calidad
        • Historial de Evaluación
        • Pestaña de Evaluación de Control de Calidad
        • Pestaña de Informes
        • Pestaña de Revisión
        • QC Admin | Pestaña de Permisos de Módulo
      • Adutante - Módulos de Grabadores
        • Admin. de Grabadores | Pestaña de Centro de Atención Telefónica
        • Admin. de Grabadores | Pestaña de Grabadores
        • Admin. de Grabadores | Pestaña de Permisos del Módulo
        • Centro de llamadas
        • Mr.
        • Pestaña de Grabaciones
        • Pestaña de Grabadores
      • Cómo agregar un Grabador al Sistema de Grabación Distribuida
    • VSLogger Server
      • Acerca de la herramienta CLI de VSLogger
        • Acerca de las Utilidades de Mantenimiento de Base de Datos
        • Acerca del convertidor de archivos
      • config hw | configurar el Hardware de VSLogger
        • Virtual HW y Canales. La replicación.
        • config channel | Canales T1, E1, ISDN PRI
        • config channel | Canales de grabación de llamadas de verificación
        • config channel | Canales de troncales SIP
        • config channel | Configuración activa del canal VOIP
        • config channel | Configuración del canal analógico
        • config channel | Configuración pasiva de canal VOIP
        • config channel | Eventos D-Canal
        • config channel | Parámetros de canal comunes a todos los tipos de canal
        • config channel |Configuración del canal digital
        • config hw siprec | Configuración activa de VOIP
        • config hw voip | Configurar la grabación VOIP pasiva
      • config general | Configuración general
        • config adutante | Adutante Registro
        • config alarms | Configuración de Alarmas
        • config filters | Configuración de los filtros de grabación
        • config license | Configuración de Licencias
        • config logging | Configuración de Registros
        • config netserver | Configuración del Servicio de Conexión
        • config smdr | Configuración SMDR
        • config smtp | Configuración de SMTP
        • config storage |Configuración de Archivos y Almacenamiento
        • config t1e1 | Configurar esquema de señalización CAS T1 o E1
      • Acerca de API VSLogger
        • Motor de grabación de llamadas VSLogger
        • VSLogger HTML API
      • Acerca del Monitor de VSLogger
        • Pestaña de Configuración
          • Administración de Asistente de escritorio (DTA)
          • Sección Almacenamiento y Archivos
          • Sección de activación de sistema y licencia
        • Pestaña de Búsqueda y Reproducción
        • Pestaña de Búsqueda y Reproducción 4.7.2+
        • Pestaña de Informes
        • Pestaña de Monitoreo en Vivo
        • Tablero
      • Acerca del hardware Controladores
      • Asistente de Escritorio de VSLogger
      • Configuración de JTAPI Enlace a la grabadora de llamadas
      • Grabación de los teléfonos Cisco BIB (built-in-bridge)
    • Preguntas, mejores prácticas, consejos, Solución de problemas
      • Acerca de la captura de pantalla
      • Adutante contra VSLogger
      • Certificados SSL
      • Idiomas y Traducciones
      • Usuario muestras de configuración Funcionalidad
    • Inicio rápido - Actualización
    • Inicio rápido - Kit de grabación
    • Inicio rápido - Sistema completo
    • PBX y modelos de teléfono compatibles con grabadoras de llamadas Versadial
  • Português (Portuguese) - Sobre a gravação de chamadas do VSLogger
    • PBX e modelos de telefone suportados por gravadores de chamadas Versadial
  • العربية (Arabic) - حول VSLogger تسجيل المكالمات
    • Versadial مقسم الهاتف ونماذج بدعم من مسجلات نداء
  • Cisco BIB Configuration
  • JTAPI Link Configuration (optional)
  • CUCM Clusters and Versadial Recorder

 

About  Cisco built-in bridge (BIB) functionality for call recordings

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:

  • A "Recording Profile" assigned to all recorded Cisco phones. 
  • Versadial recorder is configured in UCM as a SIP trunk and assigned a route pattern.
  • The "recording profile is linked to the SIP trunk using the Route Pattern in UCM.
  • When an actual agent-customer call takes place, the UCM sends the calls to the Versadial recorder for recording.

This configuration is very useful in supporting call recording for multiple sites with a centralized recording solution.Configure and Troubleshoot Basic Call Recording


Refer to CUCM recording and monitoring reference for more information about this type of the call recording (e.g. Cisco BIB Reference )


Configure VSLogger recorder for built-in bridge (BIB) recording

  1. CLI Tool used to enable voip siprec hardware    Refer to config hw siprec- Terminating VOIP   Note: Please, do not get confused with hardware term here. This is strictly software based recording. Term siprec hardware refer to configuration part responsible for defining the number of recorded channels of the specific type (similar to multi-channel voice board)
  2. Individual channels (recorded devices )  configured in the previous section, further configured in config channel - Terminating VOIP Channels

 

Configure Cisco UCM for built-in bridge (BIB) recording

Typical Configuration Steps

Step 1. Create and configure SIP trunk that points to recorder

      Navigate to  System / Security Profile / SIP Trunk Security Profile  menu item.    Click on the Add New button

Gallery: CUCM-BIB SIP trunk secure profile

  • Name  - Recorder SIP trunk security profile
  • Description  - profile used by Versadial recorders
  • Incoming Transport Type: select TCP+UDP.
  • Outgoing Transport Type: select TCP  (or match Versadial recorder settings, if different). TCP is recommended.
  • Uncheck Enable Digest Authentication - when you create the SIP Trunk Security Profile
  • Incoming Port to 5060 port  (match to settings of the Versadial recorder).
  • Make all other parameters unchecked
  • Click on the Save button.

      Navigate to Device /  Trunk menu item.  Click on the Add New button

Gallery: CUCM-BIB SIP trunk

  • Device Name  - Recorder 
  • Description  - Recorder SIP trunk
  • Device pool  default
  • Common device configuration <none
  • Call classification  <Use default>
  • Media resource group  <None>
  • Packet Capture mode  <None>
  • Packet capture duration  0
  • Retry Video Call as Audio, checked
  • Other check parameters unchecked

      In SIP information view

Gallery: CUCM-BIB SIP trunk2

  • Destination address and Destination port  - set to recorder IP address and port configured on the recorder
  • SIP TRunk security profile  set to "Recorder SIP trunk security profile" created earlier
  • Other parameters leave with  default values
  • Click Save button

Step 2. disable unsupported codecs
Navigate to System/Service Parameters/ Select Server and CallManager Service

Gallery: CUCM-BIB Service Params
Search for "Clusterwide Parameters (System - Location and Region )"
Disable unsupported codecs for recorded devices (G722,iLBC,OPUS,iSAC) 

Note : unsupported codecs can cause no RTP data sending to VSLogger


Step 3. Create and configure recording profile
Navigate to Device/ Device Settings/ Recording Profile

Gallery: CUCM-BIB Recording profile



Step 4
Configure call routing
Navigate to Call Routing/ Route/Hunt / Route Pattern

Gallery: CUCM-BIB route pattern



Gallery: CUCM-BIB route pattern2


Step 5. Configure transcoder resources (if needed)


Step 6.  Configure a recording notification tone (if needed)

Navigate to System/Service Parameters/ Select Server and CallManager Service 

Search for " Clusterwide Parameters (Feature - Call Recording )"

Gallery: CUCM-BIB Tone


Step 7.  Configure recorded device (Phone)

Navigate to Device/Phone/ Select device 
Gallery: CUCM-BIB Devices



Gallery: CUCM-BIB Device
1. Set "Built In Bridge*" option to "On"
2. Check chekbox  "Allow Control of Device from CTI" 


Go to DN (Directory Number) Settings
Gallery: CUCM-BIB Device DN



1. Make sure "Allow Control of Device from CTI" checked
2. Search for Line settings for Device

Gallery: CUCM-BIB Device DN Config

2.1 "Recording Option*" set to Automatic Call Recording Enabled
2.2 "Recording profile" set to profile created in previous steps.
2.3 "Recording Media Source*"  set to  Phone Preferred
2.4 "Monitoring Calling Search Space" if specified  or leave none 

Save  and Apply Config.




 


Note:

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 


Troubleshooting Cisco BIB recording


Problem: Cisco  recording session or even calls drop when BIB recording (RTP-forking with built-in bridge) is enabled

Symptoms:

  • calls are dropped after transfer to a recorded line,  
  • conferences cannot be initiated to 2 or more recorded lines  or other call setup related issues

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:

  1. Switch the codec selection to utilize e.g. G.711 everywhere
  2. Implement hardware transcoding between regions

Note:  Errors in codec and transcoding configuration below  can result in loss of recordings or even dropped calls 

 

Region configuration 

  1. Open Cisco Unified CM Administration
  2. Select System / Region menu item
  3. Select or add the recorder(s) region
  4. Check whether region relationship and inter-region codecs are configured according to your needs. Make sure to modify Relationship of recorder region to other regions.

Media resource configuration

  1. Select the System / Device pool option
  2. Select the recorded phones' pool(s)
  3. Check whether valid transcoding resource is available in the Media Resource Group List if according to region relationships and other needs it might be required

Codecs  configuration
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.

  • In the System/Service Parameters menu. Select the cluster to be configured, and Cisco CallManager service.
  • In Clusterwide Parameters (System - Location and Region) box find codec-specific parameters.
  • Set Enabled for All Devices Except Recording-Enabled Devices  for iLBC,  iSAC and G.722

 


 

 

About Adutante JTAPI Link

JTAPI  connector is part of the Adutante server functionality, which allows collecting Call information and signaling events from configured JTAPI providers.

Currently following JTAPI interfaces/providers supported and tested:

  1.   Cisco JTAPI - allows to get additional call information( Call Direction, Calling Party Name), which is not available in BIB call session 

Note:  See tapi/jtapi  cti supported devices matrix  here

Configure JTAPI (CTI Service) on Cisco Unified Call Manager (CUCM)

To enable CTI Service

Double check that Cisco CTIManager Service is Activated

 

Navigate to "Cisco Unified Serviceability" (drop box in top right corner)

Go to Tools->Service Activation  and check CM Services, make sure "Cisco CTIManager" is checked  and Activation Status - "Activated"

 

 

Configure Application User


Gallery: CUCM-BIB Application User

Navigate to "Cisco Unified CM Administration" (drop box in top right corner)

 

 

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


Gallery: CUCM-BIB Application User Controlled Devices



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:

  •  Standard CTI Enabled
  •  Standard CTI Allow Control of Phones supporting Connected Xfer and conf (necessary for Cisco 89xx or 99x SIP phones)

Step 6 - Apply settings

 

Install Cisco JTAPI Client 

Gallery: CUCM-BIB Plugins

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:

http://Name/CCMAdmin/main.asp

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:\Versadial\Adutante\applications\adutante\lib\external\    

 

 

Adutante CTI Configuration 

 To enable jtapi cti link on Adutante open  cti.properties file (C:\Versadial\Adutante\applications\adutante\config\)  with notepad.exe  and add following parameters:       


cti.properties

// jtapi settings

// Cisco JTAPI

cti.jtapi.cisco.enabled=Y     

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 


 

CUCM Clusters and Versadial Recorder

A CUCM Cluster is a group of CUCM servers running the same version of CUCM that share the same database and resources.

 

Typical and recommended solutions for CUCM BIB recording

Single CUCM Cluster and single recorder

   Configuration :  Recording devices group, single recorder/recorder SIP trunk

Single CUCM Cluster and redundant  recorders (Main and Backup recorders)

   Configuration :  Recording devices group, two recorders/recorder SIP trunks (Main and Backup) 

 

Two or more CUCM Clusters and single or redundant  recorder

    Configuration :  Recording devices group on each cluster point to single or redundant  recorder/recorder SIP trunk

Note: while this configuration may work, it is not recommended due potential  duplicate/conflicting configurations of the recorded devices

 

       

 

  • MM/DD/YYYY
  • HH:MM:SSAM
  • HH:MM:SS
  • https://www.adutante.com/portal
  • 1752292975305
  • 5078cdc8900d57b2204934663221751a7a151a252f2a59c9760c3f4fdcfcb873
  • 8c7244b31f1ab28ba5505a54d17a53fa5dd99779c4e0934d054e13beca68baeb
  • ADUTANTE
  • UNKNOWN
  • Y
  • Versadial Solutions
  • N
  • Y
  • 1
Hosted by: Versadial Solutions
try_count=92
p_count=1
u_count=80
s_count=5318