Hi DevNet Community,
i found a difference about the Requested H264 codec profile_level_id in Jabber Web SDK Log between answer call with going to queue 1st and answer call without going to queue 1st.
Answer call with going to queue 1st :
Requested H264 Codec: profile_level_id = 52, max_fs = 0, max_br = 0, max_mbps = 0, packetization_mode = 1, max_rcmd_nalu = 0, b=4000
Unknown H.264 profile signaled_level 52
Answer call without going to queue 1st:
Requested H264 Codec: profile_level_id = 51, max_fs = 0, max_br = 0, max_mbps = 0, packetization_mode = 1, max_rcmd_nalu = 0, b=19904
Explicit Requested H264 Codec: profile_level_id = 51, max_fs = 36864, max_br = 240000, max_mbps = 983040, packetization_mode = 1, max_rcmd_nalu = 0
We found no video from agent to client using Jabber Web SDK with going to queue 1st, Is it possible to set Requested H264 codec profile_level_id in Jabber Web SDK ? or any other solution about this issue ?
