Re: SV: [Sipping] Sipdev, incoming call alert (ring signal equivalents)

Henning Schulzrinne <hgs@cs.columbia.edu> Fri, 04 July 2003 12:41 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA24896 for <sipping-archive@odin.ietf.org>; Fri, 4 Jul 2003 08:41:47 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YPsJ-0008FN-Ib for sipping-archive@odin.ietf.org; Fri, 04 Jul 2003 08:41:19 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h64CfFhE031682 for sipping-archive@odin.ietf.org; Fri, 4 Jul 2003 08:41:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YPsJ-0008Eo-Cp for sipping-web-archive@optimus.ietf.org; Fri, 04 Jul 2003 08:41:15 -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 IAA24842 for <sipping-web-archive@ietf.org>; Fri, 4 Jul 2003 08:41:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19YPsC-0004rI-00 for sipping-web-archive@ietf.org; Fri, 04 Jul 2003 08:41:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19YPsA-0004rE-00 for sipping-web-archive@ietf.org; Fri, 04 Jul 2003 08:41:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19YPs5-000891-6o; Fri, 04 Jul 2003 08:41:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19XM7K-0007VX-LX for sipping@optimus.ietf.org; Tue, 01 Jul 2003 10:28:22 -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 KAA02519 for <sipping@ietf.org>; Tue, 1 Jul 2003 10:28:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19XM7I-00052b-00 for sipping@ietf.org; Tue, 01 Jul 2003 10:28:20 -0400
Received: from marionberry.cc.columbia.edu ([128.59.59.100] ident=cu41754) by ietf-mx with esmtp (Exim 4.12) id 19XM72-00052H-00 for sipping@ietf.org; Tue, 01 Jul 2003 10:28:04 -0400
Received: from cs.columbia.edu (dyn-wireless-246-119.dyn.columbia.edu [160.39.246.119]) (user=hgs10 mech=PLAIN bits=0) by marionberry.cc.columbia.edu (8.12.8p1/8.12.8) with ESMTP id h61EQof9027720 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 1 Jul 2003 10:26:51 -0400 (EDT)
Message-ID: <3F019A1F.1000400@cs.columbia.edu>
Date: Tue, 01 Jul 2003 10:26:39 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gunnar Hellstrom <gunnar.hellstrom@omnitor.se>
CC: Henry Sinnreich <Henry.Sinnreich@mci.com>, "'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>, trefor@trefor.plus.com, jorgen.bjorkner@hotsip.com, marcelo@envilogg.se, rkumar@cisco.com
Subject: Re: SV: [Sipping] Sipdev, incoming call alert (ring signal equivalents)
References: <NFBBJHOFMDBFILNPMNGKIENKEBAA.gunnar.hellstrom@omnitor.se>
In-Reply-To: <NFBBJHOFMDBFILNPMNGKIENKEBAA.gunnar.hellstrom@omnitor.se>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.32 (www . roaringpenguin . com / mimedefang)
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

There are pure SIP approaches for external ringing. For example, we have 
built an X-10-to/from-SIP gateway that is event-triggered. Thus, you can 
have the ringer device subscribe to call state and ring, flash, or, if 
you like, start the sprinkler if the phone rings. (The latter mechanism 
is particularly appropriate when the callee is lounging on their deck.) 
This requires no additional end device capability, but is clearly a bit 
more complicated than a wire, but also a lot more flexible, since you 
are not constrained by distance. (I'm not affiliated with X10.com; there 
are multiple vendors building equipment to that 'standard.')

Gunnar Hellstrom wrote:

> Henry,
> It is not the external alerting devices themselves that are part of the
> spec, it is just the signal to them from the sip device.
> 
> The need is valid in business as well as other environments.
> 
> A question:
> There is a sentence in the original sipdev-01 spec about the location of the
> call that I do not understand, please explain.
> ">    The location of a call MAY also be indicated."
> 

>>-Do you really want to propagate the those from the PSTN era?
> 
> Yes, the human need to be alerted on calls persists.
> 
>>-Should this really be specified for all SIP phones?
> 
> Yes, you never know what installation environment they end up in.
> 
>>-What about the SIP business phones? (Related I-D)
> 
> Same need.
> 
>>Henry
>>
> 
> 
>>>-----Original Message-----
>>>From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org]
>>>On Behalf Of Gunnar Hellstrom
>>>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 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 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