[SR-Users] CFGUtils module question
Hello Can somebody help me understand the example given with MI command "is_gflag"? ... $ kamctl fifo set_gflag 1024 $ kamctl fifo is_gflag 1024 TRUE $ kamctl fifo is_gflag 1025 TRUE $ kamctl fifo is_gflag 1023 FALSE $ kamctl fifo set_gflag 0x10 $ kamctl fifo is_gflag 1023 TRUE $ kamctl fifo is_gflag 1007 FALSE $ kamctl fifo is_gflag 16 TRUE This is how I understand it. There are 32 posible flags (0..31), each one can be set independently. The commands "is_flag" and "set_gflag" expect a bitmask as value (decimal or hex) If I set "kamctl fifo set_gflag 1024", this means "100 ", I expect that the only flag that has been set to 1 is the position 10. How come the command "kamctl fifo is_gflag 1025" which is "100 0001" can yield TRUE?. I expect it to be TRUE only if flags 0 and 10 are both set to 1. Same thing with setting the flag to 0x10 (16 in decimal, "1 " in binary), how come the "is_gflag 1023 and is_gflag 1007" can return TRUE? tx a lot fborot ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio Unexpectedly Terminating
Hello, On 5/30/12 9:10 PM, Akan wrote: This was a re-pull from the git master. I had deleted all of the old files and issued these commands: git clone --depth 1 git://git.sip-router.org/sip-router kamailio cd kamailio git checkout -b 3.2 origin/3.2 This is the source that I got. Could this be a problem within git? do not checkout branch 3.2, just try with the master branch, as said, not all patches are backported to stable 3.2. For sake of completeness, here are some guidelines: http://www.kamailio.org/wiki/install/devel/git Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio Unexpectedly Terminating
This was a re-pull from the git master. I had deleted all of the old
files and issued these commands:
git clone --depth 1 git://git.sip-router.org/sip-router kamailio
cd kamailio
git checkout -b 3.2 origin/3.2
This is the source that I got. Could this be a problem within git?
Thanks
Nathaniel
On 5/30/2012 9:55 AM, Daniel-Constantin Mierla wrote:
Hello,
On 5/30/12 4:26 AM, Akan wrote:
Sorry. To make sure I got the right versions, I removed all of the
previous files, reloaded and re-compiled Kamailio from git and ran
the test again.
is it git master branch? Because the branch 3.2 does not have all
patches backported, as I wanted to test them first, 3.2 is a stable
branch used in production.
It does not seem the latest as the line of crash is reporting to be:
102 realm_prefix.s = cfg_get(registrar,
registrar_cfg, realm_pref);
And the last source code is:
realm_prefix.s = cfg_get(registrar, registrar_cfg, realm_pref).s;
Can you try with latest git master branch? At least will be sure it is
the right source code.
Cheers,
Daniel
I have included the full trace files from the core dump. Here is my
setting for use_domain parameter:
#!define MULTIDOMAIN 1
modparam("usrloc", "db_url", DBURL)
modparam("usrloc", "db_mode", 2)
modparam("usrloc", "use_domain", MULTIDOMAIN)
Thanks
Nathaniel L Keeling
On 5/29/2012 4:15 AM, Daniel-Constantin Mierla wrote:
Hello,
is this with use_domain parameter set?
Also, from the backtrace, the condition is not
104 if (realm_prefix.len>0 &&
realm_prefix.len
but
104 if (realm_prefix.len &&
realm_prefix.len
It looks it is without the last recommendation I made - now I pushed
the change also in master branch.
Cheers,
Daniel
On 5/29/12 10:55 AM, Akan wrote:
I am still getting a core dump with Kamailio v3.2. I loaded
Kamailio on a new server, applied the patch and started testing. I
was able to register successfully which previously I was not, but
now when I try to make a call, kamailio will take a core dump. I
also loaded Kamailio v3.1 just to make sure that it is not a memory
issue and I was able to place a call successfully without Kamailio
taking a core dump. I have included the full backtrace from the
dump and it looks like it is in the same place as previously. I
loaded Kamailio v3.2 on 3 different servers with the same results
of producing a core dump. I have not tried the new development
version yet.
Thanks
Nathaniel
On 5/23/2012 1:44 AM, Akan wrote:
I'd setup another solaris server with kamailio v3.2, applied the
patch and tested the change. Kamailio did not crash nor took a
core dump. So it looks like it might be a hardware problem now.
Thanks
Nathaniel
On 5/9/2012 1:52 PM, Akan wrote:
I changed the use_domain parameter for usrloc to 0 and retried.
Kamailio did not crash and I was able to get registered. I have
another server with the same configurations as the one having the
problem. I will apply the patch there and see if the problem
still occurs. Also, setting the use_domain to 0 for usrloc, does
this limit me to not being able to use other domains within the
SIP message?
Thanks
Nathaniel
On 5/9/2012 3:05 AM, Daniel-Constantin Mierla wrote:
Hello,
I see no reason why it crashes at line 104 when
realm_prefix.len==0.
Might be a memory problem (hardware). Can you try with
use_domain parameter set to 0 for usrloc module?
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Max registered users
Hello, On 5/30/12 4:12 PM, Vitaliy Aleksandrov wrote: Hi all, I'm trying to find a way to get a number of the registered user locations and if it is bigger that some limit then kamailio will not save new registrations. reg_fetch_contacts() from registrar module doesn't help as it can fetch contacts only for one user. max_contacts parameter of the registrar module limits the number of contacts per AOR, but i need to limit max number of all contacts that proxy will keep in usrloc. the usrloc module exports a statistics counter with all existing contacts (iirc, it is named 'contacts'). You can access any of the internal statistics via $stat(name), like $stat(contacts). This should give you the value to compare against in the configuration file, not to exceed a specific upper limit. Cheers, Daniel Thank you very much ! $stat() is just what i looked for. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio Unexpectedly Terminating
Hello,
On 5/30/12 4:26 AM, Akan wrote:
Sorry. To make sure I got the right versions, I removed all of the
previous files, reloaded and re-compiled Kamailio from git and ran the
test again.
is it git master branch? Because the branch 3.2 does not have all
patches backported, as I wanted to test them first, 3.2 is a stable
branch used in production.
It does not seem the latest as the line of crash is reporting to be:
102 realm_prefix.s = cfg_get(registrar, registrar_cfg,
realm_pref);
And the last source code is:
realm_prefix.s = cfg_get(registrar, registrar_cfg, realm_pref).s;
Can you try with latest git master branch? At least will be sure it is
the right source code.
Cheers,
Daniel
I have included the full trace files from the core dump. Here is my
setting for use_domain parameter:
#!define MULTIDOMAIN 1
modparam("usrloc", "db_url", DBURL)
modparam("usrloc", "db_mode", 2)
modparam("usrloc", "use_domain", MULTIDOMAIN)
Thanks
Nathaniel L Keeling
On 5/29/2012 4:15 AM, Daniel-Constantin Mierla wrote:
Hello,
is this with use_domain parameter set?
Also, from the backtrace, the condition is not
104 if (realm_prefix.len>0 &&
realm_prefix.len
but
104 if (realm_prefix.len &&
realm_prefix.len
It looks it is without the last recommendation I made - now I pushed
the change also in master branch.
Cheers,
Daniel
On 5/29/12 10:55 AM, Akan wrote:
I am still getting a core dump with Kamailio v3.2. I loaded Kamailio
on a new server, applied the patch and started testing. I was able
to register successfully which previously I was not, but now when I
try to make a call, kamailio will take a core dump. I also loaded
Kamailio v3.1 just to make sure that it is not a memory issue and I
was able to place a call successfully without Kamailio taking a core
dump. I have included the full backtrace from the dump and it looks
like it is in the same place as previously. I loaded Kamailio v3.2
on 3 different servers with the same results of producing a core
dump. I have not tried the new development version yet.
Thanks
Nathaniel
On 5/23/2012 1:44 AM, Akan wrote:
I'd setup another solaris server with kamailio v3.2, applied the
patch and tested the change. Kamailio did not crash nor took a core
dump. So it looks like it might be a hardware problem now.
Thanks
Nathaniel
On 5/9/2012 1:52 PM, Akan wrote:
I changed the use_domain parameter for usrloc to 0 and retried.
Kamailio did not crash and I was able to get registered. I have
another server with the same configurations as the one having the
problem. I will apply the patch there and see if the problem still
occurs. Also, setting the use_domain to 0 for usrloc, does this
limit me to not being able to use other domains within the SIP
message?
Thanks
Nathaniel
On 5/9/2012 3:05 AM, Daniel-Constantin Mierla wrote:
Hello,
I see no reason why it crashes at line 104 when realm_prefix.len==0.
Might be a memory problem (hardware). Can you try with use_domain
parameter set to 0 for usrloc module?
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 -
http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 -
http://asipto.com/u/kpw
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Max registered users
Hello, On 5/30/12 4:12 PM, Vitaliy Aleksandrov wrote: Hi all, I'm trying to find a way to get a number of the registered user locations and if it is bigger that some limit then kamailio will not save new registrations. reg_fetch_contacts() from registrar module doesn't help as it can fetch contacts only for one user. max_contacts parameter of the registrar module limits the number of contacts per AOR, but i need to limit max number of all contacts that proxy will keep in usrloc. the usrloc module exports a statistics counter with all existing contacts (iirc, it is named 'contacts'). You can access any of the internal statistics via $stat(name), like $stat(contacts). This should give you the value to compare against in the configuration file, not to exceed a specific upper limit. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Max registered users
Hi, just curious, why do you want to do this, cluster/distributed registrations? One solution which immediately comes to my mind: just query the db(location table) for the number of registrations, and compare the results to a value defined in your opensips script. If the number of registrations (entries in table) is >= your defined value then don`t save the registration / don`t call save(). Best Regards Max M. On 05/30/2012 04:12 PM, Vitaliy Aleksandrov wrote: Hi all, I'm trying to find a way to get a number of the registered user locations and if it is bigger that some limit then kamailio will not save new registrations. reg_fetch_contacts() from registrar module doesn't help as it can fetch contacts only for one user. max_contacts parameter of the registrar module limits the number of contacts per AOR, but i need to limit max number of all contacts that proxy will keep in usrloc. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Max registered users
Hi all, I'm trying to find a way to get a number of the registered user locations and if it is bigger that some limit then kamailio will not save new registrations. reg_fetch_contacts() from registrar module doesn't help as it can fetch contacts only for one user. max_contacts parameter of the registrar module limits the number of contacts per AOR, but i need to limit max number of all contacts that proxy will keep in usrloc. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] acc: can't get code for the Source-IP attribute
Le 30/05/2012 12:12, Rabary a écrit : Hi all, When I start kamailio, I have theses errors in syslog and kamailio failed to start: May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: INFO: usrloc [hslot.c:53]: locks array size 512 May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: INFO: auth [auth_mod.c:312]: auth: qop set, but nonce-count (nc_enabled) support disabled May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: ERROR: acc_radius [acc_radius_mod.c:276]: acc: can't get code for the Source-IP attribute May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: ERROR: acc_radius [acc_radius_mod.c:289]: failed to init radius May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: ERROR: acc [acc_mod.c:758]: failed to initialize extra acc engine May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: ERROR: acc_radius [acc_radius_mod.c:154]: cannot register ACC RADIUS engine May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: ERROR: [sr_module.c:932]: init_mod(): Error while initializing module acc_radius (/usr/lib/kamailio/modules_k/acc_radius.so) In radiusclient dictionary.sip, I have this: teddy@kamailio:~$ sudo grep -r -i source-ip /etc/radiusclient-ng/* /etc/radiusclient-ng/dictionary.sip:ATTRIBUTE Sip-Source-IP-Address108ipaddr And in dictionary file I include this dictionary.sip like this at the end of the file: $INCLUDE/etc/radiusclient-ng/dictionary.sip There are kamailio and libradiusclient-ng2 version installed: ii kamailio 3.2.3+squeeze1 very fast and configurable SIP proxy ii kamailio-mysql-modules 3.2.3+squeeze1 MySQL database connectivity module for Kamailio ii kamailio-radius-modules3.2.3+squeeze1 radius modules for Kamailio ii libradiusclient-ng-dev 0.5.6-1.1 Enhanced RADIUS client library development files ii libradiusclient-ng20.5.6-1.1 Enhanced RADIUS client library So I don't know where I'm doing wrong, can anyone tell me what am I missing ? Thanks. solved, it was a problem of dictionary, sorry for the inconvenience. -- Rabary Teddy Inutile d'imprimer ce mail ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] PUA_RegInfo patch
Hi Gnaneshwar, i just applied and commited the patch. Thanks, Carsten 2012/5/22 Gnaneshwar Gatla : > Hey, > > I have fixed the incorrect uri’s being generated by this module while > publishing user location. This patch also includes some more user record > data to the xml during publish. > > I’m not sure if I have followed the naming convention right. Please find the > patch file attached. > > > > Regards, > > Gnaneshwar Gatla | InTouch Health | Software Developer > > 6330 Hollister Ave. Goleta CA, 93117 | P: 805.562.8686 ext: 199 > > > > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users > -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany http://www.ng-voice.com mailto:cars...@ng-voice.com Mobile +49 179 2021244 Office +49 40 34927219 Fax +49 40 34927220 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/ ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [NOT Solved]Creating RURI ($ru) from Contact ($ct)
On Wed, May 30, 2012 at 4:37 PM, Andrew Pogrebennyk wrote: > Hi, > > On 05/30/2012 12:22 PM, Aft nix wrote: >> So i'm interested if RFC 3261 provides any mechanism by which we can >> differentiate a BYE whether its from "caller" or "callee". > > Check out is_direction() function: > http://www.kamailio.org/docs/modules/3.2.x/modules_k/rr.html#id2527009 Hi Andrew, Thank you for the reply. I will test and post updates. Cheers. > > ___ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- -aft ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [NOT Solved]Creating RURI ($ru) from Contact ($ct)
Hi, On 05/30/2012 12:22 PM, Aft nix wrote: > So i'm interested if RFC 3261 provides any mechanism by which we can > differentiate a BYE whether its from "caller" or "callee". Check out is_direction() function: http://www.kamailio.org/docs/modules/3.2.x/modules_k/rr.html#id2527009 ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] [NOT Solved]Creating RURI ($ru) from Contact ($ct)
On Tue, May 29, 2012 at 3:03 PM, Aft nix wrote:
> On Tue, May 29, 2012 at 2:57 PM, Daniel-Constantin Mierla
> wrote:
>> Hello,
>>
>> in kamailio, if you want to apply immediately the changes done to the sip
>> request, then use msg_apply_changes() from textopsx module. Then you can
>> access it with the contact PV.
>>
>> Also, the pvs for source ip and port are $si and $sp -- see the PV cookbook
>> in the wiki site at kamailio.org
>>
>> Cheers,
>> Daniel
>>
>
> Hi Daniel,
>
> Thank you for quick reply. I will test both and post updates.
> Cheers.
>
Hi Daniel
The problem which i was facing is solved by adding a call
"msg_apply_changes()" after route[NATDETECT].
But i'm facing a new problem. As its the "callee" who always generates
the malformed "BYE", so i need to differentiate if the BYE is from
caller or callee.
It can be done with hardcoded IP address of my gateway , but it does
not seems OK to me.
So i'm interested if RFC 3261 provides any mechanism by which we can
differentiate a BYE whether its from "caller" or "callee".
Cheers.
>>
>> On 5/29/12 10:39 AM, Aft nix wrote:
>>>
>>> Hi,
>>>
>>> Sorry guyz, the problem is not solved as i thought. The script worked
>>> perfectly in my lab where i did'nt know that the wifi router is a so
>>> called "sip friendly router". It fixes broken contacts so it worked
>>> perfectly in my lab.
>>>
>>> But in my production server it did'nt work.
>>>
>>> Problem is when i put "contact" in hash table entry like following :
>>>
>>> sht(a=>$ci) = $ct;
>>>
>>> it puts the broken contact adress( I mean contact address with private
>>> IP) into the hashtable.
>>>
>>> At first i put my code after the execution of "fix_nated_contact()".
>>> But it did'nt work. Then i put a xlog() to print $ct. And to my
>>> surprise i saw that its printing the private IP instead of the public
>>> one. After searching through mailing list archives i came across this
>>> :
>>>
>>> http://lists.iptel.org/pipermail/serusers/2006-September/030511.html
>>>
>>> According to this although the contact is fixed with received IP and
>>> port, its not applied to the message buffer and kept in temporary
>>> storage. when the message is about to be sent over sockets this
>>> temporary storage is applied over the the original message buffer.
>>> pseudo variables like $ct will always reference to the original
>>> message, not the modified one after fix_nated_contact().
>>>
>>> So to populate my hashtable, i have to choices:
>>>
>>> 1. I can reference src_ip and src_port , put a ":" between them like
>>> following :
>>>
>>> sht(a=>$ci) = $fU + src_ip + ":" + src_port (Please help with the
>>> correct syntax for string concatenation).
>>>
>>> 2. Or if possible i reference the changed contact from the temporary
>>> storage, and put this into my hashtable.
>>>
>>> Please direct me which way should i go.
>>>
>>> Cheers.
>>>
>>> On Mon, May 28, 2012 at 8:25 PM, Aft nix wrote:
Hi all,
I'm posting the script which worked. In future if anybody faces the
same problem can get a solution out of this.
In request_route:
#!ifdef WITH_HASH
if (is_method("INVITE") && !has_totag()){
xdbg ("Contact [$ct] with Callid [$ci]");
$sht(a=>$ci) = $ct;
}
#!endif
in route[WITHINDLG]
#!ifdef WITH_HASH
xdbg ("ruri [$ru]");
if ($(sht(a=>$ci){nameaddr.uri}) != $ru){
xdbg ("hash table entry
[$sht(a=>$ci)]");
$ru =
$(sht(a=>$ci){nameaddr.uri});
sht_rm_name_re("ha=>$ci");
xdbg ("rewriting ruri to [$ru]");
}
#!endif
Thanks everyone for the help. I'm marking this thread as solved.
--
-aft
--
-aft
>>>
>>>
>>>
>>
>> --
>> Daniel-Constantin Mierla - http://www.asipto.com
>> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>> Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 -
>> http://asipto.com/u/katu
>>
>>
>>
>
>
>
> --
> -aft
--
-aft
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] acc: can't get code for the Source-IP attribute
Hi all, When I start kamailio, I have theses errors in syslog and kamailio failed to start: May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: INFO: usrloc [hslot.c:53]: locks array size 512 May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: INFO: auth [auth_mod.c:312]: auth: qop set, but nonce-count (nc_enabled) support disabled May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: ERROR: acc_radius [acc_radius_mod.c:276]: acc: can't get code for the Source-IP attribute May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: ERROR: acc_radius [acc_radius_mod.c:289]: failed to init radius May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: ERROR: acc [acc_mod.c:758]: failed to initialize extra acc engine May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: ERROR: acc_radius [acc_radius_mod.c:154]: cannot register ACC RADIUS engine May 30 12:02:11 kamailio /usr/sbin/kamailio[5652]: ERROR: [sr_module.c:932]: init_mod(): Error while initializing module acc_radius (/usr/lib/kamailio/modules_k/acc_radius.so) In radiusclient dictionary.sip, I have this: teddy@kamailio:~$ sudo grep -r -i source-ip /etc/radiusclient-ng/* /etc/radiusclient-ng/dictionary.sip:ATTRIBUTE Sip-Source-IP-Address108ipaddr And in dictionary file I include this dictionary.sip like this at the end of the file: $INCLUDE/etc/radiusclient-ng/dictionary.sip There are kamailio and libradiusclient-ng2 version installed: ii kamailio 3.2.3+squeeze1 very fast and configurable SIP proxy ii kamailio-mysql-modules 3.2.3+squeeze1 MySQL database connectivity module for Kamailio ii kamailio-radius-modules3.2.3+squeeze1 radius modules for Kamailio ii libradiusclient-ng-dev 0.5.6-1.1 Enhanced RADIUS client library development files ii libradiusclient-ng20.5.6-1.1 Enhanced RADIUS client library So I don't know where I'm doing wrong, can anyone tell me what am I missing ? Thanks. -- Rabary Teddy Inutile d'imprimer ce mail ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
