Server crashes on rest-call start-recording in Edge

Joren De Maeyer

New Member
I have created a React karaoke app webapp that uses the Flashphoner stream and recording service.

When the page is loaded the Flashphoner is initialized and a session and stream are starting.
When you click on a call to action, the Flashphoner rest-api is called to start the recording.

Everything is working fine on most of the mobile & desktop browsers.

Server version: v.0.5.28.2753-5.2.50-33b00cfec3679ecfa1f4c8b98f5d902ec8acda6f
Browser:
- Microsoft Edge 42.17134.1.0
- Microsoft EdgeHTML 17.17134

(Bottom of the logs you see the error ...)
(Removed the audioConfig because it was too large to upload)
11:18:14,975 INFO RestApiRouter - HTTP-pool-2-thread-2 Use controller class com.flashphoner.rest.server.apps.echo_apps.EchoApp with path /apps/EchoApp/StreamStatusEvent
11:18:14,978 INFO RestClient - API-ASYNC-pool-12-thread-7 RECEIVED REST OBJECT <==
URL:http://localhost:8081/apps/EchoApp/StreamStatusEvent
OBJECT:
{
"nodeId" : "BY6il2CwDteXvlX6AmZ8lhHPWpHQ4LFl@34.254.228.147",
"appKey" : "defaultApp",
"sessionId" : "/84.198.249.219:58536/172.31.0.119:8080-0379d696-792f-4c88-a1dd-87eda9b26231",
"mediaSessionId" : "25d8f690-5602-11e9-b4f0-1f0a0eb8cc55",
"name" : "4fc17e62",
"published" : true,
"hasVideo" : true,
"hasAudio" : true,
"status" : "PUBLISHING",
"audioCodec" : "opus",
"videoCodec" : "VP8",
"record" : false,
"width" : 0,
"height" : 0,
"bitrate" : 0,
"minBitrate" : 0,
"maxBitrate" : 0,
"quality" : 0,
"history" : false,
"gop" : 0,
"fps" : 0,
"audioBitrate" : 0,
"codecImpl" : "",
"transport" : "UDP",
"createDate" : 1554290293467,
"mediaProvider" : "WebRTC",
"origin" : "http://10.0.1.47:3000",
"constraints" : {
"video" : {
"width" : 1280,
"height" : 720
},
"audio" : true
}
}
11:18:15,351 INFO RtpVideoConfig - STUN-UDP-pool-36-thread-1 VideoResolution C 0x0
11:18:15,671 INFO RestApiRouter - HTTPS-pool-4-thread-1 Use controller class com.flashphoner.rest.server.rest_v2.RestStreamController with path /rest-api/stream/startRecording
11:18:15,673 INFO RestStreamController - HTTPS-pool-4-thread-1 handleRequest /rest-api/stream/startRecording params:{mediaSessionId=25d8f690-5602-11e9-b4f0-1f0a0eb8cc55}
11:18:15,682 INFO MediaSession - HTTPS-pool-4-thread-1 Creating FileFFOutputWriter - opus H264
11:18:16,206 INFO FFOutputWriter - VideoProcessor-25d8f690-5602-11e9-b4f0-1f0a0eb8cc55 Init output writer '/usr/local/FlashphonerWebCallServer/records/stream-25d8f690-5602-11e9-b4f0-1f0a0eb8cc55-r8fbcth6hfe5jvcb343sdno2io.webm'
AudioConfig{removed because of too large --ignore }
VideoConfig{codec='H264', width=424, height=240, profile=66, level=21, spropParameterSets=000000016742401595a86c7f97c04400000fa00001d4c236870ba80000000168ce3c80}
11:18:16,223 ERROR FFOutputWriter - VideoProcessor-25d8f690-5602-11e9-b4f0-1f0a0eb8cc55 Can not initialize /usr/local/FlashphonerWebCallServer/records/stream-25d8f690-5602-11e9-b4f0-1f0a0eb8cc55-r8fbcth6hfe5jvcb343sdno2io.webm
11:18:16,224 INFO RtcMediaClient - VideoProcessor-25d8f690-5602-11e9-b4f0-1f0a0eb8cc55 Stop media session 25d8f690-5602-11e9-b4f0-1f0a0eb8cc55
 
We've reproduced the problem. It occurs when VP8 codec priority is higher then H264:
Code:
codecs=opus,...,vp8,h264,...
We work on it to prevent server crashes and let you know when fix it.
As workaround, you can disable H264 on MS Edge side using stripCodecs option:
Code:
    session.createStream({
        name: streamName,
        display: localVideo,
        cacheLocalResources: true,
        receiveVideo: false,
        receiveAudio: false,
        stripCodecs: "H264,h264"
    })
 
Good day.
We fixed the problem with recording stream from MS Edge when VP8 priority is higher then H264. Please update to build 5.2.68 and check.
 
Top