[asterisk-commits] oej: branch oej/pinefrog-1.4 r239562 - /team/oej/pinefrog-1.4/

[SVN commits to the Asterisk project]

Author: oej
Date: Tue Jan 12 13:25:40 2010
New Revision: 239562

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=239562
Log:
Adding documentation of what's done and some new todo items for this branch.

View this file at
http://svnview.digium.com/svn/asterisk/team/oej/pinefrog-1.4/README.pinefrog-rtcp?revision=237655

Feedback to oej at edvina.net


Modified:
    team/oej/pinefrog-1.4/README.pinefrog-rtcp

Modified: team/oej/pinefrog-1.4/README.pinefrog-rtcp
URL: http://svnview.digium.com/svn/asterisk/team/oej/pinefrog-1.4/README.pinefrog-rtcp?view=diff&rev=239562&r1=239561&r2=239562
==============================================================================
--- team/oej/pinefrog-1.4/README.pinefrog-rtcp (original)
+++ team/oej/pinefrog-1.4/README.pinefrog-rtcp Tue Jan 12 13:25:40 2010
@@ -1,7 +1,5 @@
 Olle E. Johansson
 oej at edvina.net
-
-
 
 
 
@@ -36,13 +34,36 @@
 - It seems to mix sender and receiver reports, thus mixing data from two streams 
     - when does this happen, if at all?
 
+RTCP and NAT
+------------
+I suspect that RTCP doesn't traverse NAT very well in our implementation. For RTP,
+we start with sending media to probe NAT. I've added emtpy RTCP RR+SDES CNAME packets
+to start probing a NAT (if Asterisk is behind a NAT). I am afraid that very few devices
+do that early on.
+The idea is (like RTP)
+ - Send a few RTCP packets in the start of the session.
+ - The receiver can then apply symmetric RTCP and start sending to the NAT outside port
+   that we're sending from and we'll get their packets.
+
 Todo
 ----
-- Add support of outbound and inbound SDES. The SDES includes a stream identifier, CNAME. 
-  When this changes, we have a different stream and need to restart the stats.
+- When CNAME changes, we have a different stream and need to restart the stats.
   Should we add ability to produce multiple RTCP reports for one "call" and aggregate them?
   The different parts might have different properties.
 - Check RTCP support for the p2p RTP bridge - today it doesn't work properly.
+- Add timed manager events during a call (once a minute or so)
+- Document realtime storage format
+- Add support of RTCP goodbye
+
+Done
+----
+- Add support of outbound and inbound SDES. The SDES includes a stream identifier, CNAME. 
+- Add support of outbound SDES end
+- Add manager events at end-of call
+- Add realtime storage of RTCP reports
+- Added more information to RTCP debug
+- Added more data aggregation to ast_rtcp structure (from svn trunk really)
+
 
 Ideas and thoughts for the future
 ---------------------------------