Latest odata4-update branches include support for “eCall marshalling” - the idea that outgoing ecall client requests (callback & resendMSD) may need different remote endpoints depending on source of the original message received.
As per webplk2-frontend#82
Therefore configuration of the eCall quark has also changed, but in a backward compatible way, hopefully. In the “eCall” section of the settings file, “receivers” object has configuration for available receivers:
"eCall": {
"serviceBaseAddress": "http://localhost:8385",
"clientUri": "http://193.77.24.79:8080/ecall4allCommand/RecallResendReceiver/RecallResendReceiver",
"receivers": [
{"name":"123.33.13.11", "uri":"http://193.77.24.79:8080/ecall4allCommand/RecallResendReceiver/RecallResendReceiver"},
{"name":"123.33.13.22",
"uri":"http://193.77.11.79:1090/ecall4allCommand/RecallResendReceiver/RecallResendReceiver"},
],
"provider": "default",
"subsystem": "",
"location": "",
"active": 1
}
receivers is an array of objects containing configuration for each separate receiver:
- name: name of the receiver should be substring of value found in callId field of the eCall message from last @ character to the end (ie: if callId is
asd21312312313@13.13.13.13, name should be13.13.13.13 - uri: full remote endpoint receiver uri
In example above, we have defined two receivers:
- for received ecall having callId field ending with @123.33.13.11, remote endpoint will be
http://193.77.24.79:8080/ecall4allCommand/RecallResendReceiver/RecallResendReceiver - for received ecall having callId field ending with @123.33.13.22, remote endpoint will be
http://193.77.11.79:1090/ecall4allCommand/RecallResendReceiver/RecallResendReceiver
As for “backward compatibility” part - if no receivers are specified, for every eCall client request default remote endpoint is used, as configured in clientUri setting.
Links are still the same:
OData v4 update to test. Download from here: