Subject: [MMUSIC] SIP desktop sharing with draft-garcia-mmusic-sdp-collaboration

From: Adrian Georgescu <[email-masked]>
Date: Mon, 26 Jan 2009 17:03:59 +0100

Hello,

We have successfully implemented desktop sharing application using a  
variation of draft-garcia-mmusic-sdp-collaboration namely using an  
MSRP session instead of pure TCP. Here is the relevant negotiated SDP:

INVITE sip:[email-masked] SIP/2.0
Record-Route: <sip:81.23.228.129;lr=on;ftag=IjiXUJuaiN03As3HGxf0osjkibdnUtd2;did=919.7c6dbad4 
Via: SIP/2.0/UDP 81.23.228.129;branch=z9hG4bK7ec3.24ae5eb1.0
Via: SIP/2.0/UDP  
192.168.1.6 
:51891;received=80.101.96.20;rport=51891;branch=z9hG4bKPjcZPkzRl- 
dkYHaxeakmQLu8i5TDxIARL6
Max-Forwards: 68
From: "Adrian G." <sip:31208005169@ag- 
projects.com>;tag=IjiXUJuaiN03As3HGxf0osjkibdnUtd2
To: sip:[email-masked]
Contact: <sip:[email-masked]:51891;transport=udp>
Call-ID: M64kmnwHHuWtiVQl.QaP0svHi.rhI0-N
CSeq: 13415 INVITE
Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE,  
MESSAGE
Supported: 100rel
User-Agent: sip2sip-0.4.0-pjsip-1.0.1-r2427
Content-Type: application/sdp
Content-Length: 281
Thor-Scope: authenticate
Thor-Origin: sip:80.101.96.20:51891

v=0
o=- 3441959219 3441959219 IN IP4 192.168.1.6
s=
c=IN IP4 192.168.1.6
t=0 0
m=application 12345 TCP/TLS/MSRP/RFB *
a=path:msrps://192.168.1.6:12345/Oj0BcOEf4sim;tcp
a=accept-types:message/cpim application/x-rfb
a=accept-wrapped-types:application/x-rfb
a=setup:active

SIP/2.0 200 OK
Via: SIP/2.0/UDP 85.17.186.7;branch=z9hG4bK4ec3.220d6d27.0
Via: SIP/2.0/UDP 81.23.228.129;branch=z9hG4bK4ec3.cb13ac42.0
Via: SIP/2.0/UDP  
192.168.1.6 
: 
51891 
;rport=51891;received=80.101.96.20;branch=z9hG4bKPjpf7mDBJxwkWa5hlptKm- 
Bozt9IGYm01Y
Record-Route: <sip:81.23.228.150;lr;ftag=IjiXUJuaiN03As3HGxf0osjkibdnUtd2;did=919.8a3da7b5 
Record-Route: <sip:85.17.186.7;lr;ftag=IjiXUJuaiN03As3HGxf0osjkibdnUtd2;did=919.98f40fd4 
Record-Route: <sip:81.23.228.129;lr;ftag=IjiXUJuaiN03As3HGxf0osjkibdnUtd2;did=919.8c6dbad4 
Call-ID: M64kmnwHHuWtiVQl.QaP0svHi.rhI0-N
From: "Adrian G." <sip:31208005169@ag- 
projects.com>;tag=IjiXUJuaiN03As3HGxf0osjkibdnUtd2
To: <sip:[email-masked]>;tag=Qv2lE9YdxHGSmy1O9b534j8jhdKIoErw
CSeq: 13416 INVITE
Contact: <sip:[email-masked]:34206>
Allow: SUBSCRIBE, NOTIFY, PRACK, INVITE, ACK, BYE, CANCEL, UPDATE,  
MESSAGE
Supported: 100rel
User-Agent: ag-projects/sipclient-0.4.0-pjsip-1.0.1-r2427
Content-Type: application/sdp
Content-Length: 393

v=0
o=- 3441959219 3441959220 IN IP4 192.168.178.33
s=
c=IN IP4 192.168.178.33
t=0 0
m=application 54990 TCP/TLS/MSRP/RFB *
a=path:msrps://node03.dns-hosting.info:2855/6dm+f 
+uC6mgbryTjbHVGEDEyMzI5NzA0MjAuMDU0OjgyLjk1LjE0MS4xMjc=;tcp msrps:// 
192.168.178.33:54990/WSucWUOgCOKg;tcp
a=accept-types:message/cpim application/x-rfb
a=accept-wrapped-types:application/x-rfb
a=setup:passive

The complete SIP session negotiation (click on each message to expand  
its content) is here:

https://secure.dns-hosting.info/CDRTool/sip_trace.phtml?cdr_source=sip_trace_thor&callid=M64kmnwHHuWtiVQl.QaP0svHi.rhI0-N&fromtag=IjiXUJuaiN03As3HGxf0osjkibdnUtd2&totag=Qv2lE9YdxHGSmy1O9b534j8jhdKIoErw&proxyIP=85.17.186.7&public=1

More information and the software is available at:

http://lists.ag-projects.com/mailman/listinfo/sipclient

I am wondering if it makes sense to mention the MSRP/TLS  transport as  
a valid option for negotiating/transporting in the draft.

Kind regards,
Adrian Georgescu

_______________________________________________
mmusic mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/mmusic