Please give ur suggestions. Thank you.
>
Being selfish, I don't have time to write this for you, but I can
certainly outline what I would do:
You have the states:
Incoming Call
Missed Call
You have the event:
Phone Offhook
You would need to use the above triggers to write whichever of the
following variables were updated to a text file:
Call Name / Number/ Date / Time (In) (dynamic, monitored)
%CNAME / %CNUM / %CDATE / %CTIME
Call Name / Number/ Date / Time / Duration (Out)(dynamic, monitored)
%CONAME / %CONUM / %CODATE / %COTIME / %CODUR
(detailed on this page
http://tasker.dinglisch.net/userguide/en/variables.html)
I haven't tested, so I don't know if the variables 'aren't set' when a
call state isn't true - such as incoming call makes outgoing call
clear - or if they remain populated until the next call.
I'm sure you can see that %CTIME and %CODUR will differentiate between
incoming and outgoing for you. To find out which one of these has been
updated and therefore which other variables you write to a text file,
I would suggest setting %PREVIOUS-CTIME to %CTIME at the end of a
task, so next time a call is registered IF %CTIME =(matches) %PREVIOUS-
CTIME you would know that you need to write the %CODUR (outgoing)
variables to the text file - make sure they are appended.
You can set Tasker to zip the files up once a week and create a new
one, or if you definitely want it exported to your calendar, you would
'read paragraph' of the text file to a created variable of %CALL-LOG
and place that content into the calendar entry Tasker creates for you.
I hope the above made sense...? Any questions, happy to help.