If the network server creates a new AppSKeyEvelope for a DeviceSession (e.g. after a re-join), this information has to be sent as DeviceActivationContext to the ApplicationServer, in order to enable proper data decryption.
If this cal (NS->ASl fails, the DeviceActivationContext has to be re-sent with the next call.
This did not happen until now, as the AppSKeyEvelope is cleared before the actual call is executed.
brocaar
commented
3 years ago
If the network server creates a new AppSKeyEvelope for a DeviceSession (e.g. after a re-join), this information has to be sent as DeviceActivationContext to the ApplicationServer, in order to enable proper data decryption.
If this cal (NS->ASl fails, the DeviceActivationContext has to be re-sent with the next call. This did not happen until now, as the AppSKeyEvelope is cleared before the actual call is executed.