Hi musoket,
rad_recv: Accounting-Request packet from host n.a.s.1:1646, id=239,
length=531
Acct-Session-Id = 0024F8FF
Calling-Station-Id = 442098765432
Called-Station-Id = 0002561234567
h323-setup-time = h323-setup-time=16:53:14.471 GMT+3 Mon Aug 6 2007
For Cisco, please be sure that you have in your config
radius-server vsa send accounting
gw-accounting aaa
(or gw-accounting h323 aaa for an older IOS)
Best regards,
Claudiu Filip
@: [EMAIL PROTECTED]
Http://www.globtel.ro
T:+40344880100
F:+40344880113
Monday, August 6, 2007, 6:58:06 PM,
Hi Claudiu,
Thanks for your response,
Wed, 8 Aug 2007 12:24:57 +0300, you wrote:
For Cisco, please be sure that you have in your config
radius-server vsa send accounting
gw-accounting aaa
(or gw-accounting h323 aaa for an older IOS)
Best regards,
Claudiu Filip
@: [EMAIL PROTECTED]
Hello Ivan,
Mon, 06 Aug 2007 16:45:09 +0100, you wrote:
rlm_acct_unique: WARNING: Attribute NAS-Port was not found in request,
unique ID MAY be inconsistent
This is the source of the errors in log entries.
These are accounting start (VoIP and telephony) and stop requests. They
will use
Yes, but there was no h323-remote-address attribute in the accounting
requests. So, nothing was logged.
Ivan Kalik
Kalik Informatika ISP
Dana 7/8/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] piše:
Hello Ivan,
Mon, 06 Aug 2007 16:45:09 +0100, you wrote:
rlm_acct_unique: WARNING: Attribute
Hello Ivan,
Thu, 02 Aug 2007 12:21:02 +0100, you wrote:
Send us the log (radiusd -X) with your accounting request. Lets see if
this query gets executed.
Ivan Kalik
Kalik Informatika ISP
The output of radiusd -X is thus:
mail:~ # radiusd -X
Starting - reading configuration files ...
You need to stop the server (killall radiusd) and restart in debug mode
(radiusd -X).
Ivan Kalik
Kalik Informatika ISP
Dana 6/8/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] piše:
Hello Ivan,
Thu, 02 Aug 2007 12:21:02 +0100, you wrote:
Send us the log (radiusd -X) with your accounting request.
Hi Ivan,
Mon, 06 Aug 2007 09:07:22 +0100, you wrote:
You need to stop the server (killall radiusd) and restart in debug mode
(radiusd -X).
Ivan Kalik
Kalik Informatika ISP
I don't know if this is related to this problem but I get a lot of this in my
radius log files:
Mon Aug 6 13:19:34 2007
Hello Ivan,
Mon, 06 Aug 2007 09:07:22 +0100, you wrote:
You need to stop the server (killall radiusd) and restart in debug mode
(radiusd -X).
Ivan Kalik
Kalik Informatika ISP
This is some of the debug output indicating an INSERT statement:
modcall: entering group preacct for request 37
Chack if your NAS is keeping fields used to create acct_unique constant.
It seems that one or more of them are changing for the same session.
Ivan Kalik
Kalik Informatika ISP
Dana 6/8/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] piše:
Hi Ivan,
Mon, 06 Aug 2007 09:07:22 +0100, you wrote:
You
1. Send debug with the Accounting-Request
2. Create an extra field for that attribute (IP address is varchar(15)
type) to the radaact table and add the field and value to the query (so
it's definitely different.
Ivan Kalik
Kalik Informatika ISP
Dana 6/8/2007, [EMAIL PROTECTED] [EMAIL PROTECTED]
Hello Ivan,
Mon, 06 Aug 2007 12:52:20 +0100, you wrote:
From: [EMAIL PROTECTED]
1. Send debug with the Accounting-Request
2. Create an extra field for that attribute (IP address is varchar(15)
type) to the radaact table and add the field and value to the query (so
it's definitely different.
rlm_acct_unique: WARNING: Attribute NAS-Port was not found in request, unique
ID MAY be inconsistent
This is the source of the errors in log entries.
These are accounting start (VoIP and telephony) and stop requests. They
will use accounting_start_query and accounting_stop_query. In your
PS. BTW there is no h323-remote-address attribute in those requests.
Ivan Kalik
Kalik Informatika ISP
Dana 6/8/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] piše:
Hello Ivan,
Mon, 06 Aug 2007 12:52:20 +0100, you wrote:
From: [EMAIL PROTECTED]
1. Send debug with the Accounting-Request
2. Create
Hi Claudiu,
Thanks for your response.
Thu, 2 Aug 2007 03:10:24 +0300, you wrote:
How does your INSERT look like?
AFAIK, in logs you get something like
h323-remote-address = h323-remote-address=re.mo.te.ip
You should use the %{h323-remote-address} variable
That is in fact the variable
Send us the log (radiusd -X) with your accounting request. Lets see if
this query gets executed.
Ivan Kalik
Kalik Informatika ISP
Dana 2/8/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] piše:
Hi Claudiu,
Thanks for your response.
Thu, 2 Aug 2007 03:10:24 +0300, you wrote:
How does your INSERT
Hi musoket,
You should use the %{h323-remote-address} variable
That is in fact the variable that I am using in my insert and update
Dont forget that you have (at least) 2 call legs for each call.
With as5350, I guess you will have one voip call leg and one PSTN call
leg. The PSTN call leg wont
Hello,
Let me start off by saying I am new to this list and not very accomplished in
freeradius administration.
I am running a freeradius-1.1.0-19.6 setup to gather VoIP accounting
information from a Cisco AS5350 router and insert this information into a
mysql-5.0.18-16 database. The OS is SuSE
On Wed 01 Aug 2007, [EMAIL PROTECTED] wrote:
Hello,
Let me start off by saying I am new to this list and not very accomplished
in freeradius administration.
I am running a freeradius-1.1.0-19.6 setup to gather VoIP accounting
information from a Cisco AS5350 router and insert this
Hi musoket,
Wednesday, August 1, 2007, 3:17:15 PM, you wrote:
I am having trouble populating the MySQL database with a certain
attribute h323-remote-address. A tail of the radius logs shows me
that this attribute is being received by radius. It however does not
How does your INSERT look
20 matches
Mail list logo
