(RADIATOR) Re: Grouped Diameter AVP to Radius conversion

[Arthur Konovalov]

Mike McCauley wrote:
> 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)"
>>
>>
>>     
I think that it be good enough (at least for me) if they just be added 
to Radius attributes.
For example:
 From grouped "Time-Stamps"  "SIP-Request-Timestamp" and 
"SIP-Response-Timestamp" might be added and "Time-Stamps" just ignored.

Is it very wrong approach?


AK

--
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.