Closed happytulubi closed 5 months ago
No it doesn't, and I don't know why you label this as bug if it's not advertised as being supported anywhere.
@rfuchs apologies for resurrecting an old thread, but as someone who's currently evaluating rtpengine I'd like to clarify one point:
passthrough
in the above logs means)?
@rfuchs apologies for resurrecting an old thread, but as someone who's currently evaluating rtpengine I'd like to clarify one point:
- is it the transcoding of H264 that is not supported OR
- is rtpengine even unable to simply relay/proxy the H264 unmodified (I presume that is what the
passthrough
in the above logs means)?
There is no support for any video transcoding. But any UDP/RTP media can be relayed or proxied, including any video codec (and including RTP/SRTP translation).
rtpengine version the issue has been seen with
No response
Used distribution and its version
No response
Linux kernel version used
No response
CPU architecture issue was seen on (see
uname -m
)None
Expected behaviour you didn't see
I requested rtpengine while converting voice to video and received the following error. Does rtpengine not support H264? What should I do?
714381126.610083] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Using passthrough handler for H264/90000 with DTMF -1, CN -1 [1714381126.610089] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Codec answer for Nmt5K6HH59jvg #2 [1714381126.610092] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Reverse codec for H264/90000 (102) is H264/90000 (102) [1714381126.610108] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Setting up codec handlers for oktdjfbudc #2 -> Nmt5K6HH59jvg #2 [1714381126.610120] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Checking receiver codec H264/90000/1 (102) [1714381126.610123] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] No codec support for H264/90000 [1714381126.610126] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Using passthrough handler for H264/90000 with DTMF -1, CN -1 [1714381126.610132] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Updating supplemental codecs for oktdjfbudc #2 [1714381126.610136] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Updating supplemental codecs for Nmt5K6HH59jvg #2 [1714381126.610139] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Setting up codec handlers for oktdjfbudc #2 -> Nmt5K6HH59jvg #2 [1714381126.610143] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Checking receiver codec H264/90000/1 (102) [1714381126.610146] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] No codec support for H264/90000 [1714381126.610149] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Using passthrough handler for H264/90000 with DTMF -1, CN -1 [1714381126.610154] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Setting up codec handlers for Nmt5K6HH59jvg #2 -> oktdjfbudc #2 [1714381126.610158] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] Checking receiver codec H264/90000/1 (102) [1714381126.610161] DEBUG: [61efa3cb-80a9-123d-c684-fa163eee4917]: [codec] No codec support for H264/90000
Unexpected behaviour you saw
No response
Steps to reproduce the problem
No response
Additional program output to the terminal or logs illustrating the issue
No response
Anything else?
No response