After remeoved the support of DIAMETER mmodule from openser, tt works fine now. I have registered some numbers to it and will test it tonight with remote xlite users. BUT, what is DIAMETER? I read some post in voip forum, someone said it is far too outdated. I am wondering what it is, and what should be used to replace DIAMETER.
Thanks for helping me along to solve the issues. Sam
----- Original Message ---- From: Christian Schlatter cs@unc.edu To: norm@goes.com Cc: Live Great livegreat007@yahoo.com; users@openser.org Sent: Wednesday, October 3, 2007 10:44:06 AM Subject: Re: [OpenSER-Users] Re: can't get code for the src-leg attribute
Norman Brandinger wrote:
First,
The three radius messages from the radius log are just INFO messages, not error messages. This is a good thing.
Try using the lowest possible unused number for the attributes. My attributes are in the 240 range. Again, I haven't tested it but perhaps radius has an upper limit of maybe 255 or maybe 1024.
The upper limit is 255 because there is only one byte for RADIUS attribute types.
http://www.iana.org/assignments/radius-types
I'd suggest to either use 124-223 or 241-255 for things like src/dst-leg.
/Christian
Norm
Hi Norman,
Thanks for the reply. According to your suggestion, I have added the following lines in
raddb/dicitionary:
ATTRIBUTE Src-Leg 1075 integer
ATTRIBUTE Dst-Leg 1076 integer
change in radiusclient-ng/dictionary: ATTRIBUTE Src-Leg 1075 integer ATTRIBUTE Dst-Leg 1076 integer
change in openser/openser.cfg: #modparam("acc", "multi_leg_info",
"src_leg=$avp(i:901);dst_leg=$avp(i:902)")
modparam("acc", "multi_leg_info",
"Src-Leg=$avp(i:901);Dst-Leg=$avp(i:902)")
Note, I have commented out the original src_leg/dst_leg definition. I don't know what is that i:901 and i:902 means, so I simply change
the first letter to upper
case and change "_" to "-".
Restarted radiusd, and try to start openser then found the following
error in the
/var/log/messages file: ERROR:acc:extra2int: <Src-Leg> is not a number
When I started radiusd, there are info messages written to
/var/log/radiusd.log file:
Wed Oct 3 09:28:45 2007 : Info: Using deprecated naslist file.
Support for this will go away
soon. Wed Oct 3 09:28:45 2007 : Info: rlm_exec: Wait=yes but no output
defined. Did you mean
output=none? Wed Oct 3 09:28:45 2007 : Info: Ready to process requests.
Thanks Sam
----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com Cc: users@openser.org Sent: Wednesday, October 3, 2007 3:26:40 AM Subject: Re: can't get code for the Failed attribute
Hi Sam,
If you altered the dictionary entries, you MUST make sure that your openser.cfg, has also been updated.
For example:
modparam("acc", "radius_extra", "Src-Leg=$avp(s:source_leg); Dst-Leg=$avp(s:destination_leg)")
Note that Src-Leg and Dst-Leg MUST be in the dictionary for BOTH radiusclient-ng AND radiusd.
Regards, Norm
Live Great wrote:
Hi,
In your example, do you meant openser will trainsform Src-Leg to src_leg and Dst-Leg to dst_leg? After I followed your suggestion and changed the definition to, ATTRIBUTE Src-Leg 1075 string ATTRIBUTE Dst-Leg 1076 string
I get an error: ERROR: acc: can't get code for the src_leg attribute
I have a feeling that it is case sensitive, and openser is looking for src_leg instead Src-Leg.
Thanks Sam.
----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com Cc: users@openser.org Sent: Tuesday, October 2, 2007 9:42:15 PM Subject: Re: can't get code for the Failed attribute
Hello Sam,
The definition you used:
ATTRIBUTE src_leg 0 string
Probably isn't valid because "0" is more than likely already being used. Notice that the various ATTRIBUTE numbers are all unique and just increment. So use the next higher number that is available. If the last ATTRIBUTE was 240 then your definition might look like:
ATTRIBUTE src_leg 241 string
You might also want to consider the general naming convention that is used. The above example would then look as follows:
ATTRIBUTE Src-Leg 241 string Note, when you get around to inserting this data into a database, the column name will probably not be allowed to have a dash (unless the column name is quoted).
Regards, Norm
Live Great wrote:
It looks like it doesn't look up the dictionary files in /usr/local/share/freeradius/ directory. But src_leg and dst_leg are not defined in the share directory.
Sam.
----- Original Message ----
From: Live Great livegreat007@yahoo.com
To: Norman Brandinger norm@goes.com Cc: users@openser.org Sent: Tuesday, October 2, 2007 10:17:47 AM Subject: Re: can't get code for the Failed attribute
Hi Norman,
Thank you for the reply. With the definition of "ATTRIBUTE src_leg 0 string", I got an error "src_leg is not a number". After changed it to the following definition, ATTRIBUTE Acct-Status-Type 40 integer ATTRIBUTE Service-Type 6 integer ATTRIBUTE Event-Timestamp 55 integer ATTRIBUTE Acct-Session-Id 44 string ATTRIBUTE src_leg 1 integer ATTRIBUTE dst_leg 1 integer VALUE Acct-Status-Type Start 1 VALUE Acct-Status-Type Stop 2 VALUE Acct-Status-Type Failed 0 VALUE Service-Type Sip-Session 15
I still got this error: ERROR:acc:extra2int: <src_leg> is not a number
Thanks Sam ----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com Cc: users@openser.org Sent: Tuesday, October 2, 2007 9:43:41 AM Subject: Re: can't get code for the Failed attribute
Hi Sam,
In /usr/local/share/freeradius/dictionary.rfc2866 there exists the following entry:
VALUE Acct-Status-Type Failed 15
I'm not an expert in this area, but it appears that "Failed" is
sort of
predefined. You probably should NOT use "Failed", instead create a unique attribute such as "failed-reason". This is of course assuming the rest of your definitions are good.
Please do not cross-post configuration questions of this type to the developers mailing list.
Regards, Norm
Live Great wrote:
Hi,
After added the following Attributes in the
radiusclient-ng/dictionary
file: ATTRIBUTE src_leg 0 string ATTRIBUTE dst_leg 0 string ATTRIBUTE Failed 0 string
I got the following error: ERROR: acc: can't get code for the Failed attribute value
How to define a proper attribute in the dictionary file? Thanks Sam
----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com Cc: devel@openser.org Sent: Monday, October 1, 2007 9:01:54 PM Subject: Re: [OpenSER-Devel] can't get code for the
Sip-Response-Code
attribute
Good Morning,
You need to make sure the dictionary settings are correct and
exactly
match what you have specified in OpenSER.
The dictionaries are specified in radiusclient-ng and in radiusd
(and
mediaproxy if you use it)
The error is telling you that "Sip-Response-Code" cannot be found
in any
of the dictionaries you have specified.
Regards, Norm
Live Great wrote:
Hi,
I still can't this work, that's why I posted in the development
forum.
I have installed openser with *_ACC=ture uncommented in the
acc/Makfile..
But I can't start openser now. Here is the error when I executed /usr/local/etc/rc.d/openser
start:
core:rc.d # ./openser start Command Monit to start OpenSER... 'openser' start: /usr/local/etc/rc.d/openser 'openser' failed to start Starting Open SIP Router: Listening on udp: 127.0.0.1 [127.0.0.1]:5060 udp: 12x..x.x..x [12x.x.x.x]:5060 Aliases: udp: xxx..xxx..com.au:5060 udp: localhost.xxx.com.au:5060 udp: localhost:5060
In /var/log/messages: ERROR: acc: can't get code for the Sip-Response-Code attribute ERROR:acc:mod_init: failed to init radius
core:rc.d # ps -auxww | grep openser root 35219 0.0 0.1 1520 728 p2 R+ 12:03AM 0:00.00 grep
openser
core:rc.d # ps -auxww | grep radius root 35230 0.0 0.3 5004 3256 ?? Ss 12:04AM 0:00.00 /usr/local/sbin/radiusd core:rc.d # ps -auxww | grep mysql mysql 75881 0.0 0.1 1732 1116 p1- I 20Sep07 0:00.02
/bin/sh
/usr/local/bin/mysqld_safe --defaults-extra-file=/usr/local/var/db/mysql/my.cnf --user=mysql --datadir=/usr/local/var/db/mysql --pid-file=/usr/local/var/db/mysql/core.xxx.com.au.pid mysql 75924 0.0 2.7 49016 28336 p1- S 20Sep07 10:52.77
[mysqld]
root 35237 0.0 0.1 1544 644 p2 RL+ 12:05AM 0:00.00 grep
mysql
Why I got thos acc errors when starting openser?
Thanks SW
----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com Cc: FreeRadius users mailing list freeradius-users@lists.freeradius.org; users@openser.org Sent: Friday, September 28, 2007 11:11:23 PM Subject: Re: [OpenSER-Users] Failed to compile openser with
freeradius
support
Comment the FREERADIUS=1 in the openser/Makefile
Make sure that in modules/acc/Makefile ENABLE_RADIUS_ACC=true
is not
commented
Regards, Norm
Live Great wrote: > HI, > > In FreeBSD 6.2, I got this error when I compiled openser with > freeradius support. > > ../../radius.h:36:32: freeradius-client.h: No such file or
directory
> acc.c: In function `init_acc_rad': > acc.c:464: warning: assignment makes pointer from integer
without
a cast
> acc.c:475: error: `DICT_ATTR' undeclared (first use in this
function)
> acc.c:475: error: (Each undeclared identifier is reported only
once
> acc.c:475: error: for each function it appears in.) > acc.c:475: error: `da' undeclared (first use in this function) > acc.c:475: error: `DICT_VALUE' undeclared (first use in this
function)
> acc.c:475: error: `dv' undeclared (first use in this function) > acc.c: In function `acc_rad_request': > acc.c:509: error: `VALUE_PAIR' undeclared (first use in this
function)
> acc.c:514: error: invalid lvalue in assignment > acc.c:555: error: `OK_RC' undeclared (first use in this
function)
> gmake[1]: *** [acc.o] Error 1 > gmake[1]: Leaving directory > `/usr/ports/net/openser/work/openser-1.2.2-tls/modules/acc' > gmake: *** [modules] Error 2 > *** Error code 2 > > Stop in /usr/ports/net/openser. > *** Error code 1 > > Is there any way I can compile openser with freeradius support? > > Thanks > SW >
Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Sam,
Here is a little information about Diameter: http://ing.ctit.utwente.nl/WU5/D5.1/Technology/diameter/
Christian was absolutely correct as quoted from the above URL:
Strict limitation of attribute data Radius has only one byte reserved for the length of a datafield (max. 255) in its attribute header. Diameter reserves two bytes for its length of a datafield (max. 16535).
The web site: www.diameter.org is currently not active.
The web site: www.opendiameter.org is active and the latest release was March 2007. A quick review of the SVN repository shows the last update 2 weeks ago. This would lead me to believe that OpenDiameter is actively being developed.
Regards, Norm
After remeoved the support of
DIAMETER mmodule from openser, tt works fine now.
I have registered some numbers to it
and will test it tonight with remote xlite users.
BUT, what is DIAMETER? I read some
post in voip forum, someone said it is far too outdated.
I am wondering what it is, and
what should be used to replace DIAMETER.
Thanks for helping me along to
solve the issues.
Sam
----- Original Message ----
From: Christian Schlatter cs@unc.edu
To: norm@goes.com Cc: Live
Great livegreat007@yahoo.com; users@openser.org
Sent: Wednesday, October 3,
2007 10:44:06 AM
Subject: Re: [OpenSER-Users] Re: can't get code for the src-leg
attribute
Norman Brandinger wrote:
First,
The three radius messages from the radius log are just INFO messages,
not error messages. This is a good thing.
Try using the lowest
possible unused number for the attributes. My
attributes are in the 240 range.
Again, I haven't tested it but perhaps
radius has an upper limit of maybe 255 or
maybe 1024.
The upper limit is 255 because there is only one byte for RADIUS
attribute types.
http://www.iana.org/assignments/radius-types
I'd suggest to either use 124-223 or 241-255 for things like src/dst-leg.
/Christian
Norm
Hi Norman,
Thanks for the reply.
According to your suggestion, I have added the following
lines in
raddb/dicitionary:
ATTRIBUTE Src-Leg 1075 integer
ATTRIBUTE Dst-Leg 1076 integer
change in radiusclient-ng/dictionary:
ATTRIBUTE Src-Leg 1075 integer
ATTRIBUTE Dst-Leg 1076 integer
change in openser/openser.cfg:
#modparam("acc", "multi_leg_info",
"src_leg=$avp(i:901);dst_leg=$avp(i:902)")
modparam("acc",
"multi_leg_info",
"Src-Leg=$avp(i:901);Dst-Leg=$avp(i:902)")
Note, I have commented out the original src_leg/dst_leg
definition.
I don't know what is that i:901 and i:902 means, so I simply
change
the first letter to upper
case and change "_"
to "-".
Restarted radiusd, and try to start
openser then found the following
error in the
/var/log/messages
file:
ERROR:acc:extra2int: <Src-Leg> is not a number
When I started radiusd, there are info messages written to
/var/log/radiusd.log file:
Wed Oct 3 09:28:45 2007 : Info: Using deprecated
naslist file.
Support for this will go away
soon. Wed Oct 3 09:28:45 2007 : Info: rlm_exec: Wait=yes but no output
defined. Did you mean
output=none? Wed Oct 3 09:28:45 2007
: Info: Ready to process requests.
Thanks
Sam
----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live
Great livegreat007@yahoo.com
Cc: users@openser.org
Sent: Wednesday, October 3, 2007 3:26:40 AM
Subject: Re: can't get code for
the Failed attribute
Hi Sam,
If you altered the dictionary entries, you MUST make sure that your
openser.cfg, has also been updated.
For example:
modparam("acc", "radius_extra",
"Src-Leg=$avp(s:source_leg);
Dst-Leg=$avp(s:destination_leg)")
Note that Src-Leg and Dst-Leg MUST be in the dictionary for
BOTH
radiusclient-ng AND radiusd.
Regards,
Norm
Live Great wrote:
Hi,
In your example, do you
meant openser will trainsform Src-Leg to
src_leg and Dst-Leg to dst_leg?
After I followed your suggestion and changed the definition to, ATTRIBUTE Src-Leg 1075 string ATTRIBUTE Dst-Leg 1076
string
I get an error:
ERROR: acc: can't get code for the src_leg attribute
I have a feeling that it is case sensitive, and openser is looking for
src_leg instead Src-Leg.
Thanks Sam.
----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com Cc: users@openser.org Sent: Tuesday, October 2, 2007
9:42:15 PM
Subject: Re: can't get code for the Failed attribute
Hello Sam,
The definition you used:
ATTRIBUTE
src_leg 0 string
Probably isn't valid because
"0" is more than likely already being
used. Notice that the
various ATTRIBUTE numbers are all unique and just
increment. So use the
next higher number that is available. If the
last ATTRIBUTE was 240 then
your definition might look like:
ATTRIBUTE src_leg
241 string
You might also want to consider the
general naming convention that is
used. The above example would then look
as follows:
ATTRIBUTE Src-Leg 241 string Note, when you get around to inserting this data into a database, the column name will probably not be allowed to have a dash (unless the column name is quoted).
Regards,
Norm
Live Great wrote:
It looks like it doesn't look
up the dictionary files in
/usr/local/share/freeradius/ directory.
But src_leg and dst_leg are not defined in the share directory.
Sam.
----- Original Message ----
From: Live Great livegreat007@yahoo.com
To: Norman Brandinger norm@goes.com
Cc:
users@openser.org
Sent: Tuesday, October 2, 2007 10:17:47 AM Subject: Re: can't get code for the Failed attribute
Hi Norman,
Thank you for the reply.
With the definition of
"ATTRIBUTE src_leg 0 string", I got an error
"src_leg
is not a number".
After changed it to the following definition,
ATTRIBUTE Acct-Status-Type 40 integer
ATTRIBUTE Service-Type 6 integer
ATTRIBUTE Event-Timestamp 55 integer
ATTRIBUTE Acct-Session-Id 44 string
ATTRIBUTE src_leg 1 integer
ATTRIBUTE dst_leg 1 integer VALUE Acct-Status-Type Start 1 VALUE
Acct-Status-Type Stop 2
VALUE Acct-Status-Type Failed 0 VALUE Service-Type Sip-Session 15
I still got this error: ERROR:acc:extra2int:
<src_leg> is not a number
Thanks
Sam ----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com
Cc: users@openser.org
Sent: Tuesday, October 2, 2007 9:43:41 AM
Subject: Re: can't get code for the Failed attribute
Hi Sam,
In /usr/local/share/freeradius/dictionary.rfc2866 there exists the
following entry:
VALUE
Acct-Status-Type Failed 15
I'm not an
expert in this area, but it appears that "Failed" is
sort of
predefined. You probably should NOT use "Failed", instead
create a
unique attribute such as "failed-reason". This is
of course assuming
the rest of your definitions are good.
Please do not cross-post configuration
questions of this type to the
developers mailing list.
Regards, Norm
Live Great
wrote:
Hi,
After added the following Attributes in the
radiusclient-ng/dictionary
file:
ATTRIBUTE src_leg 0 string
ATTRIBUTE dst_leg 0 string ATTRIBUTE Failed 0 string
I got the following error: ERROR:
acc: can't get code for the Failed attribute value
How to define a proper attribute in the dictionary file? Thanks Sam
----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com
Cc: devel@openser.org
Sent: Monday, October 1, 2007 9:01:54 PM
Subject: Re: [OpenSER-Devel] can't get code for the
Sip-Response-Code
attribute
Good Morning,
You need to make sure the dictionary settings are correct and
exactly
match what you have specified in OpenSER.
The dictionaries are specified in
radiusclient-ng and in radiusd
(and
mediaproxy if
you use it)
The error is
telling you that "Sip-Response-Code" cannot be found
in any
of the dictionaries you have specified.
Regards, Norm
Live Great wrote:
Hi,
>
I still can't this work, that's why I posted in the development
forum.
> > I have
installed openser with *_ACC=ture uncommented in the
acc/Makfile..
> But I can't start openser now.
Here is the error when I executed /usr/local/etc/rc.d/openser start:
> > core:rc.d # ./openser
start
> Command Monit to start OpenSER...
'openser' start: /usr/local/etc/rc.d/openser
'openser' failed to start
> Starting Open SIP
Router:
> Listening on >
udp: 127.0.0.1 [127.0.0.1]:5060
> udp: 12x..x.x..x
[12x.x.x.x]:5060
> Aliases:
udp: xxx..xxx..com.au:5060
> udp:
localhost.xxx.com.au:5060
> udp: localhost:5060 > > In /var/log/messages:
> ERROR: acc: can't get code for the Sip-Response-Code
attribute
> ERROR:acc:mod_init: failed to init radius > > core:rc.d # ps -auxww |
grep openser
> root 35219 0.0 0.1 1520 728 p2 R+ 12:03AM
0:00.00 grep
openser >
core:rc.d # ps -auxww | grep radius
> root 35230 0.0 0.3 5004
3256 ?? Ss 12:04AM 0:00.00
> /usr/local/sbin/radiusd > core:rc.d # ps -auxww | grep mysql
mysql 75881 0.0 0.1 1732 1116 p1- I 20Sep07 0:00.02
/bin/sh
> /usr/local/bin/mysqld_safe
--defaults-extra-file=/usr/local/var/db/mysql/my.cnf --user=mysql
--datadir=/usr/local/var/db/mysql
>
--pid-file=/usr/local/var/db/mysql/core.xxx.com.au.pid
>
mysql 75924 0.0 2.7 49016 28336 p1- S 20Sep07 10:52.77
[mysqld]
> root 35237 0.0 0.1 1544 644 p2 RL+ 12:05AM 0:00.00 grep
mysql
>
Why I got thos acc errors when starting openser?
>
> Thanks > SW > >
> ----- Original Message ----
From: Norman Brandinger norm@goes.com
> To: Live Great livegreat007@yahoo.com
Cc: FreeRadius users mailing list
>
freeradius-users@lists.freeradius.org; users@openser.org
Sent: Friday, September 28, 2007 11:11:23 PM
> Subject:
Re: [OpenSER-Users] Failed to compile openser with
freeradius
> support >
Comment the FREERADIUS=1 in the openser/Makefile
> Make sure that in modules/acc/Makefile
ENABLE_RADIUS_ACC=true
is not
> commented > > Regards,
Norm
>
> Live Great wrote:
HI,
> >
In FreeBSD 6.2, I got this error when I compiled openser with
freeradius support.
> >
../../radius.h:36:32: freeradius-client.h: No such file or
directory
> > acc.c: In function
`init_acc_rad':
> > acc.c:464: warning: assignment makes
pointer from integer
without
a cast > > acc.c:475: error: `DICT_ATTR' undeclared (first use in
this
function)
> > acc.c:475:
error: (Each undeclared identifier is reported only
once
acc.c:475: error: for each function it appears in.)
acc.c:475: error: `da' undeclared (first use in this function) > > acc.c:475: error: `DICT_VALUE' undeclared (first use in
this
function)
> > acc.c:475:
error: `dv' undeclared (first use in this function)
> >
acc.c: In function `acc_rad_request':
> > acc.c:509:
error: `VALUE_PAIR' undeclared (first use in this
function)
> > acc.c:514: error: invalid lvalue in assignment > > acc.c:555: error: `OK_RC' undeclared (first use in this
function)
> > gmake[1]: *** [acc.o] Error 1
> > gmake[1]: Leaving directory
`/usr/ports/net/openser/work/openser-1.2.2-tls/modules/acc'
gmake: *** [modules] Error 2 >
*** Error code 2
> >
Stop in /usr/ports/net/openser.
> > ***
Error code 1
> > >
Is there any way I can compile openser with freeradius support?
> > Thanks
SW
> >
------------------------------------------------------------------------
>
------------------------------------------------------------------------
>
_______________________________________________
> Devel
mailing list
> Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
>
------------------------------------------------------------------------
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Sam,
Here is a little information about Diameter: http://ing.ctit.utwente.nl/WU5/D5.1/Technology/diameter/
Christian was absolutely correct as quoted from the above URL:
Strict limitation of attribute data Radius has only one byte reserved for the length of a datafield (max. 255) in its attribute header. Diameter reserves two bytes for its length of a datafield (max. 16535).
The web site: www.diameter.org is currently not active.
The web site: www.opendiameter.org is active and the latest release was March 2007. A quick review of the SVN repository shows the last update 2 weeks ago. This would lead me to believe that OpenDiameter is actively being developed.
Regards, Norm
After remeoved the support of
DIAMETER mmodule from openser, tt works fine now.
I have registered some numbers to it
and will test it tonight with remote xlite users.
BUT, what is DIAMETER? I read some
post in voip forum, someone said it is far too outdated.
I am wondering what it is, and
what should be used to replace DIAMETER.
Thanks for helping me along to
solve the issues.
Sam
----- Original Message ----
From: Christian Schlatter cs@unc.edu
To: norm@goes.com Cc: Live
Great livegreat007@yahoo.com; users@openser.org
Sent: Wednesday, October 3,
2007 10:44:06 AM
Subject: Re: [OpenSER-Users] Re: can't get code for the src-leg
attribute
Norman Brandinger wrote:
First,
The three radius messages from the radius log are just INFO messages,
not error messages. This is a good thing.
Try using the lowest
possible unused number for the attributes. My
attributes are in the 240 range.
Again, I haven't tested it but perhaps
radius has an upper limit of maybe 255 or
maybe 1024.
The upper limit is 255 because there is only one byte for RADIUS
attribute types.
http://www.iana.org/assignments/radius-types
I'd suggest to either use 124-223 or 241-255 for things like src/dst-leg.
/Christian
Norm
Hi Norman,
Thanks for the reply.
According to your suggestion, I have added the following
lines in
raddb/dicitionary:
ATTRIBUTE Src-Leg 1075 integer
ATTRIBUTE Dst-Leg 1076 integer
change in radiusclient-ng/dictionary:
ATTRIBUTE Src-Leg 1075 integer
ATTRIBUTE Dst-Leg 1076 integer
change in openser/openser.cfg:
#modparam("acc", "multi_leg_info",
"src_leg=$avp(i:901);dst_leg=$avp(i:902)")
modparam("acc",
"multi_leg_info",
"Src-Leg=$avp(i:901);Dst-Leg=$avp(i:902)")
Note, I have commented out the original src_leg/dst_leg
definition.
I don't know what is that i:901 and i:902 means, so I simply
change
the first letter to upper
case and change "_"
to "-".
Restarted radiusd, and try to start
openser then found the following
error in the
/var/log/messages
file:
ERROR:acc:extra2int: <Src-Leg> is not a number
When I started radiusd, there are info messages written to
/var/log/radiusd.log file:
Wed Oct 3 09:28:45 2007 : Info: Using deprecated
naslist file.
Support for this will go away
soon. Wed Oct 3 09:28:45 2007 : Info: rlm_exec: Wait=yes but no output
defined. Did you mean
output=none? Wed Oct 3 09:28:45 2007
: Info: Ready to process requests.
Thanks
Sam
----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live
Great livegreat007@yahoo.com
Cc: users@openser.org
Sent: Wednesday, October 3, 2007 3:26:40 AM
Subject: Re: can't get code for
the Failed attribute
Hi Sam,
If you altered the dictionary entries, you MUST make sure that your
openser.cfg, has also been updated.
For example:
modparam("acc", "radius_extra",
"Src-Leg=$avp(s:source_leg);
Dst-Leg=$avp(s:destination_leg)")
Note that Src-Leg and Dst-Leg MUST be in the dictionary for
BOTH
radiusclient-ng AND radiusd.
Regards,
Norm
Live Great wrote:
Hi,
In your example, do you
meant openser will trainsform Src-Leg to
src_leg and Dst-Leg to dst_leg?
After I followed your suggestion and changed the definition to, ATTRIBUTE Src-Leg 1075 string ATTRIBUTE Dst-Leg 1076
string
I get an error:
ERROR: acc: can't get code for the src_leg attribute
I have a feeling that it is case sensitive, and openser is looking for
src_leg instead Src-Leg.
Thanks Sam.
----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com Cc: users@openser.org Sent: Tuesday, October 2, 2007
9:42:15 PM
Subject: Re: can't get code for the Failed attribute
Hello Sam,
The definition you used:
ATTRIBUTE
src_leg 0 string
Probably isn't valid because
"0" is more than likely already being
used. Notice that the
various ATTRIBUTE numbers are all unique and just
increment. So use the
next higher number that is available. If the
last ATTRIBUTE was 240 then
your definition might look like:
ATTRIBUTE src_leg
241 string
You might also want to consider the
general naming convention that is
used. The above example would then look
as follows:
ATTRIBUTE Src-Leg 241 string Note, when you get around to inserting this data into a database, the column name will probably not be allowed to have a dash (unless the column name is quoted).
Regards,
Norm
Live Great wrote:
It looks like it doesn't look
up the dictionary files in
/usr/local/share/freeradius/ directory.
But src_leg and dst_leg are not defined in the share directory.
Sam.
----- Original Message ----
From: Live Great livegreat007@yahoo.com
To: Norman Brandinger norm@goes.com
Cc:
users@openser.org
Sent: Tuesday, October 2, 2007 10:17:47 AM Subject: Re: can't get code for the Failed attribute
Hi Norman,
Thank you for the reply.
With the definition of
"ATTRIBUTE src_leg 0 string", I got an error
"src_leg
is not a number".
After changed it to the following definition,
ATTRIBUTE Acct-Status-Type 40 integer
ATTRIBUTE Service-Type 6 integer
ATTRIBUTE Event-Timestamp 55 integer
ATTRIBUTE Acct-Session-Id 44 string
ATTRIBUTE src_leg 1 integer
ATTRIBUTE dst_leg 1 integer VALUE Acct-Status-Type Start 1 VALUE
Acct-Status-Type Stop 2
VALUE Acct-Status-Type Failed 0 VALUE Service-Type Sip-Session 15
I still got this error: ERROR:acc:extra2int:
<src_leg> is not a number
Thanks
Sam ----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com
Cc: users@openser.org
Sent: Tuesday, October 2, 2007 9:43:41 AM
Subject: Re: can't get code for the Failed attribute
Hi Sam,
In /usr/local/share/freeradius/dictionary.rfc2866 there exists the
following entry:
VALUE
Acct-Status-Type Failed 15
I'm not an
expert in this area, but it appears that "Failed" is
sort of
predefined. You probably should NOT use "Failed", instead
create a
unique attribute such as "failed-reason". This is
of course assuming
the rest of your definitions are good.
Please do not cross-post configuration
questions of this type to the
developers mailing list.
Regards, Norm
Live Great
wrote:
Hi,
After added the following Attributes in the
radiusclient-ng/dictionary
file:
ATTRIBUTE src_leg 0 string
ATTRIBUTE dst_leg 0 string ATTRIBUTE Failed 0 string
I got the following error: ERROR:
acc: can't get code for the Failed attribute value
How to define a proper attribute in the dictionary file? Thanks Sam
----- Original Message ----
From: Norman Brandinger norm@goes.com
To: Live Great livegreat007@yahoo.com
Cc: devel@openser.org
Sent: Monday, October 1, 2007 9:01:54 PM
Subject: Re: [OpenSER-Devel] can't get code for the
Sip-Response-Code
attribute
Good Morning,
You need to make sure the dictionary settings are correct and
exactly
match what you have specified in OpenSER.
The dictionaries are specified in
radiusclient-ng and in radiusd
(and
mediaproxy if
you use it)
The error is
telling you that "Sip-Response-Code" cannot be found
in any
of the dictionaries you have specified.
Regards, Norm
Live Great wrote:
Hi,
>
I still can't this work, that's why I posted in the development
forum.
> > I have
installed openser with *_ACC=ture uncommented in the
acc/Makfile..
> But I can't start openser now.
Here is the error when I executed /usr/local/etc/rc.d/openser start:
> > core:rc.d # ./openser
start
> Command Monit to start OpenSER...
'openser' start: /usr/local/etc/rc.d/openser
'openser' failed to start
> Starting Open SIP
Router:
> Listening on >
udp: 127.0.0.1 [127.0.0.1]:5060
> udp: 12x..x.x..x
[12x.x.x.x]:5060
> Aliases:
udp: xxx..xxx..com.au:5060
> udp:
localhost.xxx.com.au:5060
> udp: localhost:5060 > > In /var/log/messages:
> ERROR: acc: can't get code for the Sip-Response-Code
attribute
> ERROR:acc:mod_init: failed to init radius > > core:rc.d # ps -auxww |
grep openser
> root 35219 0.0 0.1 1520 728 p2 R+ 12:03AM
0:00.00 grep
openser >
core:rc.d # ps -auxww | grep radius
> root 35230 0.0 0.3 5004
3256 ?? Ss 12:04AM 0:00.00
> /usr/local/sbin/radiusd > core:rc.d # ps -auxww | grep mysql
mysql 75881 0.0 0.1 1732 1116 p1- I 20Sep07 0:00.02
/bin/sh
> /usr/local/bin/mysqld_safe
--defaults-extra-file=/usr/local/var/db/mysql/my.cnf --user=mysql
--datadir=/usr/local/var/db/mysql
>
--pid-file=/usr/local/var/db/mysql/core.xxx.com.au.pid
>
mysql 75924 0.0 2.7 49016 28336 p1- S 20Sep07 10:52.77
[mysqld]
> root 35237 0.0 0.1 1544 644 p2 RL+ 12:05AM 0:00.00 grep
mysql
>
Why I got thos acc errors when starting openser?
>
> Thanks > SW > >
> ----- Original Message ----
From: Norman Brandinger norm@goes.com
> To: Live Great livegreat007@yahoo.com
Cc: FreeRadius users mailing list
>
freeradius-users@lists.freeradius.org; users@openser.org
Sent: Friday, September 28, 2007 11:11:23 PM
> Subject:
Re: [OpenSER-Users] Failed to compile openser with
freeradius
> support >
Comment the FREERADIUS=1 in the openser/Makefile
> Make sure that in modules/acc/Makefile
ENABLE_RADIUS_ACC=true
is not
> commented > > Regards,
Norm
>
> Live Great wrote:
HI,
> >
In FreeBSD 6.2, I got this error when I compiled openser with
freeradius support.
> >
../../radius.h:36:32: freeradius-client.h: No such file or
directory
> > acc.c: In function
`init_acc_rad':
> > acc.c:464: warning: assignment makes
pointer from integer
without
a cast > > acc.c:475: error: `DICT_ATTR' undeclared (first use in
this
function)
> > acc.c:475:
error: (Each undeclared identifier is reported only
once
acc.c:475: error: for each function it appears in.)
acc.c:475: error: `da' undeclared (first use in this function) > > acc.c:475: error: `DICT_VALUE' undeclared (first use in
this
function)
> > acc.c:475:
error: `dv' undeclared (first use in this function)
> >
acc.c: In function `acc_rad_request':
> > acc.c:509:
error: `VALUE_PAIR' undeclared (first use in this
function)
> > acc.c:514: error: invalid lvalue in assignment > > acc.c:555: error: `OK_RC' undeclared (first use in this
function)
> > gmake[1]: *** [acc.o] Error 1
> > gmake[1]: Leaving directory
`/usr/ports/net/openser/work/openser-1.2.2-tls/modules/acc'
gmake: *** [modules] Error 2 >
*** Error code 2
> >
Stop in /usr/ports/net/openser.
> > ***
Error code 1
> > >
Is there any way I can compile openser with freeradius support?
> > Thanks
SW
> >
------------------------------------------------------------------------
>
------------------------------------------------------------------------
>
_______________________________________________
> Devel
mailing list
> Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
>
------------------------------------------------------------------------
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Live Great -
Norman Brandinger