a) Issue Description:
In OCM Audio/Video Playback report, users are unable to play the Audio/Video recordings with OCM displaying message as "There is no recordings to this session to preview"
b) Components to Verify:
Component | What to Check | Where to Check |
Recorder service | Is the WebRTCRecorder Service Up and Running | Start -> Task Manager -> Services Tab -> WebRTCRecorderService |
OCM | In OCM, user able to load the OCM Audio Video Playback report | 1. Login to OCM 2. Click on OCMReports on right top 3.Set the Report Channel as 'Video',Report Name as 'OCM Audio Video Playback Report' and 'Report Type as 'Date Range'(Provide the valid date)'. 4.Click on 'Show Report' |
Recorder | If the recordings are available | Check if the recordings are available in provided recording path(Ex: C:\WebRTCRecorder\Data\Processed) The file mixed-v.webm present inside the processed folder should be able to play in VLC player or chrome. |
c) Keywords to Search:
Component | Keywords | Log Path |
OCM Logs | Go to OCM folder ->Web.config -> key ‘Log4NetConfigFile’ will have the path to OCMLogs | |
Recorder Service | Go to WebRTCRecorder folder -> Log4net.config -> key ‘Log4NetConfigFile’ will have the path to RecorderLogs |
d) Troubleshooting:
Component | Details |
OCM | Provide complete access to the WebRTC Certificate folder. The certificate folder should contain a valid certificate.
Below are the steps to generate the certificate, 1. Go to IIS and click on the Server certificate 2. Click on Create Self Signed certificate, specify the certificate name 3. Click on 'OK' Follow the below steps to copy .cer certificate to certificate folder.
|
OCM Config | Check if the below config key is present in the OCM configuration file, if not present add this config key and check if the certificate path is provided in OCM config file as shown below. <add key="WebRTCRecorderCertificateFolder" value="C:\Avaya\OCM\Certificate" /> The certificate folder should contain a valid certificate generated for that server in .cer format. |
OCM Config | Scenario: Check by providing localhost/IP/server domain in both OCM config and WebRTC recorder config file as given below. These changes provided when OCM and WebRTC recorder are in same server. In OCM configuration check for the below keys: <add key="WebRTCRecorderAPIUrl" value="https://localhost:port/wrs/recording/rest/session/" />
|
Recorder Config | Scenario: Check by providing localhost/IP/server domain in both OCM config and WebRTC recorder config file as given below. These changes provided when OCM and WebRTC recorder are in the same server. In Recorder configuration check for the below keys: <add key="hostPublicName" value="localhost "/>
<add key="hostPublicName" value="localhost"/> |
OCM Config | Scenario: Check by providing localhost/IP/server domain in both OCM config and WebRTC recorder config file as given below. These changes provided when OCM and WebRTC recorder are in same server/different server. In OCM configuration check for the below keys: <add key="WebRTCRecorderAPIUrl" value="https://server-ip:port/wrs/recording/rest/session/" />
|
Recorder Config | Scenario: Check by providing localhost/IP/server domain in both OCM config and WebRTC recorder config file as given below. These changes provided when OCM and WebRTC recorder are in the same server/different server. In Recorder configuration check for the below keys: <add key="hostPublicName" value="server-ip"/> Provide IP in both OCM config and recorder config file, |
OCM Config | Scenario: Check by providing localhost/IP/server domain in both OCM config and WebRTC recorder config file as given below. These changes provided when OCM and WebRTC recorder are in the same server/different server. In OCM configuration check for the below keys: <add key="WebRTCRecorderAPIUrl" value="https://domain name:port/wrs/recording/rest/session/" /> Provide server domain in both OCM config and recorder config file as shown below, |
Recorder Config | Scenario: Check by providing localhost/IP/server domain in both OCM config and WebRTC recorder config file as given below. These changes provided when OCM and WebRTC recorder is on the same server/different server. In Recorder configuration check for the below keys: <add key="hostPublicName" value="domain-name"/> Provide server domain in both OCM config and recorder config file as shown below, |
Recorder | Check if the recordings(mixed-v.webm) are playing in the Processed folder of the Recorder(path C:\WebRTCRecorder\Data\Processed). |
OCM | If OCM and Recorder are in same server, no need to provide "WebRTCRecorderSecurityProtocolType" key value in the config <add key="WebRTCRecorderSecurityProtocolType" value=" " /> If both are in different server, provide security protocol in OCM web config. |
OCM | Binding the certificate Refer: https://weblog.west-wind.com/posts/2013/sep/23/hosting-signalr-under-sslhttps |