Re: [RADIATOR] Custom AuthApplicationIds

2014-06-07 Thread Arthur
To be more specific, I need a corresponding CEA for the following CER: *** Received initial Diameter request Code: 257 (CER) Version:1 Flags: 0x80 (R) Application ID: 0 (Base) Hop-to-Hop ID: 1970129370 End-to-End ID: 1970129370 Attributes:

Re: [RADIATOR] Custom AuthApplicationIds

2014-06-07 Thread Heikki Vatiainen
On 06/07/2014 12:25 PM, Arthur wrote: > DiameterDictionaryFile %D/diameter_attrs.dat > > OriginHost xx.xxx.x.xx > OriginRealm xxx.x.xx > Port 3868 > SupportedVendorIds DictVendors > AuthApplicationIds ETSI_E4 > Hello Arthur, you need to use

Re: [RADIATOR] Custom AuthApplicationIds

2014-06-07 Thread Arthur
Hi Heikki, Thanks for the detailed explanation. I've changed AuthApplicationIds to the ETSI-E4, made simple DiaDict_16777231.pm: # DiaDict_16777231.pm # Dictionary for the Diameter ETSI-E4 application # $Id: DiaDict_16777231.pm,v 1.0 2014/01/27 21:57:44 hvn Exp $ package Radius::DiaDict_1677723

Re: [RADIATOR] EAP-TTLS missing reply attributes from inner-accept

2014-06-07 Thread Heikki Vatiainen
On 06/07/2014 12:14 AM, Christopher Chance wrote: > For some reason the final reply to the device is not getting the full > attributes, we send 2 custom attributes for speed > > Cambium-Canopy-DLMB=10480, > Cambium-Canopy-ULMB=2048 Hello Chris, if you can pass me these, and any

Re: [RADIATOR] Custom AuthApplicationIds

2014-06-07 Thread Heikki Vatiainen
On 06/07/2014 09:24 PM, Arthur wrote: > Thanks for the detailed explanation. > I've changed AuthApplicationIds to the ETSI-E4, made simple > DiaDict_16777231.pm: Good to hear it works. What will happen is that when a message for this applications is received, Radiator will use DiaDict.pm + DiaDi