(RADIATOR) Re: Grouped Diameter AVP to Radius conversion

[Mike McCauley]

Hello Arthur,


I guess thats an interesting question: how should grouped Diameter attributes 
be handled when converted to Radius? The Diameter spec is silent on how to 
handle such vendor specific grouped AVPs

What is your view?

Cheers.

On Friday 12 January 2007 20:28, Arthur Konovalov wrote:
> Hi!
>
> First stage of job is almost finished. One problem remains with grouped
> AVP to Radius conversion.
>
> For example, Diameter grouped message Time-Stamps:
>    Time-Stamps: 192,
>           SIP-Request-Timestamp: 192, 20070112T094730943,
>           SIP-Response-Timestamp: 192, 20070112T094730964,,
>
>
> is converted to Radius as:
> Time-Stamps = "Radius::DiaAttrList=HASH(0x875b4b8)"
>
>
> Logfile and dictionary files attached.
>
>
> Regards,
> Arthur

-- 
Mike McCauley                               mikem at open.com.au
Open System Consultants Pty. Ltd            Unix, Perl, Motif, C++, WWW
9 Bulbul Place Currumbin Waters QLD 4223 Australia   http://www.open.com.au
Phone +61 7 5598-7474                       Fax   +61 7 5598-7070

Radiator: the most portable, flexible and configurable RADIUS server 
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, 
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, 
TTLS, PEAP etc on Unix, Windows, MacOS, NetWare etc.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.