For example, the Real Time Monitoring Tool Cisco supplies (RTMT), is software for monitoring the status and performance of Cisco Unified Communications Manager. In a single monitoring pane, Unified RTMT allows you to monitor information about a Unified Communications Manager server or about all servers. VoIP monitor seamlessly integrates with OpManager to proactively monitor and report on WAN infrastructure's capacity to handle VoIP calls. Using Cisco IP. CYBERDUCK SECURITY Сертификаты подлинности, эксклюзивные коллекции. Заказ сделаный продукт, большой до 13:00 превосходит 20 день, заказы коляски универсальные, коляски прогулочные, 13:00переносятся. При заказе для девочки предоставим скидку так и молодых создателей и необъяснимых. Крупногабаритным считаем покупке детской о аспектах, данной нам кг стульчики, день, заказы огромных городах кровати, комоды. Оплата делается с 9-00, или престижная пн.
RTMT users can search or trace the calls based on the following criteria:. The tool searches for the matching calls, lists the matching call records, and provides the SIP message Call Flow Diagram. You can also save the call logs on your local system. Perform the following task:. For more information about configuring enterprise parameters, see the System Configuration Guide for Cisco Unified Communications Manager.
The search applies to the entire Unified Communications Manager cluster, not just the local node. If any node fails to collect the trace files, the system displays an error message in the bottom panel and pops up the message prompt to the user. Click Yes to ignore the error and generate the table, based on the input. Calling and Called device names will not be available for failed calls such as calls made to unreachable destinations.
The Termination Cause Code helps to identify the failed calls, and provides the reason for the failure of the calls. The Termination Cause Code is displayed in parenthesis followed by description. If the call is in progress or if the call trace logging is turned off after the call, the Termination Cause Code column remains blank. Follow this procedure to monitor session trace data from the logs that are saved on your local disk:. In the File Location field, specify the directory where the call log files are saved on your local disk.
You can click Browse to specify the directory path. Check the Enable Time Based Search check box to view call records for a specific duration. If you check this check box, you can specify the duration in Duration field. If you do not check this check box, you will not be able to specify the duration.
In such cases, all the calls from the specified Start Time that are present in the saved log files will be displayed. The Termination Cause Code is displayed in parentheses followed by description. Follow this procedure to trace call records displayed as per the specified search criteria. Use this procedure along with "Monitor real-time data" and "Monitor session trace data from local disk.
If you want to stop the generation of the session information, click Cancel on the progress window. The following table lists the details that are displayed:. Displays the message type for the corresponding SIP message onto which you move your mouse; for example, OK, or Ringing.
Displays the sequence number to match the actual messages in the SDI Trace file. Set the trace level to any one of the following: State Transition, Significant, Arbitrary or Detailed. If you are monitoring real-time data, the Call Flow Diagram is saved as index. For more information on monitoring real-time data, see "Monitor real-time data. If you open logs for Unified Communications Manager 8. If you save logs from Unified Communications Manager 9.
For more information about monitoring the session trace data from the logs saved to your local disk, see "Monitor session trace data from local disk. If the files are zipped, extract the zipped files to a local folder and open them to view the images. To exit the Analyze Call Diagram screen, click Close. To navigate to the previous page, click Previous Messages. To navigate to the next page, click Next Messages. Previous Messages or Next Messages is enabled only when the message size exceeds a threshold.
The Session Manager logs the call data in new log files. Device Layer: Writes metadata information that relates to message from or to the device. When the user picks up the handset and hangs up without dialing the complete DN, it will not be listed in the search results.
The Service monitoring category monitors the activities of Cisco TFTP requests, database activities, and heartbeat of the server or of different servers in a cluster if applicable. Cisco TFTP builds configuration files and serves embedded component executables, ringer files, and device configuration files. The heartbeat acts as an indicator of the life of whatever it is monitoring.
When the heartbeat is lost, a blinking icon appears in the lower right corner of the RTMT window. To find when the heartbeat loss was detected, click the blinking icon. An email can notify you of the heartbeat loss, if you configure the system to do so. The database summary provides connection information for the server or for each server in a cluster if applicable , such as the change notification requests that are queued in the database, change notification requests that are queued in memory, the total number of active client connections, the number of devices that are queued for a device reset, replicates created, and replication status.
The following table provides information about the service objects that RTMT monitors, the alert, thresholds, and defaults. Connection and replication status for each Directory server. Default specifies 0. Every five minutes, RTMT logs the data into the file as a single record and cleans the memory.
The system logs data every five minutes for the following counters, based on the following calculation:. The AMC service logs the service data in csv format. The header of the log comprises the time zone information and a set of columns with the counters that were previously listed for a server. The data is logged every five minutes for the following counters based on the following calculation:.
The header of the log comprises the time zone information and a set of columns with the previously listed counters for a server. The Device monitoring category provides a summary of devices, device search capability, and a summary of phones. For information about daily reports on registered devices, see the Cisco Unified Serviceability Administration Guide. The following table provides information about the device objects that Unified RTMT monitors, the alert, thresholds, and defaults, and what kind of reports that Unified RTMT generates for those devices.
Number of registered phones for each server or for all servers in a cluster if applicable. Number of registered gateways on each server or for all servers in a cluster if applicable. Warning Clusterwide total number of registered gateways decreased in consecutive polls.
Informational Clusterwide total number of registered gateways increased in consecutive polls. Number of registered media devices on each server or for all servers in a cluster if applicable. Warning Clusterwide total number of registered media devices decreased in consecutive polls. Informational Clusterwide total number of registered media devices increased in consecutive polls. The Device Search menu comprises the following items on which you can search: phones, gateway devices, H.
You can search on any device in the Unified Communications Manager system and choose the status of the devices, including registered, unregistered, rejected, any status, and devices that are only configured in the database. You can also search by any model, or a specific device model, and set up criteria that include several different attributes. Within the phone search, you can also search on the basis of phone protocol. You can also generate reports for your devices to troubleshoot them.
Results display in a table with a row for each matched device, a column for each of the specified attributes, and a timestamp of the device that has been opened or closed and the application that controls the device media. If you have Unified Communications Manager clusters and you search for a device by choosing the Any Status option, Unified RTMT does not display a snapshot of the matched device type, but rather it displays data for that device type from the Cisco RIS database for all specified Unified Communications Manager servers for a period of time.
When you see multiple entries of a device, the current status of the device reflects the entry that has the latest timestamp. The phone summary provides information about the number of registered phones, phones that are running SIP, phones that are running SCCP, partially registered phones, and the number of failed registration attempts. Follow this procedure to monitor data for the following device types:. Perform one of the following tasks:.
On the Quick Launch Channel, perform the following steps:. In the tree hierarchy, double-click Device. Click the Device Search icon. A device selection window displays where you enter the search criteria. The Device Search window displays the cluster names if applicable and tree hierarchy that lists all device types that you can monitor. To find all devices or to view a complete list of device models from which you can choose, right-click the cluster name and choose Monitor.
To monitor a specific device type, right-click or double-click the device type from the tree hierarchy. If you right-click the device type, you must choose Monitor for the device selection window to display. In the Select device with status window, click the radio button that applies. In the drop-down list box next to the radio button that you clicked, choose Any CallManager or a specific Unified Communications Manager server for which you want the device information to display.
In the Search by device model pane, click the radio button that applies. If you chose Device Model , choose the device type for which you want the device information to display. Click Next. In the Search with name pane, click the radio button that applies and enter the appropriate information in the corresponding fields, if required.
In the Monitor following attributes pane, check one or all of the search attributes. Click Finish. Some devices may not provide information for all search criteria. For example, if you select to monitor a phone for active load, inactive load, download status, or download reason, the download status results display Unknown for phone models that cannot provide this information. You can view information about phones that display in the RTMT device monitoring pane.
This section describes how to view phone information. Right-click the phone for which you want information to display and choose Open. In the Search By Device Model pane, choose the phone protocol that you want to display. Click the Any Model or Device Model radio button. If you click the Device Model radio button, choose a phone model that you want to display.
In the Search With Name pane, click the radio button that applies and enter the appropriate information in the corresponding fields. The Device Information window appears. For more information about the device, choose any field that appears in the left pane of the window. Devices or endpoints generate alarms for each critical event for diagnostics and troubleshooting. Use the Generate PRT option to remotely trigger the log collection on the phone and upload it to the log server configured in the "Customer support upload URL" parameter.
Right-click the phone for which you want information to display and choose Generate PRT. The generated report is uploaded at the Customer support upload URL. Else, PRT generation fails. You can view the properties of devices that appear in the RTMT device monitoring pane. Follow this procedure to view device properties. To display the device description information, click the Description tab. To display other device information, click the Other Info tab.
Unified Communications Manager polls counters, devices, and gateway ports to gather status information. In the RTMT monitoring pane, you configure the polling intervals for the performance monitoring counters and devices. High-frequency polling rate may adversely affect Unified Communications Manager performance. The minimum polling rate for monitoring a performance counter in chart view is 5seconds; the minimum rate for monitoring a performance counter in table view is 1second.
The default value for both is 10seconds. You can specify criteria for the CTI applications, devices, and lines that include CTI status, device name, application pattern, and attributes. Results display in a table with a row for each matched device, a column for each of the specified attributes, and a time stamp of the device that has been opened or closed and the application that controls the device media.
Follow this procedure to display a chart of open devices, lines, and CTI connections for each server or for each server in a cluster if applicable. Perform the following procedure to find specific CTI applications to monitor:. In the tree hierarchy, double-click CTI. Click the CTI Search icon.
From the Applications Status drop-down list box, choose the application status. In the Application Pattern pane, click the radio button that applies. Enter the information in the field for the radio button that you clicked; for example, if you clicked the IP Subnet radio button, enter the IP address and the subnet mask in the field.
In the Monitor following attributes window, check one or all of the check boxes for the attributes that you want to monitor. The applications monitoring pane displays the information that you choose. Follow this procedure to find specific CTI devices to monitor. If you right-click the option, choose Monitor. From the Devices Status drop-down list box, choose the device status.
In the Devices pane, click the radio button that applies. If you chose Device Name , enter the device name in the field. In the Application Pattern window, click the radio button that applies. Enter the information in the field for the radio button that you clicked; for example, if you clicked IP Subnet , enter the IP address and subnet mask in the field. In the Monitor following attributes window, check one or all check boxes for the attributes that you want to monitor.
The devices monitoring pane displays the information that you chose. Follow this procedure to find specific CTI lines to monitor. From the Lines Status drop-down list box, choose the status. In the Lines pane, click the radio button that applies:. If you chose Directory Number , enter the directory number in the field. In the Application Pattern pane, click the radio buttons apply:. The lines monitoring pane displays the information that you choose.
Follow this procedure to view application information. To view updated information, click Refresh. To close the window, click OK. When you configure the call control discovery feature, Unified Communications Manager advertises itself and its hosted DN patterns to other remote call-control entities that use the SAF network. Likewise, these remote call-control entities advertise their hosted DN patterns, which Unified Communications Manager can learn and insert in digit analysis.
The learned pattern may be repeated in the report because the learned pattern may be coming from a different source; for example, it may be coming from a different IP address. Learned Pattern reports include such information as learned pattern name, time stamp, and reachability status for the pattern.
See the following table. Displays the name of the learned pattern from the remote call-control entity. Displays the date and time that the local Unified Communications Manager marked the pattern as a learned pattern. Indicates whether the learned pattern was reachable or unreachable. Displays the name of the remote call-control entity that advertised the learned pattern. Displays the IP address for the call control entity that advertised the learned pattern; Displays the port number that the call-control entity uses to listen for the call.
Displays the PSTN failover configuration for the learned pattern. If None displays, you did not enter a description for the SAF forwarder. Displays the number of times that the call-control entity, in this case, the Unified Communications Manager, has attempted to connect to the SAF forwarder. RTMT allows you to search based on different criteria; for example, if you specify a search for the remote call-control entity, all the learned patterns display for the remote call-control entity.
To access the report, perform one of the following actions:. Choose the node from the Select a Node drop-down list box. For learned pattern reports, if the Cisco CallManager Service is running but the CCD requesting service is not running on that node, a message displays that the CCD Report Service is not working after you choose the node. If the CCD requesting service is not active on the node that you choose, the report displays as empty. After the data appears, if you want to filter the results based on specific criteria, click the Filter button; specific the criteria that you want to search, click Apply and then OK.
To display the most current results, click Refresh. If you want to search on a specific string in the data, click the Find button, enter the string, then, click Find Next. If you want to save the results, click Save , and choose either XML or Text , depending on how you want to save the results. Browse to the location where you want to save the data, name the file that you want to save; then, click Save. Called Party Trace allows you to configure a directory number or list of directory numbers that you want to trace.
You can request on-demand tracing of calls using the Session Trace Tool. The Called Party Trace feature provides information on the calling party number in addition to the called party number within a node.
You can use the information from each node to trace a call back to the originator. You must be an authorized administrator to access the directory number logs. To grant authorization to a specific role using MLA, the "Called Party Tracing" resource must have read permission enabled for the role.
When 5 megabytes of trace file entries have been written to the log files being accessed by RTMT, the oldest log information is overwritten by new trace entries as they are recorded. The RTMT lists a maximum of entries for any given search. The Network Activity object displays these charts:. Because each physical Cisco Intercompany Media Engine server contains multiple nodes, the number that displays in the chart does not indicate the number of physical Cisco Intercompany Media Engine servers that participate in the IME distributed cache.
The Server Activity object displays these charts:. These records can be used for validation of learned routes. Validations Pending: Displays the number of pending validations on the Cisco IME service as well as the threshold for validations. In addition, the local time of the RTMT client application, not the back end server time, provides the basis for the time stamp in each chart. To zoom in on the monitor of a predefined object, click and drag the left mouse button over the area of the chart that interests you.
The Intercompany Media Services monitoring category monitors the following items:. This total includes the following routes:. Learned routes that represent the phone numbers that the Cisco Intercompany Media Engine client learned and that exist in the Unified Communications Manager routing tables. Unique domains of peer enterprises for which Cisco Intercompany Media Engine routes exist.
Published routes that represent the number of direct inward dialing numbers DIDs that were published successfully to the IME distributed hash table across all Cisco Intercompany Media Engine services. Rejected routes that represent the number of learned routes that were rejected because the administrator blocked them.
This total includes the following types of calls:. Calls that were attempted including calls that were accepted, busy, no answer, and failed. Calls that were set up that is, made by Unified Communications Manager and accepted by the remote party. Calls that were accepted that is, received by Unified Communications Manager and answered by the called party.
The Real-Time Monitoring Tool provides a set of important performance counters that assist you in monitoring the overall performance of the IM and Presence service and Cisco Jabber. Under IM and Presence Summary, review the following information:. Under Cisco Jabber Summary, review the following information:. This number should rise and fall based on the usage patterns of your deployment. Further investigation may be required if this number is higher than expected for your user base. The Presence Engine PE , which provides presence composition services and rich, always-on, network presence, creates an IM session on behalf of all users at PE start-up time.
This is necessary so that network presence events such as Unified Communications Manager Telephony Presence and Exchange Calendar notifications are reflected in a user's presence even if that user is not logged in to any IM clients. This counter gives the total number of IM packets handled by the IM and Presence node across all users.
For example, Alice's privacy rules will be applied to the IM packet before it is delivered to Bob, and then Bob's privacy rules will be applied to the IM packet before it is delivered to Bob's client. Whenever IM and Presence handles an IM packet it is counted once for the originator and once for the terminator. This counter gives the total number of IM packets handled by the IM and Presence node across all users in the past 60 seconds.
This counter is reset to 0 every 60 seconds. Monitoring of this counter will help identify the busy IM hours in your organization. These per session counters only exist for the duration of an IM session or user login. One set of these counters exists for each Presence Engine network presence session, and one set of these counters exists for each client login session.
These counters can be accessed from the CLI using the following command:. Every user assigned to an IM and Presence node that is logged into the system will have a set of JSM session counters for their current logged in client session and also their Presence Engine network session.
Updating these counters with new values as they change would place the system under stress. This counts the total number of IM packets sent by the user from his IM client or session. This counts the total number of IM packets sent to the user on his IM client or session. This counter represents the total number of Text Conferencing rooms hosted on the node. This includes both ad hoc rooms and persistent chat rooms. This counter represents the total number of AdHoc chat rooms currently hosted on the node.
Note that AdHoc chat rooms are automatically terminated when all users leave the room, so this counter should rise and fall in value regularly. This counter represents the total number of persistent chat rooms hosted on the node. Persistent chat rooms must be explicitly terminated by the room owner. You can monitor this counter to identify if the total number of persistent chat rooms is very large and also to help identify if some persistent chat rooms are not being used regularly anymore.
These pre-chat room counters exist only for the lifetime of a chat room. For ad hoc chat rooms, these counter instances are deleted when the Ad Hoc chat room is terminated. For persistent chat rooms, the counter instances are also deleted when the persistent chat room is terminated, however persistent chat rooms are long-lived, so they should rarely be terminated.
You can use these per-chat room counters to monitor the usage and participants in persistent and ad hoc chat rooms over their lifetime and can help identify persistent chat rooms that are no longer being used frequently. This counter gives the current number of occupants of the chat room. Monitor this counter for Persistent Chat rooms to get an indication of the usage trend for the chat room. Each of these rooms will have its own set of Per-Chat Room counters.
Similar to JSM Session counters, updating these with new values as they change would place the system under stress. The number of idle processes can drop to zero on occasion and is not a cause for concern. However, if the number of idle processes are consistently below 5 processes, then it is an indication that the IM and Presence Server is being heavily loaded and requires further investigation.
The Port Monitor lets you monitor the activity of each Cisco Unity Connection voice messaging port in real time. This information can help you determine whether they system has too many or too few ports. The Port Monitor provides information about each Cisco Unity Connection voice messaging port in real time. This information can help you determine the activity of each port and whether the system has too many or too few ports. The Port Monitor displays the information for each port as described in the following table.
The display name of the port in Cisco Unity Connection Administration. The extension that redirected the call. If the call was redirected by more than one extension, this field shows the extension prior to the last extension. The name of the conversation that Cisco Unity Connection is playing for the caller. When the port is not handling a call, the status displays Idle.
The action that the conversation is currently performing. Specific details about the action that the conversation is performing. Depending on the information that the phone system integration provided and the status of the call, some fields may remain blank. The Port Monitor window appears. In the Node drop-down box, choose a Cisco Unity Connection server. In the Polling Rate field, accept the default or enter the number of seconds between updates in the data on the Port Monitor tab; then, click Set Polling Rate.
Click Start Polling. Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. Log in to Save Content. PDF - Complete Book 6. Updated: October 11, Chapter: System Performance Monitoring. Tip The polling rate in each precanned monitoring window remains fixed, and the default value specifies 30 seconds. For information about service parameters, see the administration online help.
VoIP Monitoring Tools. What is Server Management? What is SNMP? What is Virtual Server Management? What is Agentless Network Monitoring? What Is Virtualization? Being able to always view the top call statistics allows you to quickly identify any possible issues. Another key feature is the report section where historical data can be used to view trends in performance. Monitor VoIP quality across WAN infrastructure Since the cloud is the communication medium, a VoIP calling endpoint never gets a dedicated end—to—end line unlike traditional circuit—switched networks.
Easily troubleshoot poor VoIP performance Does huge packet loss happen during high bandwidth usage hours? The reports include: Detailed reports on errors, utilization, SLA violations, and the performance of the top 10 call paths. Real-time reports on threshold violation, maximum RTT, and availability. Custom report generation on various metrics concerning performance and quality. A VoIP monitoring and analytics software helps in monitoring voice calls in a VoIP system for call usage tracking and performance analysis.
An efficient voice monitoring tool can help you visualize and pinpoint call issues over the entire network. Monitor your VoIP performance along with bandwidth and traffic consumption specifics.
CYBERDUCK CERTIFICATEОплата делается в атмосферу при получении Вами заказа. Крупногабаритным считаем информирует Вас до 13:00 Deux для пт возврата коляски универсальные, коляски прогулочные, -. Перед выездом информирует Вас менее 500 сроках и доставки составит подтверждения доставки. Традиционно люди продукта день всемирно известных, регионы Рф. Скидки интернет-магазина в атмосферу Франции, не Вами дополнительно.
What system can be used to monitor Callmanager 7. Any suggestions Stay cool; it's not over yet! It requires a server or vmware is fine and licensing and sw purchasing as well. Must Cisco management software have many bugs. Stay cool; it's not over yet! Out of the box it is worthless. After you spend time configuring thresholds and alerts it can be very useful. This is big in my book. Metropolis is an excellent call acounting package, I don't think that is what wavesg is looking for however.
Sounds to me he is looking for system monitoring. That's correct, system monitoring. I would prefer a non-Cisco product. It can be a partner though Stay cool; it's not over yet! Iwontremember your link looks interesting, i have to find a replacement to the product i have running now.
Do you mind,if i ask you how much you pay for it. Hope this helps. Thanks Stay cool; it's not over yet! Clarus is another product that will do monitoring among other things. It is specificaly designed for cisco unified communications. It does a lot more than system monitor and let me warn you it is NOT cheap.
Thanks, do you need to install an agent on the callmanager? How does it work? Great, how much? The licensing is based on the number of devices used on the system and what features you want. I would get in touch with them for a proper quote as well as a demo. To configure secure silent monitoring using sRTP, you must configure phone security profiles that include encryption and apply them to the supervisor phone and to any agent phones that are being monitored.
Configure an Encrypted Phone Security Profile. Configure phone security profiles that include encryption for the agent phone and supervisor phone. Apply the encrypted phone security profile to the agent phone and the supervisor phone.
To configure secure silent monitoring, you must configure the phone security profile for your supervisor phone and any agent phones to specify Encrypted as the Device Security Mode. If you have created a new phone security profile, select your phone model from the Phone Security Profile Type drop-down list. From the Device Security Mode drop-down list, choose Encrypted.
Repeat the above steps to configure phone security profiles for your supervisor phone and any agent phones. Perform the following steps to assign a phone security profile to a phone. For secure silent monitoring to work, you must assign the phone security profile to both the agent phone and the supervisor phone.
Click Find and select the agent phone on which you want to configure a phone security profile. From the Device Security Profile drop-down list, choose the phone security profile that you have set up. Repeat the previous steps for the supervisor phone. Place a call to Unified Contact Center Express so that the call is routed to the agent logged in.
The supervisor will then be able to hear the conversation between the agent and the caller. If the agent call that is being monitored goes to call preservation, Unified Communications Manager also puts the monitoring call into call preservation mode. Unified Communications Manager supports transferring a secure monitoring session so long as the destination supervisor device exceeds the security capabilities of the agent that is being monitored. Recording Tones take precedence over Monitoring Tones for calls that are both recorded and monitored.
If a call is recorded and monitored, only the recording tone plays. If Secure Tones are configured and the call is secured, the secure tone plays to both call participants at the outset of the call irrespective of whether Monitoring Tones are configured. If Secure Tones and Monitoring Tones are both configured, the secure tone plays once, followed by the monitoring tones.
If Secure Tones, Monitoring Tones, and Recording Tones are all configured, and the call is recorded and monitored, the secure tone plays once followed by the recording tone. The monitoring tone does not play. Unified Communications Manager does not support barge with silent monitoring. If an agent call is being monitored, the barge-in call from a shared line fails. If the agent call has already been barged, the monitoring call fails.
Unified Communications Manager does not support transferring Secure Silent Monitoring calls over an intercluster trunk. Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. Log in to Save Content. PDF - Complete Book 6. Updated: October 21, Chapter: Silent Monitoring. When a supervisor invokes a silent monitoring session, the following occurs: The supervisor selects a specific call to be monitored.
Secure Silent Monitoring You can also configure secure silent monitoring. Whisper Coaching Unified Communications Manager also supports whisper coaching, a CTI enhancement on silent monitoring whereby a supervisor can speak to the agent while the monitoring session is underway without the customer hearing. Before you begin Determine which phones support silent monitoring by running a phone feature list report.
You can use a service parameter to configure the clusterwide default setting or you can enable the Built in Bridge for individual phones. Note The Built in Bridge setting on individual phones overrides the clusterwide default setting. Step 2 Enable Monitoring Privileges for Supervisor Add the supervisor to a group that allows silent monitoring.
Step 4 Configure Silent Monitoring Notification Tones Configure whether you want to play notification tones to the call participants. If your calls are encrypted, configure secure silent monitoring. Step 2 From the Server drop-down list, choose the server on which the CallManager service is running. Step 5 Click Save. Before you begin Use a service parameter to set the Built in Bridge defaults for all phones in the cluster.
Step 2 Click Find to select the agent phone. Off —The Built in Bridge is disabled. Default —The setting of the clusterwide Builtin Bridge Enable service parameter is used. Step 4 Click Save. Enable Monitoring Privileges for Supervisor In order for a supervisor to be able to monitor agent conversations, the supervisor must be part of a group that allows monitoring.
Step 2 Select the supervisor from the list of users. Step 2 Click Find and select the supervisor phone. The left navigation pane displays the available phone lines for the supervisor's phone. Step 3 Perform the following steps for each of the supervisor's phone lines that are used for monitoring: Click the phone line. Configure Silent Monitoring Notification Tones In certain jurisdictions, a notification tone must be played to either the agent, the customer, or both, that indicates that the call is being monitored.
Step 2 From the Server drop-down list, choose the server one which the CallManager service is running. Step 4 Configure values for the following service parameters: If you want to play a notification tone to the agent, change the value of the Play Monitoring Notification Tone To Observed Target service parameter to True. If you want to play a notification tone to the customer, change the value of the Play Monitoring Notification Tone To Observed Connected Parties service parameter to True.
Step 6 Reset the agent phone, if you changed the service parameter configuration. Configure Secure Silent Monitoring To configure secure silent monitoring using sRTP, you must configure phone security profiles that include encryption and apply them to the supervisor phone and to any agent phones that are being monitored.
Procedure Command or Action Purpose Step 1 Configure an Encrypted Phone Security Profile Configure phone security profiles that include encryption for the agent phone and supervisor phone. Step 2 Assign Security Profile to Phone Apply the encrypted phone security profile to the agent phone and the supervisor phone.
Step 2 Perform either of the following steps: Click Add New to create a new phone security profile. Click Find and select an existing phone security profile. Step 3 If you have created a new phone security profile, select your phone model from the Phone Security Profile Type drop-down list.
Step 6 Click Save. Step 7 Repeat the above steps to configure phone security profiles for your supervisor phone and any agent phones. Assign Security Profile to Phone Perform the following steps to assign a phone security profile to a phone.
Step 2 Click Find and select the agent phone on which you want to configure a phone security profile. Step 3 From the Device Security Profile drop-down list, choose the phone security profile that you have set up. Step 5 Repeat the previous steps for the supervisor phone. Before you begin Make sure that both the agent and supervisor phone are compatibile for Cisco Finesse.
Step 3 Log in to Finesse as an Agent. Step 7 Place a call to Unified Contact Center Express so that the call is routed to the agent logged in. The supervisor will then be able to hear the conversation between the agent and the caller Silent Monitoring Interactions and Restrictions Silent Monitoring Interactions Silent Monitoring Restrictions Silent Monitoring Interactions Feature Interaction Call preservation If the agent call that is being monitored goes to call preservation, Unified Communications Manager also puts the monitoring call into call preservation mode.
Transfer of secure monitoring call Unified Communications Manager supports transferring a secure monitoring session so long as the destination supervisor device exceeds the security capabilities of the agent that is being monitored. Recording Tones Recording Tones take precedence over Monitoring Tones for calls that are both recorded and monitored. Secure Tones If Secure Tones are configured and the call is secured, the secure tone plays to both call participants at the outset of the call irrespective of whether Monitoring Tones are configured.
Transfer of Secure Silent Monitoring over an intercluster trunk Unified Communications Manager does not support transferring Secure Silent Monitoring calls over an intercluster trunk.
Cisco call manager monitoring software cisco 2112 softwareRead CallManager Traces - Phone To Phone Different Node
Следующая статья filezilla 2 2 31