RE: [Sipping] Sipdev, incoming call alert (ring signal equivalents)
Henry Sinnreich <Henry.Sinnreich@mci.com> Sat, 28 June 2003 07:47 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA18103 for <sipping-archive@odin.ietf.org>; Sat, 28 Jun 2003 03:47:41 -0400 (EDT)
Received: (from exim@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5S7lCh24329 for sipping-archive@odin.ietf.org; Sat, 28 Jun 2003 03:47:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WAQS-0006KK-JP for sipping-web-archive@optimus.ietf.org; Sat, 28 Jun 2003 03:47:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA17925 for <sipping-web-archive@ietf.org>; Sat, 28 Jun 2003 03:43:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19WAMh-00021g-00 for sipping-web-archive@ietf.org; Sat, 28 Jun 2003 03:43:19 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19WAMa-00021N-00 for sipping-web-archive@ietf.org; Sat, 28 Jun 2003 03:43:12 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19WAMQ-0005Sh-UI; Sat, 28 Jun 2003 03:43:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19UX2X-0000wY-VB for sipping@optimus.ietf.org; Mon, 23 Jun 2003 15:32:31 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07032 for <sipping@ietf.org>; Mon, 23 Jun 2003 15:31:28 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19UX2H-00058k-00 for sipping@ietf.org; Mon, 23 Jun 2003 15:31:29 -0400
Received: from dgesmtp02.wcom.com ([199.249.16.17]) by ietf-mx with esmtp (Exim 4.12) id 19UX26-00057d-00 for sipping@ietf.org; Mon, 23 Jun 2003 15:31:18 -0400
Received: from dgismtp06.wcomnet.com ([166.38.58.89]) by firewall.wcom.com (Iplanet MTA 5.2) with ESMTP id <0HGY006E48R7LS@firewall.wcom.com> for sipping@ietf.org; Mon, 23 Jun 2003 19:28:19 +0000 (GMT)
Received: from dgismtp06.wcomnet.com by dgismtp06.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with SMTP id <0HGY002018R5FK@dgismtp06.wcomnet.com>; Mon, 23 Jun 2003 19:28:18 +0000 (GMT)
Received: from hsinnreich2 ([166.50.145.238]) by dgismtp06.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with ESMTP id <0HGY001CY8R31Q@dgismtp06.wcomnet.com>; Mon, 23 Jun 2003 19:28:18 +0000 (GMT)
Date: Mon, 23 Jun 2003 14:28:16 -0500
From: Henry Sinnreich <Henry.Sinnreich@mci.com>
Subject: RE: [Sipping] Sipdev, incoming call alert (ring signal equivalents)
In-reply-to: <NFBBJHOFMDBFILNPMNGKCEIIEBAA.gunnar.hellstrom@omnitor.se>
To: 'Gunnar Hellstrom' <gunnar.hellstrom@omnitor.se>, "'Sipping@Ietf. Org'" <sipping@ietf.org>, A.vWijk@viataal.nl, 'Mike Spanner' <mike.spanner@rnid.org.uk>, 'James Hamlin' <james.hamlin@rnid.org.uk>, paulej@packetizer.com, Erik.Zetterstrom@omnitor.se, andreas.piirimets@omnitor.se, barry.dingle@bigfoot.com.au, 'Guido Gybels' <Guido.Gybels@rnid.org.uk>, gv@trace.wisc.edu, 'Judy Harkins' <judy.harkins@tap.gallaudet.edu>, 'Trefor Davies' <tref@purplepacket.com>, 'Henry Sinnreich' <Henry.Sinnreich@mci.com>
Cc: trefor@trefor.plus.com, jorgen.bjorkner@hotsip.com, marcelo@envilogg.se, rkumar@cisco.com
Message-id: <000901c339bd$997ca1f0$ee9132a6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7bit
Sender: sipping-admin@ietf.org
Errors-To: sipping-admin@ietf.org
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Id: SIPPING Working Group (applications of SIP) <sipping.ietf.org>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
> In 4.9 Ringer Behaviour : add the section below for the > purpose of people in the garden, in noisy locations, and for > the use by deaf, hearing impaired, deaf-blind people. I believe this is a good suggestion. With MAY in the general section or MUST for haering disabled. Henry > -----Original Message----- > From: Gunnar Hellstrom [mailto:gunnar.hellstrom@omnitor.se] > Sent: Monday, June 23, 2003 11:56 AM > To: 'Sipping@Ietf. Org'; A.vWijk@viataal.nl; 'Mike Spanner'; > 'James Hamlin'; paulej@packetizer.com; > Erik.Zetterstrom@omnitor.se; andreas.piirimets@omnitor.se; > barry.dingle@bigfoot.com.au; 'Guido Gybels'; > gv@trace.wisc.edu; 'Judy Harkins'; 'Trefor Davies'; Henry Sinnreich > Cc: trefor@trefor.plus.com; jorgen.bjorkner@hotsip.com; > marcelo@envilogg.se; rkumar@cisco.com > Subject: [Sipping] Sipdev, incoming call alert (ring signal > equivalents) > > > In the discussion about the sipdev spec, > > http://www.ietf.org/internet-drafts/draft-sinnreich-sipdev-req > -01.txt , I had earlier got positive reactions on a proposal: > > In 4.9 Ringer Behaviour : add the section below for the > purpose of people in the garden, in noisy locations, and for > the use by deaf, hearing impaired, deaf-blind people. > > "SIP Telephony devices MUST provide an external interface to > an external alerting system." > > I cannot find much from that proposal in the new wording, so > I repeat the proposal a bit more elaborated: > > Such external interfaces were normal in the PSTN era. It was > easy to buy an extra ringer to place in the garden or in the > garage. It was easy to find strong flashing light alerters to > place in the factory. > > Such features must be remembered and available also in the > SIP era. In PSTN, the alerters were connected directly to the > phone network. Now, it is instead the SIP phone itself that > knows if it is called. Therefore it must be specified in the > SIP device spec. > > Currently there are two kinds of electrical interfaces to > alerting systems. > > Both are simple two wire interfaces. > > One is resistance oriented. It has a high resistance ( 1 > Mohm) until the alert is wanted. Then the resistance is low ( > below 50 ohm ). It can sustain a voltage of at least 50 V in > the inactivated state, and a current of 200 mA in the activated state. > > The other is voltage oriented. A voltage over the interface > triggers the alerting. 12 V direct or alternating is common. > > Since both usually are available on alerting systems, I > suggest that it can be sufficient to provide the resistance > oriented one on SIP phones. > > I would also suggest an extension with a Bluetooth interface. > Using the serial port profile, and giving an AT command > response "RING" as the basic standard. It might be suitable > to have extensions from this basic version into variants > where you can specify some characteristics of the alert. > > So, my proposal is to change from: > .....................................Current > writing.......................................... > 4.9 Ringer Behavior > > The manner in which a user is alerted to an incoming call > (visually, > audibly or possibly both) MAY be used by the device. This includes > the different volumes and MAY point to a file that contains the > melody for the ringer alert. > > Ringer sound files MAY be specified for the following types of > incoming calls normal, high priority, internal and external. > > Different ringer sound files MAY also be associated with different > lines. > > The location of a call MAY also be indicated. This allows using the > phone by hearing-impaired or in noisy environments where external > speakers are used to render the sound. The location of the call is > also useful for paging by speakerphones. > :::::::::::::::::::End of current > writing::::::::::::::::::::::::::::::::::::::::::::::::::::::: > > To: > ::::::::::::::::::New > proposal::::::::::::::::::::::::::::::::::::::::::::::: > 4.9 Ringer Behavior > > The manner in which a user is alerted to an incoming call > (visually, > audibly or possibly both) MAY be configured in the device. > This includes > different volumes and the configuration MAY point to a > file that contains a > melody for the ringer alert. > > Ringer sound files MAY be specified for the following types of > incoming calls: normal, high priority, internal and external. > > Different ringer sound files MAY also be associated with different > lines. > > The location of a call MAY also be indicated. This allows using the > phone by hearing-impaired or in noisy environments where external > speakers are used to render the sound. The location of the call is > also useful for paging by speakerphones. > > SIP Telephony devices MUST provide an external interface to > an external alerting system. This allows free positioning > and selection of an alerting > system that may be visual, audible or tactile or any > combination of these modes. > An external interface MAY be a two-pole electrical > interface offering > low resistance (<50 ohm) during ring signals, and high > resistance ( > 1 Mohm ) between > ring indications. > It MAY also be a Bluetooth inteface with the serial > profile sending the "RING" > message at each ring signal. > -------------------------------------End of modified > proposal------------------------------ > > > Agree? > > > Gunnar Hellstrom > ------------------------------------------- > Gunnar Hellstrom, Omnitor, Renathvagen 2 > SE 121 37 Johanneshov, SWEDEN > Tel: +46 8 556 002 03 Mob: +46 708204288 > e-mail: gunnar.hellstrom@omnitor.se > web: www.omnitor.se > > > _______________________________________________ Sipping mailing list https://www1.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@cs.columbia.edu for questions on current sip Use sip@ietf.org for new developments of core SIP
- [Sipping] Sipdev, incoming call alert (ring signa… Gunnar Hellstrom
- RE: [Sipping] Sipdev, incoming call alert (ring s… Henry Sinnreich
- Re: [Sipping] Sipdev, incoming call alert (ring s… Michael Hammer
- SV: [Sipping] Sipdev, incoming call alert (ring s… Gunnar Hellstrom
- RE: [Sipping] Sipdev, incoming call alert (ring s… Henry Sinnreich
- Re: SV: [Sipping] Sipdev, incoming call alert (ri… Henning Schulzrinne