Hi,
Endpoint discovery is modified in OCF 1.0 Specification and eps field is
added. When I am trying this, I find the results are different between
multicast and unicast endpoint discovery.
I use occlientbasicops sample to test, unicast discovery seems not return
eps field in response payload.
Chen ; iotivity-dev@lists.iotivity.org
Subject: RE: [dev] Cannot find unowned devices
Coukd u use the latest cofe?
There had been an issue from a commit before, yesterday fix was applied on
1.3-rel.
BR Uze Choi
- Original Message -
Sender : June Chen
Date : 2017-07-12 12
Hi,
I am trying provisioning function with the sample of sampleserver_justwork
and provisioningclient of iotivity-1.3.0 release.
I use default dat files and build iotivity-1.3.0 with "scons SECURED=1".
But provisioningclient cannot always find unowned devices which are running
sampleserver_ju
ange message
04:57.925 DEBUG: MBED_TLS: bad server key exchange message
04:57.925 ERROR: OIC_CA_NET_SSL: Handshake error: -0x7b00
04:57.925 DEBUG: MBED_TLS: => send alert message
From: LVR Satish [mailto:satish.lankalapa...@inedasystems.com]
Sent: Wednesday, November 30, 2016 12:18
Hi,
We are trying to port Iotivity-1.2.0 to MIPS platform with security enabled
(SECURED=1).
We run sampleserver_justworks and provisioningclient in the same device and
always get handshake error.
Anyone ever see similar message? Do we miss something?
Any hint is greatly appreciated.
Than
cons TARGET_OS=android TARGET_ARCH=armeabi TARGET_TRANSPORT=ALL
WITH_CLOUD=1 WITH_TCP=1 WITH_MQ=SUB,PUB,BROKER SECURED=0 RELEASE=0
Built with TARGET_ARCH=armeabi-v7a was also tried, but it did not help
either.
Did anybody ever see this problem before? Any idea or hint is appreciated.
Thank you.