Hi Uze,
I get the latest commit(1a2c9ee) of 1.3-rel and try again. It still doesn’t work and I also see 17:31.990 INFO: OIC_PM_UTILITY: Can not find secure port information. error message. In addition, I also try easy-setup with enrollee and mediator sample. It always fails to do “Provision Security to Enrollee”. I use the same environment and flow to build iotivity-1.3 and iotivity-1.2.1, but I cannot make iotivity-1.3 work so far. Any help would be appreciated. Thank you. BR June From: 최우제 [mailto:uzc...@samsung.com] Sent: Wednesday, July 12, 2017 12:26 PM To: June Chen <june.c...@u-media.com.tw>; 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 <june.c...@u-media.com.tw> Date : 2017-07-12 12:15 (GMT+9) Title : [dev] Cannot find unowned devices 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_justwork in the same machine. I see some suspicious log that it cannot find secure port information. Detailed log is also attached. Do I miss anything? Any advice would be appreciated. June === 17:31.990 DEBUG: PayloadLog: Payload Type: Discovery 17:31.990 DEBUG: PayloadLog: DI: 12345678-1234-1234-1234-123456789012 17:31.990 DEBUG: PayloadLog: Link#1 17:31.990 DEBUG: PayloadLog: URI:/oic/sec/doxm 17:31.990 DEBUG: PayloadLog: Anchor:ocf://12345678-1234-1234-1234-123456789012 17:31.990 DEBUG: PayloadLog: Resource Types: 17:31.990 DEBUG: PayloadLog: oic.r.doxm 17:31.990 DEBUG: PayloadLog: Interfaces: 17:31.990 DEBUG: PayloadLog: oic.if.baseline 17:31.990 DEBUG: PayloadLog: Bitmap: 1 17:31.990 DEBUG: PayloadLog: Secure?: false 17:31.990 DEBUG: PayloadLog: Port: 0 17:31.990 DEBUG: PayloadLog: 17:31.990 INFO: OIC_RI_PAYLOADPARSE: Finished parse payload, result is 0 17:31.990 DEBUG: OIC_CA_MSG_HANDLE: 63 2E 72 2E 64 6F 78 6D 62 69 66 81 6F 6F 69 63 17:31.990 DEBUG: OIC_CA_MSG_HANDLE: 2E 69 66 2E 62 61 73 65 6C 69 6E 65 61 70 BF 62 17:31.990 DEBUG: OIC_CA_MSG_HANDLE: 62 6D 01 FF FF FF 17:31.990 INFO: OIC_RI_STACK: Device ID of response : 12345678-1234-1234-1234-123456789012 17:31.990 INFO: OIC_PM_UTILITY: resPaylod->uri:/oic/sec/doxm 17:31.990 INFO: OIC_PM_UTILITY: Found doxm resource. 17:31.990 INFO: OIC_PM_UTILITY: Can not find secure port information. 17:31.990 INFO: OIC_RI_CLIENTCB: Deleting token 17:31.990 INFO: OIC_RI_CLIENTCB: DB 65 AA D5 00 A7 81 38 17:31.990 DEBUG: OIC_CA_CONN_MGR: CADestroyToken 17:31.990 DEBUG: OIC_CA_CONN_MGR: OUT 17:31.990 INFO: OIC_RI_CLIENTCB: Deleting callback with uri /oic/res?rt=oic.r.doxm 17:31.990 INFO: OIC_RI_STACK: Exit HandleCAResponses === _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
_______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
