RE: [Sip] Boss-Secretary functionalities over SIP

"Paul Pepper" <paul.pepper@citel.com> Wed, 17 November 2004 16:39 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16818 for <sip-web-archive@ietf.org>; Wed, 17 Nov 2004 11:39:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CUSsb-0005Wv-7G for sip-web-archive@ietf.org; Wed, 17 Nov 2004 11:42:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUSh8-0000hW-DW; Wed, 17 Nov 2004 11:30:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CUSdH-00083K-Sh for sip@megatron.ietf.org; Wed, 17 Nov 2004 11:26:12 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15435 for <sip@ietf.org>; Wed, 17 Nov 2004 11:26:08 -0500 (EST)
Received: from firewall.citel.com ([62.190.107.60] helo=ivor.citel.com) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CUSfi-00055m-Ks for sip@ietf.org; Wed, 17 Nov 2004 11:28:43 -0500
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
Subject: RE: [Sip] Boss-Secretary functionalities over SIP
Date: Wed, 17 Nov 2004 16:21:26 -0000
Message-ID: <CD9775120D600F43B9C50329395E9DB6178DAB@ivor.citel.com>
Thread-Topic: [Sip] Boss-Secretary functionalities over SIP
Thread-Index: AcTMAoqzur8tDBP3QFy3MLW2H3gLSQAuVuKw
From: Paul Pepper <paul.pepper@citel.com>
To: "Pianigiani, Jacopo (Jacopo)" <jpianigiani@lucent.com>, sip@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: quoted-printable
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Content-Transfer-Encoding: quoted-printable

Hi,

There are various ways of offering a 'Boss-Secretary' feature. The
simplest, which we can call shared-line-monitor, would involve using the
dialog event package (see
http://www.ietf.org/proceedings/04aug/I-D/draft-ietf-sipping-dialog-pack
age-04.txt) to show the status of the monitored (the boss's) line. The
SIP service examples ID
(http://www.ietf.org/internet-drafts/draft-ietf-sipping-service-examples
-07.txt) takes this a step further in its 'Single Line Extension'
example, by letting another user join a monitored call.

A more popular requirement, in my experience, permits shared lines/AORs
to be 'seized' by any one of the users that have registered against that
AOR. Seizing a line effectively involves obtaining a mutex on the shared
line resource so that no other user can make a call out on that instance
of the AOR. This has a number of benefits when it comes to managing
calls on the shared line. The ID 'Implementing Bridged Line Appearances
Using Session Initiation Protocol' makes use of the dialog event package
to provide the line seize feature
(http://ietfreport.isoc.org/all-ids/draft-anil-sipping-bla-01.txt) -
this draft has now expired, but an updated version should be out soon.

Paul.

-----Original Message-----
From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On Behalf Of
Pianigiani, Jacopo (Jacopo)
Sent: Tuesday, November 16, 2004 5:10 PM
To: 'sip@ietf.org'
Subject: [Sip] Boss-Secretary functionalities over SIP


Hi all,
I am looking for an overview on SIP of the classic PABX Boss-Secretary
functionality from the high level call flow perspective.
Does anyone know where I could find this ? 
thanks in advance and kind regards

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip