Re: SIP/PSTN interworking draft
Scott Petrack <scott.petrack@metatel.com> Thu, 22 July 1999 14:08 UTC
Return-Path: <owner-confctrl>
Received: (from majordom@localhost) by zephyr.isi.edu (8.8.7/8.8.6) id HAA13986 for confctrl-outgoing; Thu, 22 Jul 1999 07:08:39 -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 HAA13981 for <confctrl@zephyr.isi.edu>; Thu, 22 Jul 1999 07:08:37 -0700 (PDT)
Received: from sheffield.cnchost.com (sheffield.concentric.net [207.155.252.12]) by tnt.isi.edu (8.8.7/8.8.6) with ESMTP id HAA28789 for <confctrl@ISI.EDU>; Thu, 22 Jul 1999 07:08:37 -0700 (PDT)
Received: from [192.168.10.5] (ts002d43.cht-ma.concentric.net [206.173.19.103]) by sheffield.cnchost.com id KAA21501; Thu, 22 Jul 1999 10:08:28 -0400 (EDT) [ConcentricHost SMTP Relay 1.7]
Date: Thu, 22 Jul 1999 10:10:36 -0400
From: Scott Petrack <scott.petrack@metatel.com>
To: "Adam B. Roach" <Adam.Roach@Ericsson.com>
cc: confctrl@ISI.EDU
Subject: Re: SIP/PSTN interworking draft
In-Reply-To: <199907211539.KAA10841@b04a24.exu.ericsson.se>
Message-ID: <Pine.LNX.4.10.9907220958200.3210-100000@petrack.metatel.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: owner-confctrl@zephyr.isi.edu
Precedence: bulk
It would be a very interesting thing to have a standard format for Calling Card Information, so that it could be included within, among other things a SIP payload. This would include the information on a "usual" calling card, such as the carriers name, the owner's name, the calling card number, perhaps a few bytes of special restrictions. The whole thing would be protected via either a password (analogous to the PIN) or via public-key. The point of all that is -- surely the correct format has nothing to do with OOB dtmf. In fact, dtmf could not be used, since the only way to tell in a stream of random dtmf digits which is the calling card number, which is the pin, etc., is to correlate the digits with other real-time prompts. ("please enter your pin", "please enter your calling card number"). Therefore, such dtmf information would need to be in band. Bottom line -- calling card info, yes. DTMF strings within SIP, no. Final suggestion -- if there really is some need to send DTMF within SIP, I humbly suggest that the dtmf be put into a MIME payload of type: audio/telephone-events which is being defined right now in AVT. The encoding of this MIME type should be exactly -- the RTP dtmf payload type. Why invent a new encoding? Scott On Wed, 21 Jul 1999, Adam B. Roach wrote: > > 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