When do encryption keys exchange?

[MC]

I have a problem with bonding with a static passkey. I have some sensors, which have a static passkey hardcoded in them. If I want to bond with them, I have to provide this passkey from my custom central app, which uses s120 and SDK 8.1.0. For the past few days I wasn't able to make a successfull bond, because I keep getting BLE_GAP_SEC_STATUS_AUTH_REQ from the sensor. I can't find much information on what to do in this case. I can bond with MCP just fine.

I compared log file from MCP and sniffer trace from my central bonding attempt and they are different in one very impotant aspect. MCP exchanges keys and encrypts the connection before trying to authenticate the link. Default behavioral of the device manage in SDK 8.1.0 is not the same. If I call dm_security_setup_req it only forces authentication without previous key exchange. This is why authentication fails. If I go into debug mode, I can see that keys are always 0. Does anyone have any suggestions about this matter? Are there any examples that mimic MCP behavioral?

Edit: added trace logs for windows phone, s120 and MCP log file, all done with the same sensor (which uses TI stack).

Windows phone pairing attempt: windows_pairing_with_adv.pcapng

S120 pairing attempt: s120_central_pairing.pcapng

MCP log file: log.txt

Android bonding attempt: android_bonding.pcapng

[MC]

I thought that it doesn't matter if it is from TI, as BLE responses and protocols should be standardised :) As for the pairing request, this is the main difference I was talking about, device manager in SDK 8 doesn't include sending the pairing request prior to authentication, or I don't know how to do it.

Both files I included were done at roughly the same time, after connection was established. In my attemt, no pairing request is ever sent, even if I set MITM. I tried all the combinations with and without MITM/bonding, the response is the same. If you could tell me how to initiate pairing request from s120, I think, it will solve my problem.