It not suite an “P” code for this setting, as it works with the handset, not the base station. For example, If we define 5 “p” codes for the 5 handsets, and you set the value in the configure file like below:
“p” code 1 (Handset 1): Enabled
“p” code 2 (Handset 2): Disabled
“p” code 3 (Handset 3): Disabled
“p” code 4 (Handset 4): Enabled
“p” code 5 (Handset 5): Disabled
When you register the handset to the base station, the registration order will make the setting unpredictable. Because you don’t know which handset will be used by who and registered as Handset which.
For example, if Bob use handset 1 he will has the feature enabled, but what if his handset registered the base in second place and actually is handset 2?
Of course, it does not matter if you just configure all the handsets with the same settings, but since you have this ability to change, what if some users ask you to configure his handset to a different option? and you will get yourself in trouble to maintain this setting in the config file. If you cannot make the settings in variant, then there is no meaning to use a configure file to set it, just pre-set them in an same setting, or teach the users how to configure it may be more simply. This is also the principle when comes to an handset-based feature, we don’t use a “p” code by purpose, but just let the users to configure it themselves, because our partners won’t able to know the handset is used by which end user.