Publishing works (received on server) and is available for playback over RTMP or HLS / MPEG DASH after transcoding but does not work directly in WebRTC.
Publisher JS reports correctly configured profile-level-id 42e01f (Constrained Baseline) in SDP:
Playback JS reports incorrect profile-level-id in SDP:
And results in error:
OperationError: Failed to set remote offer sdp: Session error code: ERROR_CONTENT. Session error description: Failed to set remote video description send parameters..
The RTSP stream accessible on server seems to have High profile when publishing with Safari:
h264 (High), yuv420p(progressive), 640x480, 30 tbr, 90k tbn, 180k tbc
When publishing with Chrome is Constrained Baseline:
h264 (Constrained Baseline), yuv420p(progressive), 640x480, 30 tbr, 90k tbn, 180k tbc
Same code works fine when broadcasting from Chrome:
And Chrome stream plays fine in all browsers, including in Safari:
The issue seem to be related to Safari publishing stream with High 64C029 profile instead of Constrained Baseline 42e01f.
The question: Is there something that can be done in JS code or Wowza configuration for Safari WebRTC stream to playback using WebRTC directly (without transcoding), similar to how Chrome streams work?