Re: [sipcore] Reviewers needed for new music-on-hold technique

"Elwell, John" <john.elwell@siemens-enterprise.com> Mon, 01 November 2010 10:23 UTC

Return-Path: <john.elwell@siemens-enterprise.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5F9E3A67B3 for <sipcore@core3.amsl.com>; Mon, 1 Nov 2010 03:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.024
X-Spam-Level:
X-Spam-Status: No, score=-102.024 tagged_above=-999 required=5 tests=[AWL=0.575, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qa5DnGk++0gF for <sipcore@core3.amsl.com>; Mon, 1 Nov 2010 03:23:40 -0700 (PDT)
Received: from ms01.m0019.fra.mmp.de.bt.com (m0019.fra.mmp.de.bt.com [62.180.227.30]) by core3.amsl.com (Postfix) with ESMTP id 860F93A67D4 for <sipcore@ietf.org>; Mon, 1 Nov 2010 03:23:40 -0700 (PDT)
Received: from senmx11-mx ([62.134.46.9] [62.134.46.9]) by ms01.m0020.fra.mmp.de.bt.com with ESMTP id BT-MMP-2127992; Mon, 1 Nov 2010 11:23:40 +0100
Received: from MCHP064A.global-ad.net (unknown [172.29.37.63]) by senmx11-mx (Server) with ESMTP id 97CB61EB82AB; Mon, 1 Nov 2010 11:23:40 +0100 (CET)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP064A.global-ad.net ([172.29.37.63]) with mapi; Mon, 1 Nov 2010 11:23:40 +0100
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "Worley, Dale R (Dale)" <dworley@avaya.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Date: Mon, 1 Nov 2010 11:23:38 +0100
Thread-Topic: Reviewers needed for new music-on-hold technique
Thread-Index: AQHLcVqTV/CZQEsmuUSbuxTZrQzVUpNMkT6g
Message-ID: <A444A0F8084434499206E78C106220CA023554605F@MCHP058A.global-ad.net>
References: <CD5674C3CD99574EBA7432465FC13C1B220228896D@DC-US1MBEX4.global.avaya.com>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220228896D@DC-US1MBEX4.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [sipcore] Reviewers needed for new music-on-hold technique
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Nov 2010 10:23:41 -0000

Dale,

I haven't reviewed it in detail, but I see there is no mention of RTCP. Perhaps it isn't really relevant, except that it provides another reason why the media server needs to supply an IP address and port - even though it will not receive RTP, it will receive RTCP. The RTCP port could be implicit or explicit.

John

> -----Original Message-----
> From: sipcore-bounces@ietf.org 
> [mailto:sipcore-bounces@ietf.org] On Behalf Of Worley, Dale R (Dale)
> Sent: 21 October 2010 21:00
> To: sipcore@ietf.org
> Subject: [sipcore] Reviewers needed for new music-on-hold technique
> 
> I've written draft-worley-service-example to describe a 
> music-on-hold technique which has some advantages over the 
> technique in RFC 5359.  (The two are mutually compatible, and 
> both are compatible with almost all SIP UAs.)  I am advancing 
> this as an AD-sponsored RFC.  I think I've fixed the last 
> wrinkles and would like people to review the draft.
> 
> The -05 changes describe that (as in other third-party 
> situations) it is not possible to handle codec numbers 
> exactly correctly in all situations.  But following certain 
> guidelines provides correct behavior in the vast majority of cases.
> 
>       Session Initiation Protocol Service Example -- Music on Hold
>                     draft-worley-service-example-05
> 
>    The "music on hold" feature is one of the most desired features of
>    telephone systems in the business environment.  "Music on hold" is
>    where, when one party to a call has the call "on hold", 
> that party's
>    telephone provides an audio stream (often music) to be heard by the
>    other party.  Architectural features of SIP make it difficult to
>    implement music-on-hold in a way that is fully compliant with the
>    standards.  The implementation of music-on-hold described in this
>    document is fully effective and standards-compliant, and 
> has a number
>    of advantages over the methods previously documented.  In 
> particular,
>    it is less likely to produce peculiar user interface 
> effects and more
>    likely to work in systems which perform authentication than the
>    method of RFC 5359.
> 
> Thanks,
> 
> Dale
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>