IETF-54draft-ietf-sipping-service-examples-02.txt1 Open Issues in SIP Service Examples Recent...

4
IETF-54 draft-ietf-sipping-service-exam ples-02.txt 1 Open Issues in SIP Service Examples Recent 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)

Transcript of IETF-54draft-ietf-sipping-service-examples-02.txt1 Open Issues in SIP Service Examples Recent...

Page 1: IETF-54draft-ietf-sipping-service-examples-02.txt1 Open Issues in SIP Service Examples Recent Changes Added 2-party to 3-party conversion –Uses a URI to.

IETF-54 draft-ietf-sipping-service-examples-02.txt 1

Open Issues in SIP Service Examples

Recent 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)

Page 2: IETF-54draft-ietf-sipping-service-examples-02.txt1 Open Issues in SIP Service Examples Recent Changes Added 2-party to 3-party conversion –Uses a URI to.

IETF-54 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:– [email protected]

Page 3: IETF-54draft-ietf-sipping-service-examples-02.txt1 Open Issues in SIP Service Examples Recent Changes Added 2-party to 3-party conversion –Uses a URI to.

IETF-54 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 |<============>| | |<-------------| |

Page 4: IETF-54draft-ietf-sipping-service-examples-02.txt1 Open Issues in SIP Service Examples Recent Changes Added 2-party to 3-party conversion –Uses a URI to.

IETF-54 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 | | | |<---------------| | |