fix: alarm sms forward data coding issue

config/etc/default/restconf.yaml

@@ -135,7 +135,8 @@ omc:
 # TLS Skip verify: true/false
 # email/sms
 # smProxy: sms(Short Message Service)/smsc(SMS Centre)  
-# dataCoding: 0:UCS2, 1:ASCII, 2:LATIN1
+# dataCoding: 0:GSM7BIT, 1:ASCII, 2:BINARY8BIT1, 3:LATIN1, 
+#             4:BINARY8BIT2, 6:CYRILLIC, 7:HEBREW, 8:UCS2
 alarm: 
   alarmEmailForward:
     enable: true

config/param/omc_param_config.yaml

@@ -69,7 +69,7 @@ omc:
         access: "rw"
         filter: ""
         display: "Mobile List"
-        comment: ""
+        comment: "Multiple mobile separated by commas"
       - name: "smscAddr"
         type: "string"
         value: ""
@@ -100,9 +100,9 @@ omc:
         comment: ""
       - name: "dataCoding"
         type: "enum"
-        value: "ASCII"
+        value: "GSM7BIT"
         access: "rw"
-        filter: '{"0":"UCS2","1":"ASCII","2":"LATIN1"}'
+        filter: '{"0":"GSM7BIT","1":"ASCII","2":"BINARY8BIT1","3":"LATIN1","4":"BINARY8BIT2","6":"CYRILLIC","7":"HEBREW","8":"UCS2"}'
         display: "Data Coding"
         comment: "Short message coding type"        
       - name: "serviceNumber"
@@ -111,4 +111,4 @@ omc:
         access: "rw"
         filter: "3~20"
         display: "Service Number"
-        comment: "It is the source address and length is between 3 and 20"   
+        comment: "It is the source address, the length is between 3 and 20"