SIP Call Package Jonathan Rosenberg dynamicsoft. Three Separate Pieces Call Leg State Package Conference Package To-Join/To-Replace.

Slides:



Advertisements
Similar presentations
1 © 2001, Cisco Systems, Inc. All rights reserved. © 2004, Cisco Systems, Inc. All rights reserved. Location Conveyance in SIP draft-ietf-sipping-location-requirements-02.
Advertisements

SIP, Presence and Instant Messaging
Presence and IM as SIP Services Jonathan Rosenberg Chief Scientist.
Fall IM 2000 Evfolution of Presence Based Networks Evolution of Presence Based Networks Jonathan Rosenberg Chief Scientist.
An Application Component Architecture for SIP Jonathan Rosenberg Chief Scientist.
Fall IM2000 Industry Perspective Presence: The Best Thing that Ever Happened to Voice Jonathan Rosenberg Chief Scientist.
SIP and Instant Messaging. SIP Summit SIP and Instant Messaging What Does Presence Have to Do With SIP? How to Deliver.
IMPP Update: SIP. Spring PIM 2001 IMPP Update SIMPLE Group SIMPLE = SIP for Instant Messaging Leveraging Extensions BoF Session Held.
dynamicsoft Inc. Proprietary VON Developers Conference 1/19/00 C O N N E C T I N G T H E W O R L D W I T H A P P L I C A T I O N S.
Fall IM 2000 Introduction to SIP Jonathan Rosenberg Chief Scientist.
SIMPLE Open Issues Jonathan Rosenberg dynamicsoft IETF 52.
IM May 24, 2000 Introduction to SIP Jonathan Rosenberg Chief Scientist.
VON Europe /19/00 SIP and the Future of VON Protocols SIP and the Future of VON Protocols: Presence and IM Jonathan Rosenberg.
Fall VoN 2000 SIP for IP Communications Jonathan Rosenberg Chief Scientist.
Insert Tradeshow or Event Name -- Date Insert Presentation Title Trends in Instant Messaging and Telephony Jonathan Rosenberg Chief.
Rfc4474bis-01 IETF 89 (London) STIR WG Jon & Cullen.
SIP Working Group Jonathan Rosenberg dynamicsoft.
SIP Working Group Stuff Jonathan Rosenberg dynamicsoft.
Extended REFER draft-olson-sipping-refer-extensions-01 draft-mahy-sip-remote-cc-01 François Audet
1 CPCP Hisham Khartabil XCON WG IETF 60, San Diego 2 nd August, 2004
XML Configuration Access Protocol (XCAP) Jonathan Rosenberg dynamicsoft.
SIPPING 5/6/02 Meetingdraft-ietf-sipping-service-examples-01.txt1 Open Issues in SIP Service Examples Recent Changes Added SUBSCRIBE/NOTIFY using Dialog.
A Generic Event Notification System Using XML and SIP Knarig Arabshian and Henning Schulzrinne Department of Computer Science Columbia University
Aspire Vertical Markets Real Estate Office. Real Estate.
Internet Telephony Helen J. Wang Network Reading Group, Jan 27, 99 Acknowledgement: Jimmy, Bhaskar.
1 Extending SIP Speaker: Hsuan-Ming Chen Adviser: Ho-Ting Wu Date: 2005/04/26.
What is a SIP Trunk Anyway?!? Jonathan Rosenberg Cisco.
Rohan Mahy draft-ietf-sip-join and Semantics of REFER.
1 SIP WG meeting 73rd IETF - Minneapolis, MN, USA November, 2008 Return Routability Check draft-kuthan-sip-derive-00 Jiri
Session Initiation Protocol Tutorial Ronen Ben-Yossef VP of Products - RADCOM
A SIP Call Control Model draft-mahy-sip-cc-models-00.txt Rohan Mahy
SIP Action Referral Rifaat Shekh-Yusef Cullen Jennings Alan Johnston Francois Audet 1 IETF 80, SPLICES WG, Prague March 29, 2011.
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.
Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) April 2004, RFC3725 Author(s): J. Rosenberg, J. Peterson,
Draft-audet-sipping-feature-ref Feature Referral in the Session Initiation Protocol (SIP) draft-audet-sipping-feature-ref-00 François Audet -
1 © NOKIA 1999 FILENAMs.PPT/ DATE / NN SIP Service Architecture Markus Isomäki Nokia Research Center.
@ IETF 68. Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement.
Explicit Subscriptions for REFER draft-sparks-sipcore-refer-explicit-subscription-00 SIPCORE – IETF90 Robert Sparks.
SIPPING IETF 57 Jonathan Rosenberg dynamicsoft.
Data Manipulation Jonathan Rosenberg dynamicsoft.
App Interaction Framework Jonathan Rosenberg dynamicsoft.
SIP INFO Event Framework (draft-kaplan-sip-info-events-00) Hadriel Kaplan Christer Holmberg 70th IETF, Vancouver, Canada.
SIMPLE Drafts Jonathan Rosenberg dynamicsoft. Presence List Changes Terminology change Presence List Information Data Format –Provides version, full/partial.
SIP and SIPPING WGsMay, IETF Interim Meeting Orit levin Conferencing Requirements for SIP Based Applications.
Making SIP NAT Friendly Jonathan Rosenberg dynamicsoft.
March 25, 2009SIPPING WG IETF-741 A Batch Notification Extension for the Session Initiation Protocol (SIP) draft-johnston-sipping-batch-notify-00 Alan.
SIP WG Open Issues IETF 50 Jonathan Rosenberg dynamicsoft.
Interactive Connectivity Establishment : ICE
Open issues from SIP list Jonathan Rosenberg dynamicsoft.
SIP PUBLISH Method Jonathan Rosenberg dynamicsoft.
SIP file directory draft-garcia-sipping-file-sharing-framework-00.txt draft-garcia-sipping-file-event-package-00.txt draft-garcia-sipping-file-desc-pidf-00.txt.
OPTIMIZATION OF SIGNALING TRAFFIC IN CENTRALIZED CONFERENCES USING SIP Submitted by D.NEHRU S.JAYABALAN B.Tech IT II Year.
The Session Initiation Protocol - SIP
SIPPING Drafts Jonathan Rosenberg dynamicsoft. Conferencing Package Issues Only one – scope Depends on broader work in conferencing May include –Participant.
Andrew Allen ROUTING OUT OF DIALOG REQUESTS draft-allen-dispatch-routing-out-of-dialog-request-01 Dispatch IETF 92 March 23 rd 2015.
SIP Extension Changes Jonathan Rosenberg dynamicsoft IETF 52.
SIP wg Items Jonathan Rosenberg dynamicsoft Caller Preferences: Changes Discussion of Redirects –Previous draft only proxy –Nothing different for redirect.
Narragansett Council Online Registration
RTCP Feedback Message for Image Control
Jonathan Rosenberg dynamicsoft
ECRIT Interim: SIP Location Conveyance
SIP Configuration Issues: IETF 57, SIPPING
App Interaction Framework
Transcoding Framework
Request-URI Param Delivery
Jonathan Rosenberg dynamicsoft
SIP Conferencing Requirements
The new bis.
Event Notification in SIP SUBSCRIBE and NOTIFY and an example service
IETF SIP Interim Meeting, Feb. 2001
Presentation transcript:

SIP Call Package Jonathan Rosenberg dynamicsoft

Three Separate Pieces Call Leg State Package Conference Package To-Join/To-Replace

Call Leg Package Allows a user to subscribe to the call leg state of another user –R-URI is user to subscribe to –Get back notifications on all active call legs at that user Notifications sent on messages that change state –Provisional/final responses –BYE Notification data includes –Status of the leg (in terms of response codes) –Optional leg params –Join/Replace URLs (later)

Whats it useful for? Single Line Extension –Phones in the group can know whether the calls answered by other phones are still active or not ACD –Trainer can find out whether trainees are in a call, to join it Automatic Callback

Conferencing Package Assumes a centralized manager for conferences –3-way calling (end system) –Dial-in, dial-out SUBSCRIBE to the “conference URL” Notifications on –Joins/departures –Floor control changes –Failed dialouts Notification data includes: –List of users and their status –Replaces URL (later) –Floor control state

Whats it useful for? Initiating side-bars with conference members –RTCP id not sufficient Web monitor of conference states

Join and Replace URL There is an asymmetry in joining and replacing legs –Join is implicit, based on the URL someone has handed you (or you can construct) –Replace is explicit, based on a header To transition from 2-party call to conference –Allocate conference URL –REFER everyone to it –BUT – how do you know second party isn’t ALREADY a conference URL? First idea –Unify join/replaces by using the same mechanism for both –Follow idea that interpretation of URL is conveyed separate from URL, interpreted by server that sent it –URL syntax at discretion of server

To-Join and To-Replace INVITE and 2xx both contain To-Join and To- Replace headers To-Join contains a URL, which if used, joins to that call leg –At discretion of UA how that’s done – REFER into bridge, local mix.. To-Replace contains a URL, which if used, replaces that call leg INV To-Replace:X 2xx ACK Hands To-Replace URL INV X 200 ACK BYE 200

Some Benefits URL can encode arbitrary data of use to server –Timestamps, authorization data, etc. URL can point to somewhere besides UA –Join URL goes to conference server, which actively pulls user in –Can be directly routable to THAT UA (solves consultation transfer problem) Solves problem of knowing whether you need to get a conference server or not

Discussion Points Clearly Replace URL is an alternate to replaces header To-Join makes more sense than To-Replace –You’re not really joining a leg, you’re joining a “conversation space” which is broader than a leg But you replace a leg –Sending Join requests to a different host makes more sense than replace URL in To-Join is what you would SUBSCRIBE to for conference package Main benefit of To- Replace is being able to use a URL that routes to UA

What do we want to do? Seems a key part of call control framework Completes the picture Picture of call control is: –Finding out about calls and conferences –Joining, replacing, creating, moving call legs and conferences We now have all of these pieces Proposal is to keep Replaces header, drop To-Replace, but consider To-Join