Hello, >From RFC 3550, sec. 5.3.1:
"If the X bit in the RTP header is one, a variable-length header extension MUST be appended to the RTP header, following the CSRC list if present." So, CSRC list first, then extension header :-). Best regards, Peter On Sat, Apr 2, 2011 at 4:05 PM, Brez Borland <[email protected]> wrote: > Hello folks, > > Apologies if this should not go onto this list, please suggest where else > should I look for advice in this case. > > Below is the snip from the rfc3550, which is a bit confusing. Fields X and > CC specify that, if set, they MUST follow the RTP header. My question is, > if > both X and CC are present which of these must take precedence in following > RTP header. > > ---------------------------------------------------------- > > 5.1 RTP Fixed Header Fields: > > ...... > > extension (X): 1 bit > > * If the extension bit is set, the fixed header MUST be followed > by exactly one header extension*, with a format defined in Section 5.3.1. > > CSRC count (CC): 4 bits > > The CSRC count contains *the number of CSRC identifiers that > follow the fixed header*. > > ---------------------------------------------------------- > > > Input is greatly appreciated. Let me know if clarification of the question > is needed. > > > Thank you, > > Regards, > > Brez > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
