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

[<[e-mail]>]

Hi Dale,

My answer below [MM]

Marianne 

> -----Message d'origine-----
> De : Worley, Dale R (Dale) [mailto:[e-mail]] 
> Envoyé : lundi 7 mars 2011 19:18
> À : Paul Kyzivat; MOHALI Marianne RD-CORE-ISS
> Cc : [e-mail]; [e-mail]
> Objet : RE: [sipcore] 
> I-DAction:draft-mohali-sipcore-reason-extension-application-01
> 
> On 3/3/2011 11:51 AM, [e-mail] wrote:
> > The purpose is to allow applications/services to be explicitely 
> > identified in the signaling path, so that others 
> > services/applications/telephony-AS can act accordingly. Either to 
> > apply a process taking into account the service interaction 
> or on the 
> > contrary, do not execute a feature already covered by the 
> application.
> > 
> > For instance, a caller with a prepaid service calls a directory 
> > enquiries Server to ask for a restaurant phone number. The operator 
> > would suggest to connect the caller to the researched phone number 
> > EXCEPT if the caller has a prepaid service because it is 
> not sure he 
> > has enough credit to pay for the communication. To allow this 
> > customized feature, the directory enquiries Application 
> needs to know 
> > that the prepaid Application has been invocated.
> 
> 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. 
> 
> Dale
>