[Sipping] Re: [Sipforum-discussion] SIP Telephony Device Requirements, Configuration and Data

Gunnar Hellström <gunnar.hellstrom@omnitor.se> Thu, 20 February 2003 09:04 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 EAA04730 for <sipping-archive@odin.ietf.org>; Thu, 20 Feb 2003 04:04:55 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1K9BPo29034 for sipping-archive@odin.ietf.org; Thu, 20 Feb 2003 04:11:25 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K9BPp29031 for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Feb 2003 04:11:25 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA04718 for <sipping-web-archive@ietf.org>; Thu, 20 Feb 2003 04:04:23 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1K9App28989; Thu, 20 Feb 2003 04:10:51 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1DKLxp17105 for <sipping@optimus.ietf.org>; Thu, 13 Feb 2003 15:21:59 -0500
Received: from mailf.telia.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25611 for <sipping@ietf.org>; Thu, 13 Feb 2003 15:18:07 -0500 (EST)
Received: from d1o933.telia.com (d1o933.telia.com [213.67.164.241]) by mailf.telia.com (8.12.5/8.12.5) with ESMTP id h1DKLHjd012002; Thu, 13 Feb 2003 21:21:17 +0100 (CET)
X-Original-Recipient: sipping@ietf.org
Received: from eta (h10n2fls31o933.telia.com [212.181.137.10]) by d1o933.telia.com (8.10.2/8.10.1) with SMTP id h1DKLHq25123; Thu, 13 Feb 2003 21:21:17 +0100 (CET)
From: Gunnar Hellström <gunnar.hellstrom@omnitor.se>
To: Henry Sinnreich <Henry.Sinnreich@wcom.com>, 'Jörgen Björkner' <jorgen.bjorkner@hotsip.com>, sipforum-discussion@lists.su.se
Cc: sipping@ietf.org
Date: Thu, 13 Feb 2003 21:21:41 +0100
Message-ID: <NFBBJHOFMDBFILNPMNGKOENADLAA.gunnar.hellstrom@omnitor.se>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <000601c2d113$7d0d6990$248823a6@hsinnreich2>
Content-Transfer-Encoding: 8bit
Subject: [Sipping] Re: [Sipforum-discussion] SIP Telephony Device Requirements, Configuration and Data
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: 8bit
Content-Transfer-Encoding: 8bit

Henry,

It is mentioned in the introduction to the document that "text shall be kept
in mind".

I suggest some specific text items to be entered that are in line with
existing standardisation, and accessibility needs and useful for all:

----------------------------------------------------------------------------
-------------------
SIP-xx, analogue text support: SIP adapter devices (for analog phone lines)
  MUST support conversion between real time text transmission using RFC 2793
[y]
  and text telephones according to ITU-T V.18 [x] allowing alternating use
of
  text and voice. SIP clients MUST fallback to G.711 if RFC2793 connection
fails.


SIP-zz, digital text support: SIP telephone devices MUST support
  real time text conversation using RFC 2793 [y] for the text stream.
  It MUST be possible to use text simultaneously with voice.



---------------------------------------------
In 4.11 Ringer Behaviour  : add the section below for the purpose of deaf,
hearing impaired, deaf-blind people and people in the garden and noisy
locations:

SIP Telephony devices MUST provide an external interface to
an external alerting system.



Add to References
-----------------
[y] G. Hellstrom: "RTP Payload for Text Conversation.", RFC 2793, IETF, May
2000.
[z] ITU-T Recommendation V.18 "Operational and interworking requirements for
DCEs operating in the text telephone mode", November 2000 with amendment
November 2002.

----------------------------------------------------------------------------
-------




Thanks
-------------------------------------------
Gunnar Hellström
Omnitor AB
Renathvägen 2
SE 121 37 Johanneshov
SWEDEN
+46 8 556 002 03
Mob: +46 708 204 288
www.omnitor.se
Gunnar.Hellstrom@Omnitor.se
--------------------------------------------

> -----Ursprungligt meddelande-----
> Från: sipforum-discussion-admin@lists.su.se
> [mailto:sipforum-discussion-admin@lists.su.se]För Henry Sinnreich
> Skickat: den 10 februari 2003 15:49
> Till: 'Jörgen Björkner'; sipforum-discussion@lists.su.se
> Ämne: [Sipforum-discussion] SIP Telephony Device Requirements,
> Configuration and Data
>
>
> For everyone interested SIP phones and other SIP communication devices,
> and the 56 IETF  coming next month, please see if you like or dislike or
> don't care about the draft:
>
> http://www.ietf.org/internet-drafts/draft-sinnreich-sipdev-req-00.txt
>
> The idea is to have discussions on the lists, and if there is interest
> and rough consensus to move ahead with an informational RFC. Would
> appreciate your comments to
>
> sipping@ietf.org , and also to
>
> sipforum-discussion@lists.su.se
>
> Thanks, Henry
>
> Henry Sinnreich
> WorldCom
> 400 International Parkway
> Richardson, Texas 75081
> USA
>
>
>


_______________________________________________
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