change_of_authority_coa
Differences
This shows you the differences between two versions of the page.
|
change_of_authority_coa [2016/03/27 19:31] admin created |
change_of_authority_coa [2016/03/27 19:35] admin |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Evolynx RADIUS is capable of sending Change of Authorization (CoA) packets to NAS. For this to work, NAS should be configured to send accounting intervals, or Evolynx RADIUS should be configured to run maintenance job (or both). Evolynx RADIUS setting for CoA should be enabled as well. See [[configuration_settings|Configuration Settings]]. | + | Evolynx RADIUS is capable of sending Change of Authorization (CoA) packets to NAS. For this to work, NAS should be configured to send accounting intervals, or Evolynx RADIUS should be configured to run maintenance job (or both). Evolynx RADIUS setting for CoA should be enabled as well. See [[configuration_settings#radius|Configuration Settings]]. |
| When any of these events are triggered and there is any [[custom_attributes|Custom Attribute]] defined for the service or the customer, those custom attributes are included in the CoA request. If any custom attribute is conditional, the condition will be evaluated and if met, attribute will be included in the CoA packet. For CoA to work, NAS must be accepting packets and the port it uses to listen to CoA must be specified in Evolynx Client definition (see [[clients|Configuring Clients]]). | When any of these events are triggered and there is any [[custom_attributes|Custom Attribute]] defined for the service or the customer, those custom attributes are included in the CoA request. If any custom attribute is conditional, the condition will be evaluated and if met, attribute will be included in the CoA packet. For CoA to work, NAS must be accepting packets and the port it uses to listen to CoA must be specified in Evolynx Client definition (see [[clients|Configuring Clients]]). | ||
change_of_authority_coa.txt ยท Last modified: 2023/08/14 06:41 (external edit)
