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

Henry Sinnreich <Henry.Sinnreich@wcom.com> Thu, 20 February 2003 14:09 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 JAA14922 for <sipping-archive@odin.ietf.org>; Thu, 20 Feb 2003 09:09:51 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1KEGRt15498 for sipping-archive@odin.ietf.org; Thu, 20 Feb 2003 09:16:27 -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 h1KEGRp15495 for <sipping-web-archive@optimus.ietf.org>; Thu, 20 Feb 2003 09:16:27 -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 JAA14870 for <sipping-web-archive@ietf.org>; Thu, 20 Feb 2003 09:09:20 -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 h1KEFgp15463; Thu, 20 Feb 2003 09:15:42 -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 h1KEEqp15427 for <sipping@optimus.ietf.org>; Thu, 20 Feb 2003 09:14:52 -0500
Received: from pmesmtp02.wcom.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14846 for <sipping@ietf.org>; Thu, 20 Feb 2003 09:07:45 -0500 (EST)
Received: from pmismtp04.wcomnet.com ([166.38.62.39]) by firewall.wcom.com (Iplanet MTA ) with ESMTP id <0HAM0046M1W2VS@firewall.wcom.com> for sipping@ietf.org; Thu, 20 Feb 2003 14:07:14 +0000 (GMT)
Received: from pmismtp04.wcomnet.com by pmismtp04.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with SMTP id <0HAM00E011UR54@pmismtp04.wcomnet.com>; Thu, 20 Feb 2003 14:07:14 +0000 (GMT)
Received: from hsinnreich2 ([166.42.40.80]) by pmismtp04.wcomnet.com (iPlanet Messaging Server 5.1 HotFix 0.7 (built May 7 2002)) with ESMTP id <0HAM00A8C12M1Y@pmismtp04.wcomnet.com>; Thu, 20 Feb 2003 14:06:29 +0000 (GMT)
Date: Thu, 20 Feb 2003 08:06:29 -0600
From: Henry Sinnreich <Henry.Sinnreich@wcom.com>
Subject: RE: [Sipping] Re: [Sipforum-discussion] SIP Telephony Device Requirements, Configuration and Data
In-reply-to: <NFBBJHOFMDBFILNPMNGKOENADLAA.gunnar.hellstrom@omnitor.se>
To: 'Gunnar Hellström' <gunnar.hellstrom@omnitor.se>, 'Jörgen Björkner' <jorgen.bjorkner@hotsip.com>, sipforum-discussion@lists.su.se
Cc: sipping@ietf.org
Message-id: <002101c2d8e9$448b13a0$50282aa6@hsinnreich2>
Organization: WorldCom, Inc.
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mailer: Microsoft Outlook, Build 10.0.3416
Content-type: text/plain; charset="iso-8859-1"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h1KEEqp15428
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

Gunnar Hellström writes:

> 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.

This and the other below are excellent points! Thanks for the
contribution. Will add in the next version of 

http://www.ietf.org/internet-drafts/draft-sinnreich-sipdev-req-00.txt

Henry

> -----Original Message-----
> From: sipping-admin@ietf.org [mailto:sipping-admin@ietf.org] 
> On Behalf Of Gunnar Hellström
> Sent: Thursday, February 13, 2003 2:22 PM
> To: Henry Sinnreich; 'Jörgen Björkner'; 
> sipforum-discussion@lists.su.se
> Cc: sipping@ietf.org
> Subject: [Sipping] Re: [Sipforum-discussion] SIP Telephony 
> Device Requirements, Configuration and Data
> 
> 
> 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
> 

_______________________________________________
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