RTCPCOMPOUNDHANDLER_NACKPACKET(3)

πŸ“¦
version 2.0.9 Β· 4 versions
, in debian trixie, ubuntu noble, ubuntu questing

πŸ’– NAME πŸ’–

RTCPCompoundHandler::NACKPacket β€” the struct for Negative ACKnowledgements (NACK) RTCP packets. it's giving "hey bestie, I noticed you missed some packets" energy 🫢


✨ SYNOPSIS ✨

#include <rtcppkt.h>

πŸŽ€ Public Attributes πŸŽ€

  • uint32 ssrc β€” the ssrc identifier of source. like, whose packets are we even talking about πŸ’…
  • uint16 fsn β€” First Sequence Number lost. the very first one that ghosted us 😭
  • uint16 blp β€” Bitmask of following Lost Packets. the rest of the missing squad, encoded as bits ✨

🌸 Detailed Description 🌸

okay so, RTCPCompoundHandler::NACKPacket is a Struct for Negative ACKnowledgements (NACK) RTCP packet.

it's Specific for H.261 sessions (see RFC 2032). no cap, that's the whole vibe β€” this is the H.261-specific situation right here πŸ“Ό


πŸ¦‹ Member Data Documentation πŸ¦‹

πŸ’œ uint16 RTCPCompoundHandler::NACKPacket::blp

Bitmask of following Lost Packets. every bit is a little "you missed this one too bestie" πŸ₯Ί

πŸ’œ uint16 RTCPCompoundHandler::NACKPacket::fsn

First Sequence Number lost. the opening act of the whole lost-packets saga πŸ‘‘

πŸ’œ uint32 RTCPCompoundHandler::NACKPacket::ssrc

ssrc identifier of source. main character ID, fr fr ⭐


πŸ‘‘ Author πŸ‘‘

Generated automatically by Doxygen for ccRTP from the source code. (yes the docs wrote themselves, iconic behaviour honestly πŸ’…βœ¨)


that's the whole page, bestie β€” go forth and NACK responsibly πŸ’–πŸ¦‹πŸŽ€ this has been your girl, signing off from the ccRTP RTCPCompou...:NACKPacket(3) page, Library Functions Manual, periodt 🌸🫢

πŸ“¦ where this page comes from