RPC NoCall response from device may trigger unexpected RPC frame.

When the controller performs a RPC request (e.g. Connect.req, Prmend.req) for which the device processing requires some time, the controller will send a RPC ping. When a device then first sends the response and afterwards sends a RPC No Call, the controller will send a RPC response frame to the device containing the same content as the device's RPC rersponse frame. Additionally the controller might abort the current operation (e.g. establishing a connection)

It is expected, that the controller ignores this frame.