Yes I applay patch with follow command:
mkdir freeRADIUS-client;
cd freeRADIUS-client
wget ftp://ftp.freeradius.org/pub/freeradius/freeradius-client-1.1.7.tar.gz
tar -xzvf freeradius-client-1.1.7.tar.gz
cd freeRADIUS-client/freeradius-client-1.1.7.tar.gz
patch -p1 <
Did you follow the steps in the docs on how to apply the async patch[0]
if you want to use it?
[0] http://www.opensips.org/html/docs/modules/2.2.x/aaa_radius#id294296
Ionut Ionita
OpenSIPS Developer
On 01/09/2017 03:04 PM, Dragomir Haralambiev wrote:
Hi,
Thanks for your quick replay.
When
Hi,
Thanks for your quick replay.
When try to start Opensips with aaa_radius support I receive follow Errors:
Jan 9 14:57:40 dev opensips: ERROR:core:sr_load_module: could not open
module :
/usr/local/lib64/opensips/modules/aaa_radius.so: undefined symbol:
rc_acct_resume
Jan 9 14:57:40 dev
I reed docs for AAA Radius module1.2.2. External Libraries or Applications
.
By default, radiusclient-ng is used. To change at compile time to
freeradius, uncomment the USE_FREERADIUS=1 line in main Makefile.
In Makefile I not see USE_FREERADIUS=1. Here is only FREERADIUS.
If use
you need to set this parameter for the module to load correctly
Jan 9 12:30:34 dev opensips: ERROR:core:set_mod_param_regex: no module
matching aaa_radius found
On Mon, Jan 9, 2017 at 10:36 AM, Dragomir Haralambiev
wrote:
> Hello,
>
> Here is my problem:
>
> OpenSips 2.2.2
Hello,
Here is my problem:
OpenSips 2.2.2 - latest
OS - CentOS Linux release 7.3.1611
opensips.cfg
.
loadmodule "aaa_radius.so"
..
aaa_radius.so exists in /usr/local/lib64/opensips/modules
Here is list of Eroors
Jan 9 12:30:34 dev opensips: ERROR:core:sr_load_module: could not open
> On 9/01/2017, at 9:35 PM, Nick Altmann wrote:
>
> For example sshd. Do you also run it instead of ssh?
No, as that is longer, so it doesn’t really make sense that someone would run
that. In this case, the user typed “opensi monitor”.
Running “ssh” instead of
> On 9/01/2017, at 9:36 PM, Răzvan Crainea wrote:
>
> Hello, Nathan!
Hi!
> You have my answer inline.
Likewise.
> On 01/07/2017 11:10 AM, Nathan Ward wrote:
>> Hi,
>>
>> I am running OpenSIPS 2.2.2 from RPMs from the opensips.org yum server.
>>
>> I am trying to find
Actually as Nick pointed out, the rpm specs used are here:
https://github.com/OpenSIPS/opensips/tree/2.2/packaging/redhat_fedora
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 01/09/2017 10:36 AM, Răzvan Crainea wrote:
Hello, Nathan!
You have my answer inline.
Hello, Nathan!
You have my answer inline.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 01/07/2017 11:10 AM, Nathan Ward wrote:
Hi,
I am running OpenSIPS 2.2.2 from RPMs from the opensips.org yum server.
I am trying to find out where the SPEC files to
Hello,
You could find packaging specification in packaging/redhat_fedora folder in
git tree.
However in my opinion there is no need to change opensips binary into
libexec folder.
There is no general rule to do it, most daemons in rhel are placed in
/usr/sbin as opensips.
For example sshd. Do you
No, unfortunately there is no way to install the systemd files
automatically, you have to do it manually.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com
On 01/08/2017 10:49 PM, Robert Dyck wrote:
I had a working opensips 1.11 installed by Fedora package manager. I
Hello, Khalil!
If you check the documentation of the do_routing function[1], you will
see that the group is not mandatory. If it exists, then it will use the
route set within that group. If it does not exist, the group is
determined from the dr_group table in the database - this is just a
13 matches
Mail list logo