Open Ziabatcha opened 5 months ago
Tested okay with MWDI latest version test_v1.1.5.
curl -X POST "http://xxx:xxx/v1/regard-device-attribute-value-change" -H "accept: application/json" -H "user: User Name" -H "originator: Resolver" -H "x-correlator: 550e8400-e29b-11d4-a716-446655440000" -H "trace-indicator: 1.3.1" -H "customer-journey: Unknown value" -H "operation-key: Operation key not yet provided." -H "Content-Type: application/json" -d "{\"notification-proxy-1-0:attribute-value-changed-notification\":{\"counter\":7,\"timestamp\":\"2024-04-02T07:29:02.0+00:00\",\"object-path\":\"/core-model-1-4:network-control-domain=live/control-construct=513250008/logical-termination-point=LTP-MWPS-TTP-RADIO-2A/layer-protocol=LP-MWPS-TTP-RADIO-2A/air-interface-2-0:air-interface-pac/air-interface-configuration\",\"attribute-name\":\"power-is-on\",\"new-value\":\"true\"}}"
http://xxx:xx/v1/regard-device-attribute-value-change
{"notification-proxy-1-0:attribute-value-changed-notification":{"counter":7,"timestamp":"2024-04-02T07:29:02.0+00:00","object-path":"/core-model-1-4:network-control-domain=live/control-construct=xx/logical-termination-point=LTP-MWPS-TTP-RADIO-2A/layer-protocol=LP-MWPS-TTP-RADIO-2A/air-interface-2-0:air-interface-pac/air-interface-configuration","attribute-name":"power-is-on","new-value":"true"}}
With latest package 1.1.2d , have checked the API http://xxx:xx/v1/regard-device-attribute-value-change for SIAE and HUAWEI vendors and its working.
As of now generic notifications are supported for E/// hence validation pending for avc.
When below notification is received from NP, observing 500 internal server error. Also tried the same notification on MWDI test_v1.1.4, observing same error message
Notification: