Distributed Multipoint Conferences draft-mark-sip-dmcs-00.txt Jeff.Mark@dialogic.com Kalon.Kelley@dialogic.com IETF 47: March 28, 2000
Overview � Resolve open issues with draft-ietf-mmusic-sip-cc-01 [Jun 1999] � Full meshes: admission into conference, rejected during join, status / version not needed � Alternate solution to “crossing invite” problem � Transfer: alternate implementation ideas. � Introduced new services � Merge: 2 full mesh 1 full mesh calls � Split: 1 full mesh 2 disjoint full mesh calls IETF 47: March 28, 2000 2
Add Party SIP Message Traffic B A 200 Admission Granted ACK INVITE C ACK 200 Fully Admitted 200 Admission Granted INVITE D INVITE B 1xx Seeking Admission ACK To: B To: D To: D Requested-By: A To: C To: B To: D Requested-By: A To: D To: C From: D To: C From: A From: A To: B From: A From: A From: D From: D From: D Call-ID: blue Also: A, B Call-ID: blue Call-ID: blue Call-ID: blue From: D Also: A, C From: D Call-ID: blue Call-ID: blue Also: B, C Status: 200=B Call-ID: blue Call-ID: blue Call-ID: blue Call-ID: blue C D SDP body SDP body SDP body SDP body SDP body SDP body � Three-way mesh call (A, B, C) � A wants to add D. IETF 47: March 28, 2000 3
Merge SIP Message Traffic B X X & Y gain admission to blue: Red to blue transition: The Replaces header in the INVITE X / Y INVITE Y To: X / Y � INVITE B / Requested-By: A “merge” invite instructs X & Y to � 200 Admission Granted (from B) To: Y From: A remove the AX & AY red call A From: X Call-ID: blue � INVITE C / Requested-By: A legs. Also: B, C Call-ID: blue � 200 Admission Granted (from C) C Y � ACK B / ACK C Replaces: A; call-id=red Also: A, B, C Replaces: X; call-id=red � 200 Fully Admitted (to A) / ACK Call-Disposition: merge; call-id=red Call-Disposition: merge; call-id=red � Two full mesh calls (blue & red) � A wants to merge red into blue. IETF 47: March 28, 2000 4
Split SIP Message Traffic A B INVITE C 200 OK INVITE B INVITE C 200 OK BYE D BYE D 200 OK To: D To: D To: C To: B Requested-By: A To: C To: C To: B From: A From: C From: A From: B To: C From: A From: A From: A Call-Id: blue Call-Id: blue Call-id: red Call-Id: red Call-id: red From: B Call-id: red Call-Id: red Call-id: red Also: C Also: B BYE D C D Also: A Replaces: A; call-id=blue Replaces: A; call-id=blue ACK ACK ACK To: D To: C Replaces: C; call-id=blue Call-Disposition: split; call-id=blue Call-Disposition: split; call-id=blue To: C To: B From: B From: A From: B Call-Disposition: split; call-id=blue From: A Call-Id: blue � One full mesh calls (blue) � A wants to split B,C → → red (ABC), blue (D) call. � D represents a group of other participants IETF 47: March 28, 2000 5
Summary of our approach � No new methods � Added / redefined some headers � Also, Replaces, Call-Disposition, Status, Rejected-By, Unresponsive � New response codes � 1xx Seeking Admission � 1yy Pending Request � 4ww Admission Failed � 4zz Colliding Request IETF 47: March 28, 2000 6
What’s Next � Interest in distributed full mesh scenarios? � Comments? IETF 47: March 28, 2000 7
Recommend
More recommend