1 / 4

Open Issues in SIP Service Examples: Conference Management and Participant Transitions

This document outlines current open issues related to SIP (Session Initiation Protocol) services, specifically focusing on transitioning from two-party to three-party conference calls. Key updates include using URIs for identifying conferences and events, the necessary coordination between user agents and SIP bridges, and the need for better integration with the latest REFER specifications. Notable scenarios include user addition requests and admission processes. Further attention is required on single line extensions and including conference packages in ongoing flows.

neola
Télécharger la présentation

Open Issues in SIP Service Examples: Conference Management and Participant Transitions

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. Open Issues in SIP Service ExamplesRecent Changes • Added 2-party to 3-party conversion • Uses a URI to identify the conference and SIP Events • Scenarios • User is added by participant • User requests admission (joins) draft-ietf-sipping-service-examples-02.txt

  2. Open Issues • 2-Party to 3-Party transition • subscription/interaction between UA and bridge • use of Join/Fork? • discovery of conference URI • Single Line Extension • needs more attention • To Do: • align with latest REFER changes • include Conference Package in flow • Contact: • alan.johnston@wcom.com draft-ietf-sipping-service-examples-02.txt

  3. 2.9 3-way Conference – Third Party is Added User A User B Bridge User C | RTP | | | |<==============>| | | |INVITE (hold)/200/ACK | | |<---------------| | | | No RTP | INVITE/200/ACK | | |------------->| | | | RTP | | | |<============>| | | REFER Refer-To:Bridge/202 | | |<---------------| | | | INVITE/200/ACK | | |------------------------------>| | | RTP | | |<=============================>| | | NOTIFY/200 | | | |--------------->| | | | BYE/200 | | | |<---------------| | | | | REFER Refer-To:C/202 | | |------------->| | | | | INVITE/180/200/ACK | | |------------->| | | | RTP | | | NOTIFY/200 |<============>| | |<-------------| | draft-ietf-sipping-service-examples-02.txt

  4. 2.10 3-way Conference – Third Party Joins User A User B Bridge User C | | | | | RTP | | INVITE | |<==============>| |<-------------| | | | 180 | | | NOTIFY/200 |------------->| | |<-------------| | |INVITE (hold)/200/ACK | | |<---------------| | | | No RTP | INVITE/200/ACK | | |------------->| | | | RTP | | | |<============>| 200 OK | | | |------------->| | | | ACK | | | |<-------------| | | | RTP | | | NOTIFY/200 |<============>| | |<-------------| | | REFER Refer-To:Bridge/202 | | |<---------------| | | | INVITE/200/ACK | | |------------------------------>| | | RTP | | |<=============================>| | | NOTIFY/200 | | | |--------------->| | | | BYE/200 | | | |<---------------| | | draft-ietf-sipping-service-examples-02.txt

More Related