SIP/PSTN interworking draft
"Adam B. Roach" <Adam.Roach@Ericsson.com> Wed, 21 July 1999 15:39 UTC
Return-Path: <owner-confctrl>
Received: (from majordom@localhost) by zephyr.isi.edu (8.8.7/8.8.6) id IAA17734 for confctrl-outgoing; Wed, 21 Jul 1999 08:39:04 -0700 (PDT)
Received: from tnt.isi.edu (tnt.isi.edu [128.9.128.128]) by zephyr.isi.edu (8.8.7/8.8.6) with ESMTP id IAA17729 for <confctrl@zephyr.isi.edu>; Wed, 21 Jul 1999 08:39:03 -0700 (PDT)
Received: from gwa.ericsson.com (gwa.ericsson.com [198.215.127.2]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id IAA26682 for <confctrl@isi.edu>; Wed, 21 Jul 1999 08:39:01 -0700 (PDT)
Received: from mr4.exu.ericsson.se (mr4a.ericsson.com [198.215.127.160]) by gwa.ericsson.com (8.9.3/8.9.3) with ESMTP id KAA19406 for <confctrl@isi.edu>; Wed, 21 Jul 1999 10:38:30 -0500 (CDT)
Received: from newman.exu.ericsson.se (newman.exu.ericsson.se [138.85.10.50]) by mr4.exu.ericsson.se (8.9.3/8.9.3) with ESMTP id KAA19458 for <confctrl@isi.edu>; Wed, 21 Jul 1999 10:38:10 -0500 (CDT)
Received: from b04a24.exu.ericsson.se (b04a24.exu.ericsson.se [138.85.60.124]) by newman.exu.ericsson.se (8.7.5/8.7.3) with ESMTP id KAA05719 for <confctrl@isi.edu>; Wed, 21 Jul 1999 10:38:30 -0500 (CDT)
Received: (from exuadam@localhost) by b04a24.exu.ericsson.se (8.9.1/8.9.1) id KAA10841 for confctrl@isi.edu; Wed, 21 Jul 1999 10:39:11 -0500 (CDT)
Message-Id: <199907211539.KAA10841@b04a24.exu.ericsson.se>
Subject: SIP/PSTN interworking draft
To: confctrl@ISI.EDU
Date: Wed, 21 Jul 1999 10:39:10 -0500
From: "Adam B. Roach" <Adam.Roach@Ericsson.com>
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-confctrl@zephyr.isi.edu
Precedence: bulk
My interpretation of the feedback I had at last week's MMUSIC meeting on draft-roach-mmusic-sip-pstn-require-header-00.txt is as follows: 1. In-band DTMF transmission should be removed from the draft. 2. Call-control services should be removed from the draft. 3. Out-of-band DTMF transit is controversial. My purpose in this message is to check if there are any counter-arguments to the first two points which anyone would like to present, and to begin a dialogue on the third point. To summarize what I beleive the main arguements for and against inclusion of OOB DTMF: - Christian Huitema made the point that an interworking draft should limit itself to those features absolutely necessary for signalling interworking. Since DTMF isn't a necessary part of call setup and teardown, it doesn't belong in this draft. - Steve Donovan contends that, without having a requirement to send DTMF information in a format understood by SIP nodes, the most basic services (such as calling card services) will be impossible to implement. PSTN interworking is of limited value if you can't authenticate users. I'm on the fence, myself. Both seem like valid arguments. I'd appreciate it if anyone who has a stake in this arena would weigh in on one side or the other. Thanks. -- Adam Roach, Ericsson Inc. | Ph: +1 972 583 7594 | 1010 E. Arapaho, MS L-04 adam.roach@ericsson.com | Fax: +1 972 669 0154 | Richardson, TX 75081 USA
- SIP/PSTN interworking draft Adam B. Roach
- Re: SIP/PSTN interworking draft Scott Petrack
- Re: SIP/PSTN interworking draft Sean Olson
- Re: SIP/PSTN interworking draft Lawrence Conroy
- Re: SIP/PSTN interworking draft Sean Olson
- RE: SIP/PSTN interworking draft Dean Willis
- RE: SIP/PSTN interworking draft Sean Olson