IETF Logo Mail Archive

Re: [BLISS] Call-completion issue 1010: The event model

<R.Jesske@telekom.de> Tue, 20 July 2010 08:45 UTC

Return-Path: <R.Jesske@telekom.de>
X-Original-To: bliss@core3.amsl.com
Delivered-To: bliss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B43E3A67A4 for <bliss@core3.amsl.com>; Tue, 20 Jul 2010 01:45:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.32
X-Spam-Level:
X-Spam-Status: No, score=-2.32 tagged_above=-999 required=5 tests=[AWL=0.930, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2slhmdaV3S65 for <bliss@core3.amsl.com>; Tue, 20 Jul 2010 01:45:52 -0700 (PDT)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id 5FEC73A6A09 for <bliss@ietf.org>; Tue, 20 Jul 2010 01:45:52 -0700 (PDT)
Received: from s4de8psaans.blf.telekom.de (HELO s4de8psaans.mitte.t-com.de) ([10.151.180.168]) by tcmail71.telekom.de with ESMTP; 20 Jul 2010 10:46:03 +0200
Received: from S4DE8PSAAQB.mitte.t-com.de ([10.151.229.13]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675); Tue, 20 Jul 2010 10:46:02 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 20 Jul 2010 10:46:01 +0200
Message-ID: <9886E5FCA6D76549A3011068483A4BD4065E66AF@S4DE8PSAAQB.mitte.t-com.de>
In-Reply-To: <4C371EE5.1030200@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [BLISS] Call-completion issue 1010: The event model
Thread-Index: AcsfZ56+Z/Q2lguHRCaf37Ijiv9KNQIff/Wg
References: <CD5674C3CD99574EBA7432465FC13C1B21FE98EE8B@DC-US1MBEX4.global.avaya.com> <4C371EE5.1030200@cisco.com>
From: R.Jesske@telekom.de
To: pkyzivat@cisco.com, dworley@avaya.com
X-OriginalArrivalTime: 20 Jul 2010 08:46:02.0853 (UTC) FILETIME=[FBF92950:01CB27E7]
Cc: bliss@ietf.org
Subject: Re: [BLISS] Call-completion issue 1010: The event model
X-BeenThere: bliss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Basic Level of Interoperability for SIP Services \(BLISS\) BoF" <bliss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bliss>
List-Post: <mailto:bliss@ietf.org>
List-Help: <mailto:bliss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bliss>, <mailto:bliss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 08:45:57 -0000

>Another solution to this is:
>
>Formulate the state of the queue as a list of the entries in the queue,

>each containing identifying information and an indicator for whether it

>is "active".
>
>Then have a default filter for "normal" subscribers that only allows 
>them to see entries for themself.
>
>As a result, normal subscribers will get an initial notification with 
>their own entry, indicating "inactive". Then they will get no further 
>notification until the part of the state visible to them changes, which

>is when they become "active".
>
>More "privileged" subscribers might be able to see the complete list.
>
>	Thanks,
>	Paul


Hi all,
Perhaps there is a misunderstanding. The caller subscribes to his own CC
state which is a combination of the caller's position in the queue and
busy state of the callee. 

Therefore it is valid that several callers receive the "queued" state at
the same time, but of course only on caller is notified about the
"ready" state per time. 


Best Regards

Roland and Martin

v2.23.0 | Report a Bug | By Email