This is exactly why we're doing it :D<br><br>another thing we're looking at is centralising some of the state - like the tm module and dialog modules could store data centrally so calls (transactions) can be served by any instance of an 'OpenSER cloud'. Havent got there yet, but been thinking about it- possibly using something like memcached. Would love to work with the list if anyone else has interest.<br>
<br>Cheers<br>Jason<br><br><div class="gmail_quote">On Thu, Mar 19, 2009 at 5:16 PM, Klaus Darilion <span dir="ltr"><<a href="mailto:klaus.mailinglists@pernau.at">klaus.mailinglists@pernau.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Henning Westerholt schrieb:<div><div></div><div class="h5"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thursday 19 March 2009, Jason Penton wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I am getting all of OpenSER modparam information from a web service<br>
(SOAP/HTTP) as opposed to configuring openser through the config file. So<br>
when OpenSER boots it fetches all the information includeing modules to<br>
load, etc,etc and configures the modules. I have also created a structure<br>
that holds addresses of all of my backend web service hosts. It is this<br>
pointer i want to make available to quite a few custom modules, hence the<br>
question.<br>
<br>
BUT, thanks for the help, its working like a charm!<br>
</blockquote>
<br>
That is a interesting architecture. :-) Good that it works now.<br>
</blockquote>
<br></div></div>
Might be fancy for example when using Amazon ECC and when you need more proxies just start up some Amazon images which fetch their config from a webservice.<br>
<br>
regards<br><font color="#888888">
klaus<br>
</font></blockquote></div><br>