We will need to get the event_id first, to know how to process the content as Operation status content is different from rest.

So this line is just for getting the event id, and based on the result, process the rest into the correct variables

removed

fixed

remove if we are sure about the message ID

Will we need this after adding the below code?

Fix typo

are we missing any value in (). If not remove the (
Same in line 298

Please reserve the IDs in the shared excel and use the available IDs

I think that's what is usually shown, the first 7 char, but in this case it might have been a typo

Was it a regulatory requirement before to have 7 characters from commit ID or something we implemented?

No need, in a different CR I have a module that pulls the Alarm ID, Reject Reason and Msg Ids directly from the FW. After that's merged, this file won't be needed any more manual update.

For more information check LDT-5205 CR, file: utils\ enum_updater.py

In FW we pre-populated Alarm IDs up to 300 to help with the reservation process. Would this also benefit dialin if we reserve up to 300?

Wrong MsgID
Update the entity name too

Wrong MsgID
Update the entity name too

Update header

Update header

.name

Use the name as key, to match the above suggested changes

.name
Use the name instead of the full enum for key

import from msg_ids, because the enum located there not in msg_defs

Update

Align the values please

Conflicting with existing ones