Re: [Notifications] Enterprise MWI Use Case

Eric Burger <eburger@bea.com> Tue, 31 July 2007 11:12 UTC

Return-path: <notifications-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFpdw-0000pi-LM; Tue, 31 Jul 2007 07:12:00 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IFpdv-0000pa-5T for notifications-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 07:11:59 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFpdu-0000pQ-R7 for notifications@ietf.org; Tue, 31 Jul 2007 07:11:58 -0400
Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFpdu-0004Bn-An for notifications@ietf.org; Tue, 31 Jul 2007 07:11:58 -0400
Received: from repmmr02.bea.com (repmmr02.bea.com [10.160.30.72]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l6VBBuPN025455; Tue, 31 Jul 2007 04:11:56 -0700
Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l6VBBIcJ021836; Tue, 31 Jul 2007 04:11:19 -0700
Received: from 172.24.28.86 ([172.24.28.86]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Tue, 31 Jul 2007 11:11:54 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Mon, 30 Jul 2007 07:44:46 -0500
Subject: Re: [Notifications] Enterprise MWI Use Case
From: Eric Burger <eburger@bea.com>
To: Cullen Jennings <fluffy@cisco.com>, notifications@ietf.org
Message-ID: <C2D3476E.862C%eburger@bea.com>
Thread-Topic: [Notifications] Enterprise MWI Use Case
Thread-Index: AcfQm/hBZdoTqVmnRGWHBf7SuUpgqQCC3BdY
In-Reply-To: <0F4D841F-40E2-464E-AF1A-986012C41FCE@cisco.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
x-BEA-PMX-Instructions: AV
x-BEA-MM: Internal-To-External
X-Spam-Score: 1.8 (+)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc:
X-BeenThere: notifications@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Message Notifications interest group discussion list <notifications.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/notifications>
List-Post: <mailto:notifications@ietf.org>
List-Help: <mailto:notifications-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=subscribe>
Errors-To: notifications-bounces@ietf.org

I can help on the what is "voicemail": see RFC 3458.


On 7/27/07 5:17 PM, "Cullen Jennings" <fluffy@cisco.com> wrote:

> 
> 
> Phase 1:
> 
> Enterprise phones have a little red light on them. This light should
> be on if, and only if, the the email store as any unseen message that
> contain voicemails. I don't really know the precise term for "unseen"
> or "voicemail" mean in this context so hopefully someone can provide
> the right term. On average, this light changes state less than a 6
> times per day. A large system would have less than 100,000 phones
> receiving notifications. The network environment is typically 100Mbps
> although sometimes remote offices with a less than 500 phones will be
> on a slower WAN link. When the state on the email store changes, the
> red light needs to change in less than 10 seconds and changing in
> under 2 seconds is desirable. If a phone is power cycled, the state
> of the red light after the power cycle needs to be correct and can
> not wait for the next time the state changes.
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Notifications mailing list
> Notifications@ietf.org
> https://www1.ietf.org/mailman/listinfo/notifications
> 



Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.


_______________________________________________
Notifications mailing list
Notifications@ietf.org
https://www1.ietf.org/mailman/listinfo/notifications