Re: [sipcore] I-DAction:draft-mohali-sipcore-reason-extension-application-01

<marianne.mohali@orange-ftgroup.com> Thu, 17 March 2011 16:29 UTC

Return-Path: <marianne.mohali@orange-ftgroup.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 B25743A69DB for <sipcore@core3.amsl.com>; Thu, 17 Mar 2011 09:29:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.962
X-Spam-Level:
X-Spam-Status: No, score=-2.962 tagged_above=-999 required=5 tests=[AWL=0.288, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1]
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 IX3UQU5lgi9I for <sipcore@core3.amsl.com>; Thu, 17 Mar 2011 09:29:20 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by core3.amsl.com (Postfix) with ESMTP id 69AC13A6996 for <sipcore@ietf.org>; Thu, 17 Mar 2011 09:29:20 -0700 (PDT)
Received: from p-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 34AC68B8002; Thu, 17 Mar 2011 17:31:17 +0100 (CET)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by p-mail1.rd.francetelecom.com (Postfix) with ESMTP id 29D3C8B800B; Thu, 17 Mar 2011 17:31:17 +0100 (CET)
Received: from ftrdmel1.rd.francetelecom.fr ([10.192.128.40]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Thu, 17 Mar 2011 17:30:44 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Mar 2011 17:30:43 +0100
Message-ID: <B11765B89737A7498AF63EA84EC9F5776A5936@ftrdmel1>
In-Reply-To: <CD5674C3CD99574EBA7432465FC13C1B220B5C1567@DC-US1MBEX4.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [sipcore] I-DAction:draft-mohali-sipcore-reason-extension-application-01
Thread-Index: AcvZyONLW9FOvLuUTUqkYcckL0it7wDKxr0yAFSpeNAAEGYxoAGIbH+g
References: <B11765B89737A7498AF63EA84EC9F5775D36A6@ftrdmel1><4D6C2CB6.4040800@cisco.com><B11765B89737A7498AF63EA84EC9F577617DBB@ftrdmel1>, <4D6FD03A.8040507@cisco.com> <CD5674C3CD99574EBA7432465FC13C1B220B5C154B@DC-US1MBEX4.global.avaya.com>, <B11765B89737A7498AF63EA84EC9F57765B3A4@ftrdmel1> <CD5674C3CD99574EBA7432465FC13C1B220B5C1567@DC-US1MBEX4.global.avaya.com>
From: marianne.mohali@orange-ftgroup.com
To: dworley@avaya.com, pkyzivat@cisco.com
X-OriginalArrivalTime: 17 Mar 2011 16:30:44.0589 (UTC) FILETIME=[A9EC71D0:01CBE4C0]
Cc: sipcore@ietf.org, Christer.Holmberg@ericsson.com
Subject: Re: [sipcore] I-DAction:draft-mohali-sipcore-reason-extension-application-01
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: Thu, 17 Mar 2011 16:29:21 -0000

Hi Dale,

Here is a simple call flow to illustrate the example mentioned in my email (you can see 2 more examples in the I-D with Reason header inside History-Info header or NOT):

Alice calls a Toll Free Directory service to retreive a restaurant phone number in Prague. 
She is calling from a public phone using her Prepaid card.

     Alice      Prepaid service  Toll Free Directory    Restaurant
       |                |                 |                 |
       |    INVITE F1   |                 |                 |
       |--------------->|   INVITE F2     |                 |
       |                |---------------->|                 |
       |                |                 |    INVITE F3    |
       |                |                 |---------------->|  

F1: INVITE Alice -> Prepaid

INVITE sip:+18005555555@prepaid.com;user=phone SIP/2.0
From: Alice <sip:alice@example.com>; tag=1234567
To: Prepaid service <sip:info@prepaid.biloxie.com>
Supported: histinfo
...

F2: INVITE Prepaid -> Toll Free Directory

INVITE sip:+18005551212@phone2net.com SIP/2.0
From: Alice <sip:alice@example.com>; tag=1234567
To: sip:+18005551212@phone2net.com;user=phone
Supported: histinfo
History-Info: <sip:+18005555555@example.com;user=phone?Reason=application
              %3Bcause%3D9%3B text%3D "Prepaid">;index=1
              <sip:+18005551212@phone2net.com>;index=1.1;mp=1
...
 
F3: INVITE Toll Free Directory -> Restaurant

INVITE sip:+420224841111@prague.com SIP/2.0
From: Alice <sip:alice@example.com>; tag=1234567
To: sip:+420224841111@prague.com;user=phone
Supported: histinfo
History-Info: <sip:+18005555555@prepaid.com;user=phone?Reason=application
              %3Bcause%3D9%3B text%3D "Prepaid">;index=1,
              <sip:+18005551212@phone2net.com?Reason=application
              %3Bcause%3D11%3B text%3D "Toll Free">;index=1.1;mp=1,
		  <sip:+420224841111@prague.com>index=1.1.1
...


Regards,
Marianne

> -----Message d'origine-----
> De : Worley, Dale R (Dale) [mailto:dworley@avaya.com] 
> Envoyé : mercredi 9 mars 2011 19:32
> À : MOHALI Marianne RD-CORE-ISS; pkyzivat@cisco.com
> Cc : sipcore@ietf.org; Christer.Holmberg@ericsson.com
> Objet : RE: [sipcore] 
> I-DAction:draft-mohali-sipcore-reason-extension-application-01
> 
> ________________________________________
> From: marianne.mohali@orange-ftgroup.com 
> [marianne.mohali@orange-ftgroup.com]
> 
> > -----Message d'origine-----
> > De : Worley, Dale R (Dale) [mailto:dworley@avaya.com]
> >
> > Could we see an example of how this is expected to be done?
> > (Or have I overlooked the example?)  There are various 
> subtlties in a 
> > protocol feature whose *absence* in the signaling tells another 
> > application that a certain action may be taken.
> 
> [MM] In my network, I have an agreement with the Prepaid 
> application that is to identify itself in the signaling (in 
> the H-I header) when applied.
> So that, I can offer to all of my clients a customized 
> service with a connection to the reseached phone number 
> except for prepaid callers.
> Callers from other networks will not be able to enjoy the 
> customized service (with the connection) as they are 
> considered as untrusted.
> _______________________________________
> 
> I was thinking of a call flow, showing the critical header 
> fields, the various proxies involved, etc.
> 
> Dale
>