openvidu-server: prepare for mediaNode CDR events

pull/331/head
pabloFuente 2019-10-04 13:29:27 +02:00
parent bdc35d6654
commit bf1a86fc9a
3 changed files with 7 additions and 5 deletions

View File

@ -45,7 +45,9 @@ public class CDREvent {
public JsonObject toJson() {
JsonObject json = new JsonObject();
json.addProperty("sessionId", this.sessionId);
if (sessionId != null) {
json.addProperty("sessionId", this.sessionId);
}
json.addProperty("timestamp", this.timeStamp);
return json;
}

View File

@ -19,6 +19,6 @@ package io.openvidu.server.cdr;
public enum CDREventName {
sessionCreated, sessionDestroyed, participantJoined, participantLeft, webrtcConnectionCreated, webrtcConnectionDestroyed, recordingStarted, recordingStopped, recordingStatusChanged, filterEventDispatched
sessionCreated, sessionDestroyed, participantJoined, participantLeft, webrtcConnectionCreated, webrtcConnectionDestroyed, recordingStarted, recordingStopped, recordingStatusChanged, filterEventDispatched, mediaNodeAdded, mediaNodeRemoved
}

View File

@ -93,10 +93,10 @@ import io.openvidu.server.webhook.CDRLoggerWebhook;
public class CallDetailRecord {
@Autowired
protected SessionManager sessionManager;
private SessionManager sessionManager;
@Autowired
protected OpenviduConfig openviduConfig;
private OpenviduConfig openviduConfig;
private Collection<CDRLogger> loggers;
@ -226,7 +226,7 @@ public class CallDetailRecord {
this.log(new CDREventFilterEvent(sessionId, participantId, streamId, filterType, event));
}
private void log(CDREvent event) {
protected void log(CDREvent event) {
this.loggers.forEach(logger -> {
// TEMP FIX: AVOID SENDING recordingStarted AND recordingStopped EVENTS TO