h264 packetization mode for FUA

空扰寡人 提交于 2019-12-03 16:44:28

FUA is used in packetization modes 1 & 2. packetization-mode defaults to 0 (single-NAL mode); if both sides agree to modes 1 or 2 you will typically see an FU-A when a NAL exceeds the UDP MTU or configured maximum packet size.

The packetization/de-packetization layer should take NALs and generate FU-A's when needed, and on reception take a series of FU-A's and reassemble a NAL to feed to the decoder.

See RFC 3984 and RFC 3984bis (of which I'm an author).

A B2BUA should not accept or offer a packetization-mode it's not ready to process, though it may be simply passing through the offer/answer from the other UA.

Also note that (if compliant with RFC 3984) a UA must support packetization-mode 0, though it's not required to offer it on an INVITE.

I'm not sure if I understand your question correctly, but FU-A is not a packetization mode, it just signals that the NAL unit is a Fragmentation Nal Unit i.e. a NAL unit is fragmented over several RTP packets. RFC3984 table 3 shows that NAL FU-A can only be used in the interleaved and non-interleaved packetization modes (modes 1 and 2) i.e. not in single Nal Unit mode (mode 0).

As for encoder/decoder support: if the SDP signals packetization mode 1 or 2, it means that there might be FU-As in the RTP stream. This won't affect the decoder though RFC3894 section 7.1: "If a decapsulated packet is an FU-A, all the fragments of the fragmented NAL unit are concatenated and passed to the decoder."

I don't understand the last part of your question relating to the SIP B2BUAs, the SDP signals packetization modes and based on that the RTP receiver must be able to handle the different NAL unit types that are specified in RFC3984.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!