Re: [splices] SIP INVOKE method
Peter Musgrave <musgravepj@gmail.com> Wed, 18 May 2011 17:37 UTC
Return-Path: <musgravepj@gmail.com>
X-Original-To: splices@ietfa.amsl.com
Delivered-To: splices@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1E17E06C8 for <splices@ietfa.amsl.com>; Wed, 18 May 2011 10:37:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JLwqA-uduAAV for <splices@ietfa.amsl.com>; Wed, 18 May 2011 10:37:35 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1E7A9E06C3 for <splices@ietf.org>; Wed, 18 May 2011 10:37:34 -0700 (PDT)
Received: by fxm15 with SMTP id 15so1589175fxm.31 for <splices@ietf.org>; Wed, 18 May 2011 10:37:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=mnWpWrzmEDJRecpgnnG7A23wwzboqq0JlWa/+TVr/hk=; b=EJV5XhtoqiRErWKmc4fR08x5Q33aFmqwrLyDBHdaqz4/XkF3Ln55NYYfENbHutpkbe 6RDo+/2Tp/0+E0PDvqyLUy9kGStRsXRo1YZbBjCoYGYJmqRC124MJzv3qs0OETxdos1/ LT8BvjokvJ2ePQLNYgivPTYh4urPRs8V/jmsg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=d2/qsFFD6Nc+SKgXIc03UOxMAQmeOAj53AxLvyWrA2BYcp7mDst2UOyVyrVU+TUsi0 WtcypeHU2FL8XI2VUXglvxOhWj3/q3/nEmF67nqZO1dCL4CtPtumXwMgJB3bp46RwsPZ Uzu2rR81yAwXwiRMWR86xcP7PS1S41nJY+Zlo=
MIME-Version: 1.0
Received: by 10.223.113.193 with SMTP id b1mr2699456faq.47.1305740254186; Wed, 18 May 2011 10:37:34 -0700 (PDT)
Received: by 10.223.103.67 with HTTP; Wed, 18 May 2011 10:37:34 -0700 (PDT)
In-Reply-To: <4DD401F4.6050502@cisco.com>
References: <6369CB70BFD88942B9705AC1E639A33822CBDA8EBF@DC-US1MBEX4.global.avaya.com> <BANLkTinLjrS3DocT=_MbnDrHdoTLs7RuhQ@mail.gmail.com> <6369CB70BFD88942B9705AC1E639A33822CBDA9548@DC-US1MBEX4.global.avaya.com> <4DD2C7BF.1030000@cisco.com> <6369CB70BFD88942B9705AC1E639A33822CBE5C339@DC-US1MBEX4.global.avaya.com> <4DD3C26A.9050705@cisco.com> <6369CB70BFD88942B9705AC1E639A33822CBE5C465@DC-US1MBEX4.global.avaya.com> <BANLkTi=RrRrJEqrqVoWkS428y4-=TPZ16A@mail.gmail.com> <6369CB70BFD88942B9705AC1E639A33822CBE5C63F@DC-US1MBEX4.global.avaya.com> <BANLkTikSBqp3bVHvX57Ekm07s+SDvcHGeA@mail.gmail.com> <4DD401F4.6050502@cisco.com>
Date: Wed, 18 May 2011 13:37:34 -0400
Message-ID: <BANLkTinc28U1xhyvufF327O7eQ_fvm11tA@mail.gmail.com>
From: Peter Musgrave <musgravepj@gmail.com>
To: Paul Kyzivat <pkyzivat@cisco.com>
Content-Type: multipart/alternative; boundary="001636c594e3050d1704a39058db"
Cc: "splices@ietf.org" <splices@ietf.org>
Subject: Re: [splices] SIP INVOKE method
X-BeenThere: splices@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Loosely-coupled SIP Devices \(splices\) working group discussion list" <splices.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/splices>, <mailto:splices-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/splices>
List-Post: <mailto:splices@ietf.org>
List-Help: <mailto:splices-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/splices>, <mailto:splices-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2011 17:37:35 -0000
Do you think it has relevance to CLUE? [For which we *also* have you as representative ;-) ] > But not so general that it becomes a general purpose tunnel-over-sip > mechanism. There needs to be a scope of applicability. I'm thinking its > limited to controlling the behavior of a sip device with respect to the > mapping of call streams to devices, initiating, terminating and otherwise > managing calls, ... > >
- Re: [splices] SIP INVOKE method gao.yang2
- [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method - implicit regist… Christer Holmberg
- Re: [splices] SIP INVOKE method - implicit regist… Adam Roach
- Re: [splices] SIP INVOKE method Paul Kyzivat
- Re: [splices] SIP INVOKE method Peter Musgrave
- Re: [splices] SIP INVOKE method Peter Musgrave
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Parthasarathi R (partr)
- Re: [splices] SIP INVOKE method Paul Kyzivat
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Parthasarathi R (partr)
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Paul Kyzivat
- Re: [splices] SIP INVOKE method Parthasarathi R (partr)
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Peter Musgrave
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Peter Musgrave
- Re: [splices] SIP INVOKE method Salvatore Loreto
- Re: [splices] SIP INVOKE method Paul Kyzivat
- Re: [splices] SIP INVOKE method Peter Musgrave
- Re: [splices] SIP INVOKE method Christer Holmberg
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method R.Jesske
- Re: [splices] SIP INVOKE method Shekh-Yusef, Rifaat (Rifaat)
- Re: [splices] SIP INVOKE method Hutton, Andrew