I figured out my own problem, I was misreading the bit order in the RTP message from the RFC 1889 spec. The network byte order being big endian was okay, but the bit order as outlined in their diagramed header is also in network bit order, so I misread a version 0 instead of a version 2.
Original Message ----------------------- Thanks for the reply, Actually, no the ATA is only configured to support G732.1 exclusively. I'm not sure exactly what the payload type is since I'm not sure how to unwrap the RTP packet and interpret the results. The RTP version is being returned as zero not as '2' as I would Original Message ----------------------- Is it returning a PT (payload type) header of 0? If so, then it is trying to use G.711. -----Original Message----- From: sipdev [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 30, 2003 12:03 AM To: Sip-implementors Subject: [Sip-implementors] (unrelated) SIP to ATA This isn't directly a ser question, but I'm tyring to talk to ATA 186 using G732.1 codec, and when I receive RTP data back I noticed that I'm getting 0 as the RTP version number (first byte value is 0x80). How do I communicate to this ATA using whatever RTP this is? Sorry for being ignorant on this but I'm puzzled as to what data this thing is actually sending over RTP. _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
