Jay, Pat explained TTL in the attached email. Please let us know if you need more information. Thanks, =Sam
From: ??? [mailto:junghyun...@samsung.com] Sent: Thursday, April 16, 2015 5:26 PM To: ???; Samidurai, Sakthivel; Kesavan, Vijay S; ??? Cc: iotivity-dev at lists.iotivity.org Subject: Fwd: Re: Re: [dev] [Multicast presence Issue raise] FW: Inquire about base C API for multicast presence Sam, One more thing. :) Could explain us the "Subject" or "Purpose" of the ttl for the API "OCStartPresence()"? Let me clarify my question with the definition of "ttl" & please correct me if I'm wrong. TTL : Maximum time for multicasting the presence packet from Resource server side. Q1. The presene packet can only be sent when the Application calls the "OCProcess". Sample applications are using "While loop" in order to call the "OCProcess" to multicast the presence packet. Then what is the usage the the "TTL" if the C-Stack doesn't care this TTL. inside? The doxygen description in the header is not enough for us to understand the usage of it. So we will be appreciated if you share us bit more detailed information of Presence feature related APIs. Thank you. Jay. ------- Original Message ------- Sender : ???<junghyun.oh at samsung.com<mailto:junghyun.oh at samsung.com>> S5(??)/??/IoT Solution Lab(S/W??)/???? Date : 2015-04-17 09:12 (GMT+09:00) Title : Re: Re: [dev] [Multicast presence Issue raise] FW: Inquire about base C API for multicast presence Hi Sam, I have a question based on your reply.. Why the format of input parameter for the "Presence Check" is different? Since the multicast presence need uri without scheme & port #, unicast presence requires fully uri (scheme://address:port/path). Could we abstract the input parameter for the presence bit more general form? ex) Remove, scheme(coap, http, etc..), the Multicast IP Addr(224.0.1.187) & Common Uri(/oc/presence) Anyway, I will talk with developers who reported this issues with your answer. Thank you. Jay. ------- Original Message ------- Sender : Samidurai, Sakthivel<sakthivel.samidurai at intel.com<mailto:sakthivel.samidurai at intel.com>> Date : 2015-04-17 08:10 (GMT+09:00) Title : Re: [dev] [Multicast presence Issue raise] FW: Inquire about base C API for multicast presence Uze, We are unable to reproduce the presence issue. We tested on the same and two systems with WI-FI/Ethernet. We tested with both C++ and C sample and clients is getting the presence notification. * Multicast presence: The app can use ?224.0.1.187/oc/presence? * Unicast Presence: The app can use ?coap://<server IP>:6298/oc/presence? We recommend trying the Iotivity base C/C++ sample application on your test system and let us know the test results. Please open a JIRA ticket and provide steps to reproduce the issue. The client does not receive any presence notification if the client discovered the server but there is no change in the resource. In this case, the server does not send any presence notification. Please note that we identified a presence TIMEOUT issue that is not related to the presence issue that you have reported. The presence timeout fix is in the changeset https://gerrit.iotivity.org/gerrit/#/c/759/ with commit ad60f765b797923ca457322abb83331c9563e12f. The misleading presence log messages in C sample server source (ocserver.cpp) are modified in the changeset : https://gerrit.iotivity.org/gerrit/#/c/748/ The test log is below for your reference. Multicast presence Log: query: 224.0.1.187/oc/presence<http://224.0.1.187/oc/presence> requiredUri=224.0.1.187/oc/presence<http://224.0.1.187/oc/presence> referenceUri=(null) conType=1 43:21.738 INFO: occlient: Callback Context for Presence recvd successfully 43:21.738 INFO: occlient: StackResult: OC_STACK_OK 43:21.738 INFO: occlient: NONCE NUMBER: 154451112 43:21.738 INFO: occlient: Callback Context for Presence notification recvd successfully 0 43:21.738 INFO: occlient: JSON = (null) =============> Presence Response 43:23.738 INFO: occlient: Callback Context for Presence recvd successfully 43:23.738 INFO: occlient: StackResult: OC_STACK_OK 43:23.738 INFO: occlient: NONCE NUMBER: 4221900748 43:23.738 INFO: occlient: Callback Context for Presence notification recvd successfully 1 43:23.738 INFO: occlient: JSON = (null) =============> Presence Response 43:27.738 INFO: occlient: Callback Context for Presence recvd successfully 43:27.738 INFO: occlient: StackResult: OC_STACK_OK 43:27.738 INFO: occlient: NONCE NUMBER: 2132196551<tel:2132196551> 43:27.738 INFO: occlient: Callback Context for Presence notification recvd successfully 2 43:27.738 INFO: occlient: JSON = (null) =============> Presence Response 43:29.738 INFO: occlient: Callback Context for Presence recvd successfully 43:29.738 INFO: occlient: StackResult: OC_STACK_OK 43:29.738 INFO: occlient: NONCE NUMBER: 2474188232 43:29.738 INFO: occlient: Callback Context for Presence notification recvd successfully 3 43:29.738 INFO: occlient: JSON = (null) =============> Presence Response Unicast presence Log: Query: coap://192.168.1.104:6298/oc/presence<http://192.168.1.104:6298/oc/presence> 46:48.042 INFO: occlient: Callback Context for Presence recvd successfully 46:48.042 INFO: occlient: StackResult: OC_STACK_OK 46:48.042 INFO: occlient: NONCE NUMBER: 98872639 46:48.042 INFO: occlient: Callback Context for Presence notification recvd successfully 0 46:48.042 INFO: occlient: JSON = (null) =============> Presence Response 46:52.042 INFO: occlient: Callback Context for Presence recvd successfully 46:52.042 INFO: occlient: StackResult: OC_STACK_OK 46:52.042 INFO: occlient: NONCE NUMBER: 3881206201 46:52.042 INFO: occlient: Callback Context for Presence notification recvd successfully 1 46:52.042 INFO: occlient: JSON = (null) =============> Presence Response 46:54.042 INFO: occlient: Callback Context for Presence recvd successfully 46:54.042 INFO: occlient: StackResult: OC_STACK_OK 46:54.042 INFO: occlient: NONCE NUMBER: 2187039498<tel:2187039498> 46:54.042 INFO: occlient: Callback Context for Presence notification recvd successfully 2 46:54.042 INFO: occlient: JSON = (null) =============> Presence Response 46:56.042 INFO: occlient: Callback Context for Presence recvd successfully 46:56.042 INFO: occlient: StackResult: OC_STACK_OK 46:56.042 INFO: occlient: NONCE NUMBER: 474262046 46:56.042 INFO: occlient: Callback Context for Presence notification recvd successfully 3 46:56.042 INFO: occlient: JSON = (null) =============> Presence Response We have highlighted the presence notification being sent by the server and them being received by the client. linux/SimpleClientServer$ ./ocserver -o0 29:50.982 DEBUG: ocserver: OCServer is starting... Sending presence notification Sending presence notification Sending payload 1983849130:60 Sending presence notification Sending payload 876748912:60:core.light 29:50.990 INFO: ocserver: Created Light resource with result: OC_STACK_OK 29:50.990 INFO: ocserver: Entering ocserver main loop... Sending payload {"href":"/a/light","sid":"2441775918","prop":{"rt":["core.light"], "if":["oc.mi.def"],"obs":1}} Sending presence notification Sending payload 876748912:60 30:00.998 INFO: ocserver: ================ presence count 10 30:00.998 INFO: ocserver: Creating /a/fan for presence Sending presence notification Sending payload 285258306:60:core.fan 30:06.002 INFO: ocserver: Creating /a/led for presence Sending presence notification Sending payload 1003359691:60:core.led 30:11.002 INFO: ocserver: ================ presence count 9 30:16.003 INFO: ocserver: Deleting /a/fan for presence Sending presence notification Sending payload 126341009:60:core.fan 30:21.003 INFO: ocserver: ================ presence count 8 30:21.003 INFO: ocserver: Deleting /a/led for presence Sending presence notification Sending payload 4292822242:60:core.led 30:31.003 INFO: ocserver: ================ presence count 7 30:41.003 INFO: ocserver: ================ presence count 6 30:51.003 INFO: ocserver: ================ presence count 5 31:01.003 INFO: ocserver: ================ presence count 4 31:11.003 INFO: ocserver: ================ presence count 3 31:21.003 INFO: ocserver: ================ presence count 2 31:31.003 INFO: ocserver: ================ presence count 1 31:41.003 INFO: ocserver: ================ stopping presence Sending payload 558822771:0 ./occlient -c1 -t12 29:52.350 INFO: occlient: Entering occlient main loop... 29:58.350 INFO: occlient: Callback Context for DISCOVER query recvd successfully 29:58.350 INFO: occlient: StackResult: OC_STACK_OK 29:58.350 INFO: occlient: Discovered on WiFi 29:58.350 INFO: occlient: Device =============> Discovered {"oc":[{"href":"/a/light","sid":"2441775918","prop":{"rt":["core.light"], "if":["oc.mi.def"],"obs":1}}]} @ 10.246.31.157:6298 29:58.350 INFO: occlient: Executing InitPresence 30:00.354 INFO: occlient: Callback Context for Presence recvd successfully 30:00.354 INFO: occlient: StackResult: OC_STACK_OK 30:00.354 INFO: occlient: NONCE NUMBER: 876748912 30:00.354 INFO: occlient: Callback Context for Presence notification recvd successfully 0 30:00.354 INFO: occlient: JSON = (null) =============> Presence Response 30:02.354 INFO: occlient: Callback Context for Presence recvd successfully 30:02.354 INFO: occlient: StackResult: OC_STACK_OK 30:02.354 INFO: occlient: NONCE NUMBER: 285258306 30:02.354 INFO: occlient: Callback Context for Presence notification recvd successfully 1 30:02.354 INFO: occlient: JSON = (null) =============> Presence Response 30:06.358 INFO: occlient: Callback Context for Presence recvd successfully 30:06.358 INFO: occlient: StackResult: OC_STACK_OK 30:06.358 INFO: occlient: NONCE NUMBER: 1003359691 30:06.358 INFO: occlient: Callback Context for Presence notification recvd successfully 2 30:06.358 INFO: occlient: JSON = (null) =============> Presence Response 30:16.379 INFO: occlient: Callback Context for Presence recvd successfully 30:16.379 INFO: occlient: StackResult: OC_STACK_OK 30:16.379 INFO: occlient: NONCE NUMBER: 126341009 30:16.379 INFO: occlient: Callback Context for Presence notification recvd successfully 3 30:16.379 INFO: occlient: JSON = (null) =============> Presence Response 30:22.387 INFO: occlient: Callback Context for Presence recvd successfully 30:22.387 INFO: occlient: StackResult: OC_STACK_OK 30:22.387 INFO: occlient: NONCE NUMBER: 4292822242 30:22.387 INFO: occlient: Callback Context for Presence notification recvd successfully 4 30:22.387 INFO: occlient: JSON = (null) =============> Presence Response 31:22.447 INFO: occlient: Callback Context for Presence recvd successfully 31:22.447 INFO: occlient: StackResult: OC_STACK_PRESENCE_TIMEOUT 31:22.447 INFO: occlient: NONCE NUMBER: 0 31:22.447 INFO: occlient: Callback Context for Presence notification recvd successfully 5 31:22.447 INFO: occlient: JSON = (null) =============> Presence Response 31:42.455 INFO: occlient: Callback Context for Presence recvd successfully 31:42.455 INFO: occlient: StackResult: OC_STACK_PRESENCE_STOPPED 31:42.455 INFO: occlient: NONCE NUMBER: 558822771 31:42.455 INFO: occlient: Callback Context for Presence notification recvd successfully 6 31:42.455 INFO: occlient: JSON = (null) =============> Presence Response Thanks, =Sam From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Kesavan, Vijay S Sent: Wednesday, April 15, 2015 6:21 PM To: uzchoi at samsung.com<mailto:uzchoi at samsung.com> Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] [Multicast presence Issue raise] FW: Inquire about base C API for multicast presence Uze, The team is investigating both the presence issues. We do not have a fix yet and will provide either a fix or an update to you by tomorrow. It sounded like Jyong Kim?s suggestion is addressing the multicast presence issue for you, so we are prioritizing the unicast presence issue. In any case, we will send you an update tomorrow. --Vijay From: ???(Uze Choi) [mailto:uzc...@samsung.com] Sent: Wednesday, April 15, 2015 6:09 PM To: Kesavan, Vijay S Cc: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: RE: [Multicast presence Issue raise] FW: [dev] Inquire about base C API for multicast presence Hi Vijay, Would you mind answering for my question? Your answer will affect our QA test schedule, so that we need it. BR, Uze Choi From: ???(Uze Choi) [mailto:uzc...@samsung.com] Sent: Wednesday, April 15, 2015 7:30 PM To: Kesavan, Vijay S (vijay.s.kesavan at intel.com<mailto:vijay.s.kesavan at intel.com>) Cc: 'iotivity-dev at lists.iotivity.org' Subject: [Multicast presence Issue raise] FW: [dev] Inquire about base C API for multicast presence Importance: High Hi Vijay, We are urgently integrating the master branch merged from CA with our primitive services. There seems to be several major problems but I wish you resolve two issues regarding multicast presence. 1. Multicast presence issue in the C API layer as following mail.(Doil.Kwon) 2. Unicast Presence request fail (Hyunjun.Kim will send detail later) If you willing to fix them in a couple of days, we will wait. Unless we will fix our code workaround which may cause the side effect, but there is no other option to make the release time. If possible let us know the status on tomorrow OSWG CC. or direct call setup please. BR, Uze Choi From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of ??? Sent: Wednesday, April 15, 2015 10:54 AM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] Inquire about base C API for multicast presence Dear iotivity-dev members. i am doil kwon and resource hosting developer. our application is not working about multicast presence for using base C API. After analyzing causes, previous version is a request for using uri that is "coap://224.0.1.187/oc/presence" in order to request multicast presence, After merging "CA branch",we didn't receive callback message about presence although we request,too. so, Checking "Base" and "CA" code, if there is not port, don't transfer message(ex: "coap://224.0.1.187/oc/presence"), and if there is port, can transfer message(ex: "coap://224.0.1.187:5683/oc/presence"),but don't find cbData when receiving callback message. it is occurred that we don't find cbData because occlientcb search for multicast presence request uri using "224.0.1.187/oc/presence". so, i want to know how we can solve this problem. if you know this, plz tell me about any solution. BR, doil kwon. ________________________________ ? ? ? (Doil Kwon) S3 / Assistant Engineer Advanced Convergence Lab. Software R&D Center. Samsung Electronics Co., Ltd. Tel: +82-31-279-3894 Mobile : +82-10-5648-2660 E-Mail : doil.kwon at samsung.com<mailto:doil.kwon at samsung.com> ________________________________ Jung-hyun Oh. IoT Solution Lab. | SW R&D Center | SAMSUNG ELECTRONICS CO.,LTD Mobile +82-10-9890-6731 | Beyond your imagination, Always Jung-hyun Oh. IoT Solution Lab. | SW R&D Center | SAMSUNG ELECTRONICS CO.,LTD Mobile +82-10-9890-6731 | Beyond your imagination, Always [cid:image001.gif at 01D0787A.A54C5210] [http://ext.samsung.net/mailcheck/SeenTimeChecker?do=d083a0c0528fae52948c007eb0b7a0279d818e4639c8639daa7d5f2254dc0a9a79ea3fd7a9838f8b0082e009b7802cd90cfaa4221cd57baf4bea3c1765014a1208cece8541bc14eacf878f9a26ce15a0] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150417/f3f1dab2/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 13168 bytes Desc: image001.gif URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150417/f3f1dab2/attachment.gif> -------------- next part -------------- An embedded message was scrubbed... From: "Lankswert, Patrick" <patrick.lanksw...@intel.com> Subject: Re: [dev] Question - What is the usage of the "ttl" when using the "OCStartPresence" Date: Thu, 16 Apr 2015 16:23:04 +0000 Size: 45884 URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150417/f3f1dab2/attachment.mht>
