How I can get phone name or address on S110 based proximity device ?

RE: How I can get phone name or address on S110 based proximity device ?

RK — Sun, 28 Aug 2016 23:54:37 GMT

No the peer name is not in there, that requires reading a characteristic on the other device. It's the peer address you need to recognise the peer anyway, the name is totally irrelevant.

RE: How I can get phone name or address on S110 based proximity device ?

FlashBack — Sun, 28 Aug 2016 21:46:30 GMT

But if peer name is also available there ? As in that structure I can get address only of peer. Or name is not translated to device ?

RE: How I can get phone name or address on S110 based proximity device ?

FlashBack — Sun, 28 Aug 2016 21:28:17 GMT

Oh, right. That was very close, found in p_ble_evt->evt.gap_evt.params.connected.peer_addr Thanks a lot!

RE: How I can get phone name or address on S110 based proximity device ?

FlashBack — Sun, 28 Aug 2016 21:26:08 GMT

Yes, but in BLE_GAP_EVT_CONNECTED event I am getting 2 sources of information : ble_evt_t * p_ble_evt and m_conn_handle = p_ble_evt->evt.gap_evt.conn_handle, which is part of p_ble_evt. So, they allow me to get local address, local name and I can perform some operations like disconnection, getting rssi info and other around connection. But how I can get peer information there ? Looks I am missing something :(

RE: How I can get phone name or address on S110 based proximity device ?

RK — Sun, 28 Aug 2016 01:03:45 GMT

The address of the central is in the data which comes with the connection event, BLE_GAP_EVT_CONNECTED. That gives you your address and the peer address and a whole load of other information too.

No there is no other mechanism besides whitelisting to block incoming connections. If you advertise connectably without a whitelist anything can connect to you, read the GATT table and attempt to read and write characteristics. Depending on the permissions you set up for the services it may not be able to read or write anything and after it's connected you will get an event and can disconnect it again forcibly, but absent a whitelist, anything can get as far as being connected to you.