Configuration keys are inconsistent for min/max attenuation

[ttsou]

In the apps section of the code and in the example configuration file, UMTS.Radio.PowerManager is used for min/max attenuation values. The CLI uses GSM.Radio.PowerManager. This disparity may lead to crashing behavior when running OpenBTS-UMTS.

apps/OpenBTS-UMTS.example.sql

INSERT OR IGNORE INTO "CONFIG" VALUES('UMTS.Radio.PowerManager.MaxAttenDB','10',0,0,'Maximum transmitter attenuation level, in dB wrt full scale on the D/A output.  This sets the minimum power output level in the output power control loop.');
INSERT OR IGNORE INTO "CONFIG" VALUES('UMTS.Radio.PowerManager.MinAttenDB','0',0,0,'Minimum transmitter attenuation level, in dB wrt full scale on the D/A output.  This sets the maximum power output level in the output power control loop.');

apps/GetConfigurationKeys.cpp

        tmp = new ConfigurationKey("UMTS.Radio.PowerManager.MaxAttenDB","10",
                "dB",
                ConfigurationKey::CUSTOMERTUNE,
                ConfigurationKey::VALRANGE,
                "0:80",// educated guess
                false,
                "Maximum transmitter attenuation level, in dB wrt full scale on the D/A output.  "
                        "This sets the minimum power output level in the output power control loop."
        );
        map[tmp->getName()] = *tmp;
        delete tmp;

        tmp = new ConfigurationKey("UMTS.Radio.PowerManager.MinAttenDB","0",

CLI/CLI.cpp

    gConfig.set("GSM.Radio.PowerManager.MinAttenDB",argv[1]);
    gConfig.set("GSM.Radio.PowerManager.MaxAttenDB",argv[2]);