16 Jun
2004
16 Jun
'04
12:45 p.m.
Does anyone know how to account for non successful calls to Radius? I
would like 0 second calls accounted for as well.
Thanks,
Adrian
1:17 p.m.
I did.
It saves missed calls in mysql but it generates no RADIUS requests at
all.
Adrian
On Jun 16, 2004, at 6:58 PM, Juha Heinanen wrote:
AG Projects support writes:
Does anyone know how to account for non
successful calls to Radius? I
would like 0 second calls accounted for as well.
there is failed_transaction flag. have you tried to turn it on?
-- juha 
1:18 p.m.
I did.
It saves missed calls in mysql but it generates no RADIUS requests at
all.
Adrian
On Jun 16, 2004, at 6:58 PM, Juha Heinanen wrote:
AG Projects support writes:
Does anyone know how to account for non
successful calls to Radius? I
would like 0 second calls accounted for as well.
there is failed_transaction flag. have you tried to turn it on?
-- juha 
1:22 p.m.
for radius/db/diameter are separate parameters:
(radius|db|diameter)_missed_flag
bogdan
Adrian Georgescu wrote:
I did.
It saves missed calls in mysql but it generates no RADIUS requests at
all.
Adrian
On Jun 16, 2004, at 6:58 PM, Juha Heinanen wrote:
AG Projects support writes:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Does anyone know how to account for non
successful calls to Radius? I
would like 0 second calls accounted for as well.
there is failed_transaction flag. have you tried to turn it on?
-- juha
1:38 p.m.
I have this turned on alright. Only SIP status between 200 and 300 are
dealt with in the acc module for sending a RADIUS START message.
Outside the [200 - 300] range, a RADIUS 15 is sent by function
rad_status
Wed Jun 16 19:08:43 2004 : Error: rlm_radutmp: NAS 81.23.228.139 port
5060 unknown packet type 15)
Wed Jun 16 19:08:44 2004 : Info: rlm_sql (sql): Unsupported
Acct-Status-Type = 15
Wed Jun 16 19:08:44 2004 : Error: rlm_radutmp: NAS 81.23.228.139 port
5060 unknown packet type 15)
Wed Jun 16 19:08:44 2004 : Info: rlm_sql (sql): Unsupported
Acct-Status-Type = 15
Wed Jun 16 19:08:44 2004 : Error: rlm_radutmp: NAS 81.23.228.139 port
5060 unknown packet type 15)
15 is a not a recognized RADIUS Packet
according to radius definitions from radiusclient.h valid types are:
/* ACCOUNTING STATUS TYPES */
#define PW_STATUS_START 1
#define PW_STATUS_STOP 2
#define PW_STATUS_ALIVE 3
#define PW_STATUS_MODEM_START 4
#define PW_STATUS_MODEM_STOP 5
#define PW_STATUS_CANCEL 6
#define PW_ACCOUNTING_ON 7
#define PW_ACCOUNTING_OFF 8
Adrian
On Jun 16, 2004, at 7:22 PM, Bogdan-Andrei IANCU wrote:
for radius/db/diameter are separate parameters:
(radius|db|diameter)_missed_flag
bogdan
Adrian Georgescu wrote:
I did.
It saves missed calls in mysql but it generates no RADIUS requests at
all.
Adrian
On Jun 16, 2004, at 6:58 PM, Juha Heinanen wrote:
AG Projects support writes:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
Does anyone know how to account for non
successful calls to Radius?
I
would like 0 second calls accounted for as well.
there is failed_transaction flag. have you tried to turn it on?
-- juha
2:09 p.m.
New subject: [Serusers] 15 is a not a recognized RADIUS Packet
Do you know by any chance what does it mean?
Radius client and freeradius server do not know it.
Adrian
On Jun 16, 2004, at 8:04 PM, Juha Heinanen wrote:
Adrian Georgescu writes:
15 is a not a recognized RADIUS Packet
not by freeradius mysql module, but it is defined in radius specs.
-- juha
2:26 p.m.
New subject: [Serusers] 15 is a not a recognized RADIUS Packet
Adrian Georgescu writes:
Do you know by any chance what does it mean?
here are all official radius acct-status-types:
Values for RADIUS Attribute 40, Acct-Status-Type [RFC 2866]:
1 Start [RFC 2866]
2 Stop [RFC 2866]
3 Interim-Update [RFC 2866]
4-6 (unassigned)
7 Accounting-On [RFC 2866]
8 Accounting-Off [RFC 2866]
9 Tunnel-Start [RFC 2867]
10 Tunnel-Stop [RFC 2867]
11 Tunnel-Reject [RFC 2867]
12 Tunnel-Link-Start [RFC 2867]
13 Tunnel-Link-Stop [RFC 2867]
14 Tunnel-Link-Reject [RFC 2867]
15 Failed [RFC 2866]
you can find definition of 15 from the above mentioned rfc, but if a
fails before starting, then 15 is the right way to report it.
-- juha
1:39 p.m.
Adrian Georgescu writes:
It saves missed calls in mysql but it generates no
RADIUS requests at
all.
in the first message you talked about "non successful" calls and here
about "missed calls". are you interested accounting of failed calls by
the caller or calls that the callee has missed?
regarding failed calls, i checked from the source and did't find
anything apparently wrong with it.
-- juha
1:49 p.m.
Telcos consider ASR an important factor which measure the health of
interconnect with different peers. All cals should end up in Radius
regardless of their succes or missing/failures so the ratio between
good calls/bad calls can be measured and dealt with.
I would like both missed and failed calls logged in RAdius with their
corresponding release code (sip status).
Adrian
On Jun 16, 2004, at 7:39 PM, Juha Heinanen wrote:
Adrian Georgescu writes:
It saves missed calls in mysql but it generates
no RADIUS requests at
all.
in the first message you talked about "non successful" calls and here
about "missed calls". are you interested accounting of failed calls by
the caller or calls that the callee has missed?
regarding failed calls, i checked from the source and did't find
anything apparently wrong with it.
-- juha
7322
days inactive
7322
days old
10 comments
4 participants
participants (4)
-
Adrian Georgescu -
AG Projects support -
Bogdan-Andrei IANCU -
Juha Heinanen