Re: [Iptel] CPL as a standard for distinctive ringing

ssa@hss.hns.com Thu, 05 February 2004 06:36 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20957 for <iptel-archive@odin.ietf.org>; Thu, 5 Feb 2004 01:36:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aod72-0003KP-DN for iptel-archive@odin.ietf.org; Thu, 05 Feb 2004 01:35:44 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i156Zih9012787 for iptel-archive@odin.ietf.org; Thu, 5 Feb 2004 01:35:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aod72-0003KA-9W for iptel-web-archive@optimus.ietf.org; Thu, 05 Feb 2004 01:35:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20935 for <iptel-web-archive@ietf.org>; Thu, 5 Feb 2004 01:35:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aod6z-00007h-00 for iptel-web-archive@ietf.org; Thu, 05 Feb 2004 01:35:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aod64-000027-00 for iptel-web-archive@ietf.org; Thu, 05 Feb 2004 01:34:45 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1Aod5L-0007kw-00 for iptel-web-archive@ietf.org; Thu, 05 Feb 2004 01:33:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aod5N-00039m-Rr; Thu, 05 Feb 2004 01:34:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Aobjr-0006mX-LX for iptel@optimus.ietf.org; Thu, 05 Feb 2004 00:07:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA18649 for <iptel@ietf.org>; Thu, 5 Feb 2004 00:07:40 -0500 (EST)
From: ssa@hss.hns.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Aobjp-0000OJ-00 for iptel@ietf.org; Thu, 05 Feb 2004 00:07:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Aobiv-0000Jh-00 for iptel@ietf.org; Thu, 05 Feb 2004 00:06:46 -0500
Received: from [61.16.168.131] (helo=hss.hns.com) by ietf-mx with esmtp (Exim 4.12) id 1Aobig-0000EG-00 for iptel@ietf.org; Thu, 05 Feb 2004 00:06:30 -0500
Received: from pragati.hss.hns.com (pragati.hss.hns.com [139.85.249.33]) by hss.hns.com (8.11.6/8.11.2) with ESMTP id i15545D30693; Thu, 5 Feb 2004 10:34:16 +0530
In-Reply-To: <16417.19413.514429.166633@cnr.cs.columbia.edu>
Subject: Re: [Iptel] CPL as a standard for distinctive ringing
To: Jonathan Lennox <lennox@cs.columbia.edu>
Cc: iptel@ietf.org, ssa@hss.hns.com, xiaotaow@cs.columbia.edu
X-Mailer: Lotus Notes Release 6.0.1 February 07, 2003
Message-ID: <OF0F8F0EA4.10F69FAB-ON65256E31.00191C92-65256E31.001BE387@hss.hns.com>
X-MIMETrack: Serialize by Router on Pragati/BLR/HSS(Release 6.5|September 18, 2003) at 02/05/2004 10:35:01 AM
MIME-Version: 1.0
Content-type: text/plain; charset="US-ASCII"
Sender: iptel-admin@ietf.org
Errors-To: iptel-admin@ietf.org
X-BeenThere: iptel@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=unsubscribe>
List-Id: IP Telephony <iptel.ietf.org>
List-Post: <mailto:iptel@ietf.org>
List-Help: <mailto:iptel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iptel>, <mailto:iptel-request@ietf.org?subject=subscribe>
List-Archive: <https://www.ietf.org/mail-archive/working-groups/iptel/>
Date: Thu, 05 Feb 2004 10:34:42 +0530
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60




Probably subject of my mail was misleading. My intension was to mean CPL as
a standard way of scripting distinct ring plan at proxy server.

Its very much true that distinctive ringing has to be implemented at
end-points - which precisely means playing the ring tone specified in the
alert-info header in INVITE.

The hypothetical extension (draft-ietf-iptel-cpl-08: chapter 12.10) can be
used by proxy administrators to script a distinct ring plan for a
subscriber/ end-point. I was wondering how long this will be kept as a
"hypothetical" extension in the draft? The suggested "ring" node can be
included in the standard CPL schema just like other nodes e.g. "mail"
non-signalling node. In that case, proxy server developers will provide CPL
as a standard way of scripting distinct ring plan for a subscriber.



                                                                           
             Jonathan Lennox                                               
             <lennox@cs.columb                                             
             ia.edu>                                                    To 
                                       ssa@hss.hns.com                     
             02/05/04 01:15 AM                                          cc 
                                       iptel@ietf.org,                     
                                       xiaotaow@cs.columbia.edu            
                                                                   Subject 
                                       Re: [Iptel] CPL as a standard for   
                                       distinctive ringing                 
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




On Wednesday, February 4 2004, "ssa@hss.hns.com" wrote to "iptel@ietf.org,
ssa@hss.hns.com" saying:

> This is regarding the suggested hypothetical extension to CPL
> (draft-ietf-iptel-cpl-08: chapter 12.10) for distinctive ringing.
>
> This extension was originally proposed in the 03 version of the draft.
> Since then it has been kept as a "hypothetical" extension and _not_ as a
> "standard" action node in 5 more later versions including the latest 08
> version.
>
> I would like to know the possibility/ acceptance of "ring"
> (draft-ietf-iptel-cpl-08: chapter 12.10) node coming in the standard CPL
> schema in future versions of the draft.
>
> Also response from SIP proxy developers, who are following the suggested
> extension for their distinctive ringing implementation, will be
> appreciated.

CPL is intended as a language for controlling SIP proxy servers.  There's
no
(standardized) way to implement distinctive ring in a proxy server; it
needs
to be done by user agents.

You might want to take a look at Xiaotao Wu's LESS, the Language for End
System Services.  It's an extension of CPL designed for end-system control
of this sort.

--
Jonathan Lennox
lennox@cs.columbia.edu



_______________________________________________
Iptel mailing list
Iptel@ietf.org
https://www.ietf.org/mailman/listinfo/iptel