On Jun 5, 2008, at 4:27 PM, Klaus Darilion wrote:
Hi Adrian!
I am not sure if I got it right - the MI-proxy is just a proxy. Thus
it forwards requests from the client to the MI interface of openser.
Thus, openser's (potential buggy?) MI server is still used.
Only the rpc part is buggy
Thus, how does the proxy increases stability?
thanks
klaus
Adrian Georgescu schrieb:
> Hello,
> There is a new component useful for implementing the presence
> server solution using OpenSER and OpenXCAP.
> OpenSER MI Proxy
> ----------------
> OpenSER MI Proxy is designed to allow remote XML-RPC clients to
> issue MI
> commands to OpenSER.
> This proxy replaces the need for OpenSER built-in xml-rpc server,
> which has
> no access list and is prone to crash the server.
> One of its purposes is to allow a remote OpenXCAP server to safely
> call the
> refreshWatchers() command on the management interface of the SIP
> Presence
> server when the presence policy document has changed.
> The proxy can listen on custom IP addresses and provides an access
> list for
> the clients allowed to connect.
> The software can be downloaded from:
>
http://download.ag-projects.com/OpenXCAP/
> Kind regards,
> Adrian Georgescu
> _______________________________________________
> Devel mailing list
> Devel(a)lists.openser.org
>
http://lists.openser.org/cgi-bin/mailman/listinfo/devel