Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AcmThresholdCrossAlarmType :: amountOfSeconds cannot contain the number of seconds of a day #47

Closed
niloda opened this issue Apr 28, 2021 · 3 comments
Assignees

Comments

@niloda
Copy link

niloda commented Apr 28, 2021

This attribute is defined as int16 in the current model, this means that it can contain a number between -32768 and +32767, not allowing to set a value equal to the maximum number of seconds of a day (86400) for instances related to 24 Hours .

Proposal: change the type from int16 to int32

@openBackhaul
Copy link
Owner

openBackhaul commented Apr 29, 2021

Decision on the 5G-xhaul-call on 12th of May 2021:
Datatype of AcmThresholdCrossAlarmType :: amountOfSeconds = -1 shall be increased from Integer16 to Integer32.

@PrathibaJee
Copy link
Collaborator

As per the issue#38 , the attribute AcmThresholdCrossAlarmType::amountOfSeconds is renamed to AcmThresholdCrossAlarmType::secondsForRaisingAlarm.
So , Datatype of AcmThresholdCrossAlarmType::secondsForRaisingAlarm = -1 shall be increased from Integer16 to Integer32.

@openBackhaul
Copy link
Owner

Fixed with AirInterface_2.0.0-tsp.220328.1245.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants