Troubleshooting Tips for Cisco MediaSense
From DocWiki
(Difference between revisions)
(→General) |
|||
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
| - | |||
| - | |||
'''Print PDF:''' [[Print Troubleshooting Tips for Cisco MediaSense]] | '''Print PDF:''' [[Print Troubleshooting Tips for Cisco MediaSense]] | ||
Revision as of 13:27, 27 September 2012
Print PDF: Print Troubleshooting Tips for Cisco MediaSense
Contents |
API
- API: API request returns Error 405: Method not supported
- API: Incorrect participant duration
- API: MediaSense application sign-in fails with administration credentials
- API: Missing events and closed subscription
- API: Incorrect session or participant duration
Administration
- Administration: Administration Login returns unexpected error
- Administration: Unable to access Administration and Serviceability UI on a newly installed system
- Administration: Unknown request error display
- Administration: Saving an AXL service provider configuration will result in an incorrect error message under certain pre-conditions
Configuration
- Configuration: Call between two RT phones is not recorded
- Configuration: Calls using g.722 codec are not recorded
- Configuration: Configuration and Recording meta data is not synchronized between Primary and Secondary Servers
- Configuration: Conversation after a transfer is not recorded on RT-Lite phones
- Configuration: Failure to playback audio or video when using RT video phone
- Configuration: MediaSense application does not record even if recording is enabled
- Configuration: Starting SNMP on MediaSense causes the Host Resource Agent to hang in starting state
Database
- Database: Database not updated after event forwarding
- Database: Database no longer accepts data
- Database: Executing the “show db synchronization status” command on the primary ORA DB server, does not show any information
General
- General: HTTP Status 500 message displays when opening Cisco MediaSense Administration after system restart
- General: Check and repair MediaSense file system Installation
- General: Performance issues as a result of hardware failure
- General: RTSP live monitoring sessions fail when using CUBE
Installation
Upgrade
Recording
- Recording: QuickTime does not playback G.729 recording, but status bar keep moving
- Recording: CUBE disconnects Cisco MediaSense right after recording begins
- Recording: Unified CM drops MediaSense recording as soon as recording begins
- Recording: Recordings from CUBE fail with SIP error 488 Not Acceptable Here
RTMT
- RTMT: Unable to login to RTMT from the primary server
- RTMT: Unified RTMT connected to secondary node, does not show alarm information if the primary node is down
