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

[<[e-mail]>]

Oups, to following my example, 
F3 flow should be a 200 OK (to Alice)
And F4 would be a BYE from the Toll Free Directory to Alice (Alice is a prepaid card caller so it would not be proposed a connection to the Restaurant).  

Sorry

> -----Message d'origine-----
> De : [e-mail] 
> [mailto:[e-mail]] De la part de 
> [e-mail]
> Envoyé : jeudi 17 mars 2011 17:31
> À : [e-mail]; [e-mail]
> Cc : [e-mail]; [e-mail]
> Objet : Re: 
> [sipcore]I-DAction:draft-mohali-sipcore-reason-extension-appli
> cation-01
> 
> 
> 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:[e-mail];user=phone SIP/2.0
> From: Alice <sip:[e-mail]>; tag=1234567
> To: Prepaid service <sip:[e-mail]>
> Supported: histinfo
> ...
> 
> F2: INVITE Prepaid -> Toll Free Directory
> 
> INVITE sip:[e-mail] SIP/2.0
> From: Alice <sip:[e-mail]>; tag=1234567
> To: sip:[e-mail];user=phone
> Supported: histinfo
> History-Info: 
> <sip:[e-mail];user=phone?Reason=application
>               %3Bcause%3D9%3B text%3D "Prepaid">;index=1
>               <sip:[e-mail]>;index=1.1;mp=1
> ...
>  
> F3: INVITE Toll Free Directory -> Restaurant
> 
> INVITE sip:[e-mail] SIP/2.0
> From: Alice <sip:[e-mail]>; tag=1234567
> To: sip:[e-mail];user=phone
> Supported: histinfo
> History-Info: 
> <sip:[e-mail];user=phone?Reason=application
>               %3Bcause%3D9%3B text%3D "Prepaid">;index=1,
>               <sip:[e-mail]?Reason=application
>               %3Bcause%3D11%3B text%3D "Toll Free">;index=1.1;mp=1,
> 		  <sip:[e-mail]>index=1.1.1
> ...
> 
> 
> Regards,
> Marianne
> 
> > -----Message d'origine-----
> > De : Worley, Dale R (Dale) [mailto:[e-mail]] Envoyé : 
> > mercredi 9 mars 2011 19:32 À : MOHALI Marianne RD-CORE-ISS; 
> > [e-mail] Cc : [e-mail]; 
> > [e-mail] Objet : RE: [sipcore]
> > I-DAction:draft-mohali-sipcore-reason-extension-application-01
> > 
> > ________________________________________
> > From: [e-mail]
> > [[e-mail]]
> > 
> > > -----Message d'origine-----
> > > De : Worley, Dale R (Dale) [mailto:[e-mail]]
> > >
> > > 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
> > 
> _______________________________________________
> sipcore mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sipcore
>