Re: Query regarding update reason
Vijay Badola wrote: > I have a query regarding Update-Reason field in PPAQ attribute of > Access-Request for prepaid case. > > According to WiMax specification the size of this AVP is 4 > byte(including tag and length). *Which* WiMAX specification? The geniuses involved in WiMAX *changed* the definition of multiple attributes when they updated the specifications. > And according to dictionary.wimax supplied by freeradius size of > Update-Reason field is 4 byte means total size of AVP is 6 byte. We're compatible with the specification we quote at the top of dictionary.wimax. > Can we change the size of Update-Reason field to 2 byte in > dictionary.wimax to make over all AVP size 4 byte, to decode this AVP at > server properly (when incoming Access-Request has 4 byte for > update-reason AVP)? Or What is other way to achieve it? The dictionaries are text for a reason: you can edit them. > Please correct me if my understading is wrong? WiMAX is completely wrong. The specs are ridiculously complicated. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Query regarding update reason
Hi, I have a query regarding Update-Reason field in PPAQ attribute of Access-Request for prepaid case. According to WiMax specification the size of this AVP is 4 byte(including tag and length). And according to dictionary.wimax supplied by freeradius size of Update-Reason field is 4 byte means total size of AVP is 6 byte. Can we change the size of Update-Reason field to 2 byte in dictionary.wimax to make over all AVP size 4 byte, to decode this AVP at server properly (when incoming Access-Request has 4 byte for update-reason AVP)? Or What is other way to achieve it? Please correct me if my understading is wrong? , * P We have responsibility to the environment. Before printing this e-mail or any other document, let's ask ourselves whether we need a hard copy. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
