1 / 12

draft-miniero-mediactrl-escs-00.txt

draft-miniero-mediactrl-escs-00.txt. Alessandro Amirante Tobia Castaldi Lorenzo Miniero Simon Pietro Romano (University of Napoli Federico II). Session Control Protocol (SIP) Control Framework (ESCS/SCFW) Call Flow Examples.

joshua-savage
Download Presentation

draft-miniero-mediactrl-escs-00.txt

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. draft-miniero-mediactrl-escs-00.txt Alessandro Amirante Tobia Castaldi Lorenzo Miniero Simon Pietro Romano (University of Napoli Federico II)

  2. Session Control Protocol (SIP) Control Framework (ESCS/SCFW) Call Flow Examples • This document provides a number of Media Server Control Framework call flows • It is meant as a BCP document conceived to help the development of the framework specification with a practical approach • All the flow scenarios come from direct implementation experience, which can help fix potential drawbacks and/or issues emerging in the protocol Univeristy of Napoli - mediactrl WG, 70th IETF meeting, Vancouver, Dec. 3rd 2007

  3. A Practical Approach • The document embraces a practical approach by providing: • State Diagrams of the framework protocol (both AS and MS perspectives); • Some implementation-oriented considerations that come out of the specification analysis. • Many real-life scenarios are considered in the call flows, and diagrams with different perspectives are included Univeristy of Napoli - mediactrl WG, 70th IETF meeting, Vancouver, Dec. 3rd 2007

  4. Showed at the demo! Call Flows and Diagrams • Control Channel Establishment • COMEDIA-based negotiation • SYNCH framework transaction • Use Case Scenarios and Examples • Echo Test • Direct Echo Test • Echo Test based on Recording • Phone Call • Direct Connection • Conference-based Approach • Conferencing • Simple Bridging • Rich Conference Scenario • Coaching Scenario • Sidebars • Others? Univeristy of Napoli - mediactrl WG, 70th IETF meeting, Vancouver, Dec. 3rd 2007

  5. CONTROL / - CONTROL PENDING API 202 / 202 CONTROL RECEIVED IDLE / TERMINATE API 200 / 200 API Error / Error API PENDING / REPORT PENDING 200 / - Media Server perspective PENDING SENT WAITING FOR LAST 200 API TERMINATE / REPORT TERMINATE 200 / - API TERMINATE / REPORT TERMINATE PENDING CONFIRMED API UPDATE / REPORT UPDATE UPDATE CONFIRMED UPDATE SENT API UPDATE / REPORT UPDATE 200 / -

  6. Apllication Server perspective 202 / - CONTROL SENT 202 RECEIVED API CONTROL / send CONTROL REPORT PENDING / send 200 200 / - IDLE / TERMINATE PENDING Error / Error REPORT TERMINATE / send 200 UPDATE REPORT UPDATE / send 200 REPORT TERMINATE / send 200 REPORT UPDATE / send 200

  7. Steady-state operation SIP signalling Control Framework signalling RTP data University of Napoli ApplicationServer (Wesip) OpenSER SIP messages SIP messages (High speed binary connector) SIP messages Control Channel User RTP communication University of Napoli Media Server Univeristy of Napoli - mediactrl WG, 70th IETF meeting, Vancouver, Dec. 3rd 2007

  8. (6) 200 OK with COMEDIA • SIP INVITE • with COMEDIA (7) ACK (4) SIP 100 TRYING (10) SYNCH (Dialog-ID, etc.) (9) TCP connect (Control Channel) (11) 200 OK Control channel (2) SIP INVITE with COMEDIA (5) 200 OK with COMEDIA (3) SIP 100 TRYING (8) ACK SIP signalling Control Framework signalling TCP University of Napoli ApplicationServer (Wesip) Control channel setup OpenSER User University of Napoli Media Server Univeristy of Napoli - mediactrl WG, 70th IETF meeting, Vancouver, Dec. 3rd 2007

  9. (4) 180 Ringing (14) ACK (1) SIP INVITE (13) 200 OK (2) SIP INVITE (11) 200 OK (8) 100 Trying (15) ACK (3) 180 Ringing (12) 200 OK (5) INVITE (3PCC) (16) ACK (6) INVITE (3PCC) (7) 100 Trying (10) 200 OK (17) ACK (9) SDP negotiation with UAC + tags and labels mapping SIP signalling Third Party Call Control (3PCC) Control Framework signalling RTP data University of Napoli ApplicationServer (Wesip) OpenSER User RTP media streams flowing University of Napoli Media Server Univeristy of Napoli - mediactrl WG, 70th IETF meeting, Vancouver, Dec. 3rd 2007

  10. (2) 202 (5) 200 OK (3) REPORT/PENDING (7) 200 OK (6) REPORT/TERMINATE • CONTROL • (join UAC to itself) (4) “self-join” UAC SIP signalling Direct Echo example: self connection Control Framework signalling RTP data University of Napoli ApplicationServer (Wesip) OpenSER User RTP media streams flowing The UAC is echoed back everything University of Napoli Media Server Univeristy of Napoli - mediactrl WG, 70th IETF meeting, Vancouver, Dec. 3rd 2007

  11. Considerations • Is the 202 message really necessary? • Always followed by a REPORT(pending) • Ambiguity between notify/update possible states in REPORT messages • Should notify/update events be possible *after* a terminate? • If only the 200 error code can carry a body, how are package-specific errors notified? • …and others, mostly related to each specific control package • WIP… Univeristy of Napoli - mediactrl WG, 70th IETF meeting, Vancouver, Dec. 3rd 2007

  12. Discussion • Is the document of interest to the WG? • Are the provided scenarios enough? Are they well described and analyzed? • Should security considerations be in the scope of this document, or should they just be referenced from the specification documents? • What else is needed and/or needs to be fixed? Univeristy of Napoli - mediactrl WG, 70th IETF meeting, Vancouver, Dec. 3rd 2007

More Related