From cbc5e63127b53bb2adf13c4a81fe8024ac1272dc Mon Sep 17 00:00:00 2001 From: "daeken.kwon" Date: Tue, 6 Oct 2015 14:32:32 +0900 Subject: [PATCH] [IOT-762] Something wrong with handling unicast presence response - client always get "PRESENCE_TIMEOUT" < Cause > ocstack don't do ResetPresenceTTL() after getting presence response from server because there was no change in sequnceNumber < Solution > To resolve this case, it is just needed to put ResetPresenceTTL() before exit in this caseTo resolve this case, it seems that we just put ResetPresenceTTL() before exit in this case Change-Id: If1e32692d3b859cea84382bded0cceecf42874d5 Signed-off-by: daeken.kwon Reviewed-on: https://gerrit.iotivity.org/gerrit/3595 Reviewed-by: Uze Choi Tested-by: jenkins-iotivity Reviewed-by: Patrick Lankswert --- resource/csdk/stack/src/ocstack.c | 2 ++ 1 file changed, 2 insertions(+) mode change 100644 => 100755 resource/csdk/stack/src/ocstack.c diff --git a/resource/csdk/stack/src/ocstack.c b/resource/csdk/stack/src/ocstack.c old mode 100644 new mode 100755 index cf2ccb8..d458b22 --- a/resource/csdk/stack/src/ocstack.c +++ b/resource/csdk/stack/src/ocstack.c @@ -931,6 +931,8 @@ OCStackResult HandlePresenceResponse(const CAEndpoint_t *endpoint, if(cbNode->sequenceNumber == response.sequenceNumber) { OC_LOG(INFO, TAG, "No presence change"); + ResetPresenceTTL(cbNode, maxAge); + OC_LOG_V(INFO, TAG, "ResetPresenceTTL - TTLlevel:%d\n", cbNode->presence->TTLlevel); goto exit; } -- 2.7.4