IETF Logo Mail Archive

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

"WORLEY, Dale R (Dale)" <dworley@avaya.com> Fri, 09 July 2010 17:04 UTC

Return-Path: <dworley@avaya.com>
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 0DCA93A6A5D for <bliss@core3.amsl.com>; Fri, 9 Jul 2010 10:04:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[AWL=0.590, BAYES_00=-2.599]
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 RvpTChIrlEhC for <bliss@core3.amsl.com>; Fri, 9 Jul 2010 10:04:11 -0700 (PDT)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 061793A6A3A for <bliss@ietf.org>; Fri, 9 Jul 2010 10:04:10 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,564,1272859200"; d="scan'208";a="197316035"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by de307622-de-outbound.net.avaya.com with ESMTP; 09 Jul 2010 13:04:15 -0400
X-IronPort-AV: E=Sophos;i="4.53,564,1272859200"; d="scan'208";a="480490516"
Received: from dc-us1hcex1.us1.avaya.com (HELO DC-US1HCEX1.global.avaya.com) ([135.11.52.20]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 09 Jul 2010 13:04:13 -0400
Received: from DC-US1MBEX4.global.avaya.com ([169.254.1.161]) by DC-US1HCEX1.global.avaya.com ([2002:870b:3414::870b:3414]) with mapi; Fri, 9 Jul 2010 13:04:13 -0400
From: "WORLEY, Dale R (Dale)" <dworley@avaya.com>
To: Scott Lawrence <xmlscott@gmail.com>, "bliss@ietf.org" <bliss@ietf.org>
Date: Fri, 09 Jul 2010 13:02:52 -0400
Thread-Topic: [BLISS] Call-completion issue 1010: The event model
Thread-Index: AcsfaEgpvVGaMuSmS/eBeTqp2JFIYQAIEkTf
Message-ID: <CD5674C3CD99574EBA7432465FC13C1B21FE98EE90@DC-US1MBEX4.global.avaya.com>
References: <CD5674C3CD99574EBA7432465FC13C1B21FE98EE8B@DC-US1MBEX4.global.avaya.com>, <4C371FE2.3070506@gmail.com>
In-Reply-To: <4C371FE2.3070506@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Fri, 09 Jul 2010 17:04:12 -0000

________________________________________
From: bliss-bounces@ietf.org [bliss-bounces@ietf.org] On Behalf Of Scott Lawrence [xmlscott@gmail.com]

Why not send the notification to all subscribers, but include in the
notice an explicit indication of which is active?  Rather than send
'active', send 'active sip:subscriber@domain' where
'sip:subscriber@domain' is the contact URI from the head of the queue?
_______________________________________________

It certainly simplifies the situation.  In principle there might be privacy problems.  In practice, SBCs modify the Contact URI, so the agent doesn't know what Contact URI the monitor sees.

Dale

v2.23.0 | Report a Bug | By Email