BFCP examples are:
m=application 50000 TCP/TLS/BFCP *
a=setup:passive
a=connection:new
a=fingerprint:SHA-1 \
4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
a=floorctrl:s-only
a=confid:4321
a=userid:1234
a=floorid:1 mstrm:10
a=floorid:2 mstrm:11
a=bfcpver:1
m=audio 50002 RTP/AVP 0
a=label:10
m=video 50004 RTP/AVP 31
a=label:11
m=application 50000 UDP/TLS/BFCP *
a=setup:actpass
a=fingerprint:SHA-1 \
4A:AD:B9:B1:3F:82:18:3B:54:02:12:DF:3E:5D:49:6B:19:E5:7C:AB
a=floorctrl:c-only s-only
a=confid:4321
a=userid:1234
a=floorid:1 mstrm:10
a=floorid:2 mstrm:11
a=bfcpver:2
m=audio 50002 RTP/AVP 0
a=label:10
m=video 50004 RTP/AVP 31
a=label:11
Cheers,
Charles
On 9/18/14, 1:15 PM, "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
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
