What version of Janus is this happening on?
v1.1.4 cascade feature
Put the version and the commit identifier (available in version.c or from an info request) here
Have you tested a more recent version of Janus too?
this bug existed on the latest code
Was this working before?
No
Is there a gdb or libasan trace of the issue?
No
Additional context
“h264_profile”,“vp9_profile” of remote publisher's stream type error.
When invode "add_remote_publisher" and "update_remote_publisher" request, its parameter is checked according to the remote_publisher_stream_parameters structure, which is defined as below:
In this definition, "h264_profile" and "vp9_profile" is defined as JANUS_JSON_BOOL type. But when these both parameter is used later, they are interpreted as a string, as the following code:
What version of Janus is this happening on? v1.1.4 cascade feature Put the version and the commit identifier (available in
version.c
or from aninfo
request) hereHave you tested a more recent version of Janus too? this bug existed on the latest code
Was this working before? No
Is there a gdb or libasan trace of the issue? No
Additional context
“h264_profile”,“vp9_profile” of remote publisher's stream type error.
When invode "add_remote_publisher" and "update_remote_publisher" request, its parameter is checked according to the remote_publisher_stream_parameters structure, which is defined as below:
In this definition, "h264_profile" and "vp9_profile" is defined as JANUS_JSON_BOOL type. But when these both parameter is used later, they are interpreted as a string, as the following code:
They should be a mistaken when coding