<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to support-requests</title><link>https://sourceforge.net/p/tipcon1/support-requests/</link><description>Recent changes to support-requests</description><atom:link href="https://sourceforge.net/p/tipcon1/support-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 18 Jan 2013 15:56:17 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/tipcon1/support-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>SSRC mismatch between RTP and RTCP?</title><link>https://sourceforge.net/p/tipcon1/support-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Attached is a wireshark capture which appears to demonstrate that the SSRC values contained in RTP packets do not match any SSRC value advertised in the source description packets in RTCP. This prevents me from displaying user-friendly participant information without relying on SIP. I note that two instances of TipCon1 are able to provide each others' friendly names but I suspect that they are using the SIP headers.&lt;br /&gt;
I content that the SSRCs in RTP should match the SSRCs in the source description messages. Please comment.&lt;br /&gt;
Regards&lt;br /&gt;
Matt&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matthew Daughtrey</dc:creator><pubDate>Fri, 18 Jan 2013 15:56:17 -0000</pubDate><guid>https://sourceforge.net0a56376918f20c0e5b61240190ab966e5695bb1c</guid></item></channel></rss>