Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Submitted By: Philippe Favier (quark38)
>Assigned to: Dan (dan_pascu)
Summary: call_control: TCP connection for external prepaid app
Added socket type TCP in addition to UNIX socket.
New config parameters:
o modparam("call_control", "socket_type", "tcp") # default = "unix"
o modparam("call_control", "server_name", "myserver.mydomain.com")
o modparam("call_control", "server_port", 5000)
Motivations for this patch:
o external prepaid application in Java (no Unix socket in Java)
o several openSIPS B2BUA's can be client to the same prepaid app
o prepaid app can run on a different server
>Comment By: Dan (dan_pascu)
Date: 2009-06-05 10:30
Are you aware of the callcontrol application, available from
That is a bridge between the opensips call_control module and the actual
With this application combined with the call_control opensips module, one
can already do all you list there. We currently have this running with:
- external prepaid application in PHP (the rating engine from CDRTool)
- multiple opensips proxies are clients to the same rating engine (via the
- rating engine runs on a different server
The external callcontrol application acts as a bridge between the opensips
call_control module and the prepaid engine.
On input it listens on the unix socket and it connects over tcp to the
From this point of view, it's much easier to modify this callcontrol
application to connect to your rating engine than to modify the opensips
module to talk tcp. One of the reasons why a direct TCP connection to the
rating engine was not considered in the first place is that tcp connections
can potentially freeze your proxy if the other site becomes unavailable.
Plus the callcontrol application is also able to keep track of time and
close the sessions that exceed their credit limit.