Blink uses this for Screen sharing using VNC protocol: m=application 2855 TCP/TLS/MSRP * a=path:msrps://192.168.8.3:2855/52e5cab14755380a6d14;tcp a=accept-types:application/x-rfb a=setup:active a=rfbsetup:active
Regards, Adrian On 18 Sep 2014, at 17:15, Dale R. Worley <wor...@alum.mit.edu> wrote: > I'm making up a list of the media types that are carried using SIP, or > rather, that are described in the SDP carried in real SIP systems. > > The list I have so far is: > > - m=audio > > - m=video > > - MSRP, for message-oriented IM and file transfer: > m=message 7394 TCP/MSRP * > > - Real-time text using T.140 with redundancy: > m=text 11000 RTP/AVP 100 98 > a=rtpmap:98 t140/1000 > a=rtpmap:100 red/1000 > a=fmtp:100 98/98/98 > > - Fax: > RFC 3362: > m=image 1000 TCP t38 > > RFC 4612: > m=audio 6800 RTP/AVP 0 98 > a=rtpmap:98 t38/8000 > a=fmtp:98 T38FaxVersion=2;T38FaxRateManagement=transferredTCF > > - Whiteboarding > I've seen proposals to use SDP to carry TCP connection information > so that a whiteboarding application (including a web browser) can > connect to a whiteboarding server, using SDP like this: > m=application 54111 TCP t38 > a=setup:passive > a=connection:new > > Does anyone know of any others? > > Thanks, > > Dale > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > -- Adrian
_______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors