Is the fix_avaya issue already added?

[JeGoi]

Describe the bug
From https://sourceforge.net/p/packetfence/mailman/packetfence-users/thread/1720136717.11234296.1556099781504.JavaMail.zimbra%40novasys.coop/#msg36648083

On raddb/policy.d/packetfence

fix_avaya {

     if (!&Calling-Station-Id) {
         if (&User-Name && (&User-Name =~ /^${policy.mac-addr-regexp}$/i)) {
             update {
                 &request:Calling-Station-Id := 
"%{tolower:%{1}%{2}%{3}%{4}%{5}%{6}}"
             }
         }
     }
}

and in conf/radiusd/packetfence (Here
https://github.com/inverse-inc/packetfence/blob/devel/conf/radiusd/packetfence.example#L15),
add fix_avaya

Like that:

#  need to setup hints for the remote radius server
authorize {
     fix_avaya
     # Add in PacketFence specific configuration
     update {

The solution is working and used by at least one client.

Could it be added to our code?

Thanks

[fdurand]

Will have to create a Admin UI configuration parameter.