Heikki wrote in January:
> Later it might be possible to upgrade the code to an application that
> handles just Diameter requests and does not need to go through
> conversion, but it's not possible yet.
Is there any information on when it might happen
Node-Functionality: VM., 6
How to add "Subscription-Id-Data" (and possible "Subscription-Id-Type"
too) to the Radius conversion? Currently it just dropped and I loose
this information for the further analysis.
br,
Arthur
___
r
er-Name: $subscription");
}
But in the log file I have an empty 'User-Name'. Where I have did mistake?
br,
Arthur
27.03.2014 21:04, Heikki Vatiainen kirjutas:
> On 03/27/2014 04:57 PM, Arthur wrote:
>> In my incoming Diameter Accounting message I have the following part:
> On 03/28/2014 11:50 AM, Arthur wrote:
>
>> dia_to_radius_hook.pl:
>> sub
>> {
>> my $d=${$_[0]};
>> my $p=${$_[1]};
>>
>> my $subscription = $p->get_attr('Subscription-Id-Data');
>> $subscription =~ s/^sip:/
30.03.2014 22:27, Heikki Vatiainen kirjutas:
> On 03/30/2014 11:47 AM, Arthur wrote:
>
>> It seems that some tuning needed. I've the following hook code:
>> sub
>> {
>> my $d=${$_[0]};
>> my $r=${$_[1]};
>> my $si = $d->get(873, 10
31.03.2014 16:16, Heikki Vatiainen kirjutas:
> On 03/31/2014 10:30 AM, Arthur wrote:
>
>>SDP-Session-Description: VM., v=0
>>SDP-Session-Description: VM., o=- 640284584 403958478 IN IP4
>> 94.50.86.245
>>SDP-Session-Description: VM., s=-
>
1.04.2014 17:33, Heikki Vatiainen kirjutas:
> On 04/01/2014 02:12 PM, Arthur wrote:
>
>> One mystery (or bug?) needs explaining, though.
>> I have the following Diameter request part:
> Can't really say why you need to use get_attrs. What does your
> dictionary
help.
Radiator-4.12.1 has the same problem, while Radiator-4.11 works
correctly with the same configuration.
How to solve this issue?
br,
Arthur
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
Id ETSI_E4 16777231
# Supported-Vendor-Id in CEA:
VENDOR 3GPP 10415
VENDOR ETSI 13019
Is there Radiator somewhat broken after 4.11?
Regards,
Arthur
6.06.2014 16:58, Arthur kirjutas:
> Hi,
>
> I just tried to customize CEA/CER for ETSI_E4 with Radiator-4.13 and
> I've added line to
Credit Control
application
__DATA__
VALUEAuth-Application-IdETSI_E416777231
and it works.
Thank you again.
Regards,
Arthur
7.06.2014 20:44, Heikki Vatiainen kirjutas:
> On 06/07/2014 12:25 PM, Arthur wrote:
>
>> DiameterDictionaryFile %D/diameter_attrs.dat
23.12.2014 23:29, Heikki Vatiainen kirjutas:
> On 12/19/2014 02:18 PM, Arthur Konovalov wrote:
>
>>if (my @medintflowstat = $medintstat->get_attr(1086, 193)) {
>> My problem is that hook doesn't parse second "Media-Flow-Statistics"
>> AVP gro
lp in this situation with pure Diameter
environment?
br,
Arthur
28.03.2015 4:59, Hugh Irvine kirjutas:
> Hello Arthur -
>
> The best way to see what is happening is to run Radiator at trace 4 with
> LogMicroseconds enabled.
>
> This will show you exactly how long each proce
30.03.2015 13:05, Heikki Vatiainen kirjutas:
> On 28.3.2015 10.44, Arthur wrote:
>> OK, it's mean that my mentioned 5.2 seconds delay example caused by
>> previously slowly processed requests and OS rx buffer filling?
>> I have trace 4 with LogMicroseconds logfile and I
/raddb
LogFile %L/logfile-%Y%m
LogMicroseconds
Trace 3
FarmSize 4
AuthPort
AcctPort 1813
br,
Arthur
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
e smooth CPUs and radiusd load?
br,
Arthur
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
Thank You for explanation.
Does proxy will work with DIAMETER protocol too?
br,
Arthur
> The frontend simply proxies the requests with an "AuthBy *BALANCE" to the
> backends where the processing occurs.
>
> You would set up multiple backends on different port numbers su
Thread name changed, because I'm interesting does Diameter works with
Radiator proxy environment.
Say, one instance runs as proxy with 'AuthBy *BALANCE' and others in the
different ports as child instances.
Without Farming.
br,
Arthur
Heikki Vatiainen wrote:
> On 08/06/201
I have a set of Radiator with frontend and backends on the same server.
Sometimes I see warnings in the logfile like that:
Mon Aug 23 21:51:20 2010: WARNING: Unknown reply received in AuthRADIUS
for request 138 from 127.0.0.1:1650
What reasons it can be for this? Overload? Is it possible to avoi
xxx"
If I tried to add only Line-Information AVP, then it replied, but
without grouped AVP and peer doesn't accept it.
br,
Arthur
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
cation-Information 350 string
VENDORATTR 13019 Line-Identifier 500 string
Is it OK, or some number conversion are still missed in the code?
In the diameter_attr.dat file I have:
VENDORATTR 13019 Location-Information 350 Grouped
VENDORATTR 13019 Line-Identifier 500 OctetString
br,
="Ascend=CLID"
Useraccount
Authentication-Type=Unix-PW
However I do not know how to do this on radiator.
Thanks for any comment!
Arthur
ypass this level of authen,
then go to next level authen:
-a1234567
Authentication-Type=Unix-PWAs a result, is it possible to perform the
same authentication process atthe
Radiator?Regards,Arthur
e both ip addresses
variants to SQL?
Does upgrading Radiator might help there?
br,
Arthur
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
something else?
I can provide Wireshark capture file as well if needed (both - live and
emulated, they looks similar).
br,
Arthur
___
radiator mailing list
radiator@open.com.au
http://www.open.com.au/mailman/listinfo/radiator
24 matches
Mail list logo
