[sr-dev] Fwd: module writing & per message variable within my module

[Olle E. Johansson]

On 08 May 2014, at 08:49, jay binks <jaybinks at gmail.com> wrote:

> Sorry to repost this but, Im still looking for answers.
> is there a better place to be asking these questions ??
> 
> Jay
> 
> ---------- Forwarded message ----------
> From: jay binks <jaybinks at gmail.com>
> Date: 19 March 2014 19:18
> Subject: module writing & per message variable within my module
> To: sr-dev <sr-dev at lists.sip-router.org>
> 
> 
> So Im writing a custom module to implement some of our business logic,
> there are a few steps that im building into the module,  for example
> 
> conform_callerid
> conform_destination 
> 
> what I want to achive should be fairly simple, but let me explain and im sure someone will tell me where to look.
> 
> when I call conform_callerid, I want to store a few bits of info so Initially I store them in a global variable ( yup lazy & dangerous I guess )
> 
> then I write the pv "get" function, to return the value from the global.
> 
> this was only done as a quick proof of concept.
> but being global, im sure the variable will be overwritten by other message etc etc..
> 
> so I effectively want to store some custom fields against the message.
> I didnt see this on the msg structure, but maybe I missed something
> 
> or is there a better way to achieve this ??
> 
> basically I want to be able to call conform_callerid 
> then when I call conform_destination I want to look at some fields from the conform_callerid process  ( within the context of the message we are processing )
> 
> any pointers would be appreciated.

avps are stored in the transaction, process variablees in the process. You don't clearly say in which context you want to "save" the data and when you want to "use" it so it's hard to answer this.

Why do you need to write a module for this? What is it you can not do in the scripts?

/O



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-dev/attachments/20140508/28cbfce2/attachment.html>