This document outlines how to configure Cisco Unified Border Element to do network based call recording using Cisco MediaSense.
The media forking on CUBE supports Cisco’s Open Recording Architecture (ORA). CUBE at the network layer would act as a Recording Client and Cisco MediaSense will act as a Recording Server at the Services Layer.
The functionalities of the Recording Client (CUBE in this case) are:
To set up a separate SIP dialog with Cisco MediaSense
To fork the active calls traversing through it, and to act as the source of the recorded media, sending it to the Recording Server (Cisco MediaSense).
During the initial SIP dialog setup, CUBE sends information to the server, which would help the server associate the call with the media streams and identify the participants of the call. This information is called “metadata”
This recording can then be consumed via any 3rd party partner application.
I have a "just double checking" kind of question. Does swapping the active/inactive phone loads in CUCM Device Defaults cause the phones to reboot and get the new firmware? I have the new firmware staged and ready to swap but wanted to double ...
Hi,We need the following information of the informix databases used by CUCM (version 11.5.1) and CCX (version 11.6.1); - code set- collating sequence- territory Does anybody know which query we can use to get this information? Thanks
We are running CUCM 11.5.1 SU6 and CER 11.5.4. We connect emergency calls to PSTN via AT&T SIP trunks (IP Flex). I received an email notification from our Emergency Responder the other day with the subject "Emergency call could not be rout...