This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Last revision Both sides next revision | ||
devel:irc-meetings:2012b [2012/11/22 16:09] pd [Agenda] |
devel:irc-meetings:2012b [2012/11/22 17:10] pd [Agenda] |
||
---|---|---|---|
Line 48: | Line 48: | ||
* rtpproxy: can only bind to two networks - if you have lots of networks to bridge between you can end up with many rtpproxy instances | * rtpproxy: can only bind to two networks - if you have lots of networks to bridge between you can end up with many rtpproxy instances | ||
* rtpproxy: support for failover between proxies (media session surviving server failure) | * rtpproxy: support for failover between proxies (media session surviving server failure) | ||
- | * rtpproxy: RTP/SAVPF to RTP/AVP interworking support | + | * rtpproxy: RTP/SAVPF to RTP/AVP interworking support |
* rtpproxy: STUN and TURN server support (so can be used by client or server) | * rtpproxy: STUN and TURN server support (so can be used by client or server) | ||
+ | * rtpproxy: Handle ICE candidate lines (for WebRTC) | ||
* (pd) OMA PAL (Presence Access Layer) module? | * (pd) OMA PAL (Presence Access Layer) module? | ||
* complements OMA presence SIMPLE (same internal data structures) but uses more efficient messaging based around " | * complements OMA presence SIMPLE (same internal data structures) but uses more efficient messaging based around " |