31 May
2008
31 May
'08
11:23 a.m.
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
31 May
31 May
1:54 p.m.
New subject: [OpenSER-Users] [OpenSER-Devel] New OpenSER-mi-proxy release 1.0.0
Adrian Georgescu writes:
This proxy replaces the need for OpenSER built-in
xml-rpc server,
which has
no access list and is prone to crash the server.
adrian,
we earlier had fifo_relay, which i didn't like at all because it
introduced yet another single point of failure to the system. i
therefore proposed to add access lists to current built-in xmlrpc
server. if i remember correctly, this was not deemed necessary because
one could use ip tables to limit access to the built-in server.
i don't remember seeing any bug reports on built-in xmlrpc server
crashing openser. if there are some, i think it would be very important
to get those bugs fixed so that an external xmlrpc proxy would not be
needed.
-- juha
2:30 p.m.
New subject: [OpenSER-Users] [OpenSER-Devel] New OpenSER-mi-proxy release 1.0.0
Hi Juha
Feel free to consider this a bug report.
We have encountered several problems with the built in xml-rpc server
which has several limitations.
1. No access list and managing IP tables is something I wish to avoid
2. No possibility to listen on a custom IP address, the server
listens on all interfaces
3. Random crashes for which after months of testing we could not
locate the source for. Practically we cannot use Presence in
production environment because of this.
Personally, I would be happy not to have an extra piece software to
install if the rpc server in OpenSER works fine but until is fixed
this solution works fine for me and I wanted to share it with others.
Adrian
On May 31, 2008, at 1:54 PM, Juha Heinanen wrote:
Adrian Georgescu writes:
This proxy replaces the need for OpenSER built-in
xml-rpc server,
which has
no access list and is prone to crash the server.
adrian,
we earlier had fifo_relay, which i didn't like at all because it
introduced yet another single point of failure to the system. i
therefore proposed to add access lists to current built-in xmlrpc
server. if i remember correctly, this was not deemed necessary
because
one could use ip tables to limit access to the built-in server.
i don't remember seeing any bug reports on built-in xmlrpc server
crashing openser. if there are some, i think it would be very
important
to get those bugs fixed so that an external xmlrpc proxy would not be
needed.
-- juha
2:37 p.m.
New subject: [OpenSER-Users] [OpenSER-Devel] New OpenSER-mi-proxy release 1.0.0
Adrian Georgescu writes:
Personally, I would be happy not to have an extra
piece software to
install if the rpc server in OpenSER works fine but until is fixed
this solution works fine for me and I wanted to share it with others.
adrian,
sure, no problems with that. i was just worried about possible openser
crashes caused by built-in xmlrpc interface that have not been reported
before.
what comed to your other concerns, they are exactly the same ones that i
expressed on built-in xmlrpc server. unfortunately i have not heard of
any better xmlrpc server c library than then one openser is using.
-- juha
5:13 p.m.
New subject: [OpenSER-Users] [OpenSER-Devel] New OpenSER-mi-proxy release 1.0.0
On Saturday 31 May 2008, Juha Heinanen wrote:
Adrian Georgescu writes:
I think there is a confusion here. There are no crashes related to the
xmlrpc interface. The problem is that when using the xmlrpc interface,
after a while the xmlrpc MI process freezes and refuses to answer any
more requests. All the rest of openser works just fine, but xmlrpc is
dead and won't recover without a restart. I reported the problem here and
it was also acknowledged by someone else who inspected the code and
suggested that the issue may be with the abyss code not releasing the
connections and not accepting new connections after a certain number of
unreleased connections are present.
--
Dan
Personally, I would be happy not to have an extra
piece software to
install if the rpc server in OpenSER works fine but until is fixed
this solution works fine for me and I wanted to share it with
others.
adrian,
sure, no problems with that. i was just worried about possible openser
crashes caused by built-in xmlrpc interface that have not been reported
before. 
5 Jun
5 Jun
4:27 p.m.
New subject: [OpenSER-Users] [OpenSER-Devel] New OpenSER-mi-proxy release 1.0.0
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. 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
4:51 p.m.
New subject: [OpenSER-Users] [OpenSER-Devel] New OpenSER-mi-proxy release 1.0.0
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
6 Jun
6 Jun
2:31 p.m.
New subject: [OpenSER-Users] [OpenSER-Devel] New OpenSER-mi-proxy release 1.0.0
Adrian Georgescu schrieb:
On Jun 5, 2008, at 4:27 PM, Klaus Darilion wrote:
klaus
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. What interface does the MI-proxy use to openser? Does it use
FIFO?
5802
days inactive
5808
days old
7 comments
4 participants
participants (4)
-
Adrian Georgescu -
Dan Pascu -
jh＠tutpro.com -
Klaus Darilion