Hello Marcel, I have incorporated your feedback into the document . Please let me know if anything needs to be changed. Thanks Raji Callhistory Adapter-Agent CallHistory is a built in plugin for ofono. It uses CallHistoryAgent api exposed by client to push voice call history information. CallHistoryAgent api is a service interface exposed by client over dbus. Plugin exposes CallHistory interface that CallHistoryAgent registers and unregisters with. if the CallHistoryAgent registers with CallHistory then plugin pushes the history information to the agent soon as it receives from ofono, otherwise it caches the data in a disk file until agent registers, once agent registers plugin will read the data from the disk file and pushes all the records to it. CallHistory: it is going to register and unregister the agent. It calls the methods on the agent for delivering history information whent the agent is up and running. The history record will be written to the disk if agent method returns error or if the agent is not running. CallHistory hierarchy ============= Service : org.ofono Interface : org.ofono.CallHistory Object path : [variable prefix]/{modem0,modem1,...}/CallHistory Methods void RegisterAgent (objectpath) RegisterAgent method registers the agent object path. Methods on this agent will be called if history needs to push data. Possible Errors: [service].Error.InvalidArguments [service].Error.InvalidFormat [service].Error.InUse void UnregisterAgent (objectpath) UnregisterAgent method unregister the already registered agent object path. Possible Errors: [service].Error.InvalidArguments [service].Error.InvalidFormat [service].Error.InUse CallHistoryAgent hierarchy ================ Service Name : Unique Name Interface : org.ofono.CallHistoryAgent Objectpath : Freely definable Methods void SendHistory( array{dict}) This method gets called by ofono to deliver an array of records. Each record is represented as a dictionary, all the dict properties are described in the "Properties" section. Possible Errors: [service].Error.Unsuccessful void Release() Cleans up agent, assumes that agent is already unregistered, so not needed to unregister. Properties ======= integer Uid [Read Only] Integer representing the unique id of the history record string Calltype [Read Only] string representing the call type. Call type can be one of the following three alternatives "outgoing" - it is an outgoing call "incoming" - it is an incoming call "missed" - it is a missed call string LineIdentification [Read Only] string representing the LineIdentification , for outgoing call it is the phone number dialed. For Incoming call it is the CLIP, or COLP if received by the underlying implementation. string StartTime [Read Only] String representing start time of the call string EndTime [Read Only] String representing end time of the call

Marcel, org.ofono.History will be the main adapter interface and org.ofono.CallHistoryAgent the callhistory agent and org.ofono.SmsHistoryAgent as the sms history agent. I want to seperate the two agents so that sms app will expose sms history agent and dialer will register and expose callhistory agent. Then it will be clear which agent is interested in which history, vs one org.ofono.HistoryAgent exposing ReportCall and ReportTextMessage methods. In the later case adapter needs to flush both smshistory and callsistory onto two agents even though agents are not interested only in type of history. Does it sound reasonable? Thanks, Raji Marcel Holtmann wrote:

Hello Marcel, Marcel Holtmann wrote: No, Dialer and Sms applications are the ones that read and stores locally, this will probably move to tracker eventually. So I dont think we can assume that there is going to be a tracker agent. I am thinking by separating the applications will only register and get data they are interested in.

Marcel, Marcel Holtmann wrote: For outgoing TextMessages, ofono updates the history plugin in two method calls, first all the text message history related properties msg id, message , local received time,actual sent time, lineid and status='Pending' and in another method ofono updates plugin with the status. Earlier design, I sent out history record with pending status and when I received status update I used 'property changed' signal for status update. But I use 'uint32,variant' type which is not consistent with the current ofono property changed signal type. My questions, 1) Are you ok with using signal for status update, this lets us send out history as soon as we receive them if the agent is running 2) If we want to avoid signal, then we can store the outgoing text message record until we receive the status update from ofono, combine them and send out in case of agent running. In case of agent not running we do this anyway.

Marcel, Marcel Holtmann wrote: Updated API is below. Raji _______________________________________________ History Adapter-Agent History is a built in plugin for ofono. It uses HistoryAgent api exposed by client to push history information. HistoryAgent api is a service interface exposed by client over dbus. Plugin exposes History interface that HistoryAgent registers and unregisters with. if the HistoryAgent registers with History then plugin pushes the history information to agent soon as it receives from ofono, otherwise it caches the data in a disk file until agent registers, once agent registers plugin will read the data from the disk file and pushes all the records to it. History: it is going to register and unregister the agent. It calls the methods on the agent for delivering history information whent the agent is up and running. The history record will be written to the disk if agent method returns error or if the agent is not running. For outgoing messages ofono hands over history to plugin in 2 calls. It calls the plugin with all the message history properties with 'Pending" status first and updates the status with another method call. Plugin updates the messages history to client in 2 calls using same ReportTextMessage method. History hierarchy ============================ Service : org.ofono Interface : com.meego.TelephonyHistory Object path : / Methods void RegisterAgent (objectpath) RegisterAgent method registers the agent object path. Methods on this agent will be called if history needs to push data. Possible Errors: [service].Error.InvalidArguments [service].Error.InvalidFormat [service].Error.InUse void UnregisterAgent (objectpath) UnregisterAgent method unregister the already registered agent object path. Possible Errors: [service].Error.InvalidArguments [service].Error.InvalidFormat [service].Error.InUse HistoryAgent hierarchy ========================== Service Name : Unique Name Interface : com.meego.TelephonyHistoryAgent Objectpath : Freely definable Methods void ReportTextMessage( array{dict}) This method gets called by ofono to deliver an array of records. Each record is represented as a dictionary, all the dict properties are described in the "Properties" section. Possible Errors: [service].Error.Failed void ReportVoiceCall( array{dict}) This method gets called by ofono to deliver an array of records. Each record is represented as a dictionary, all the dict properties are described in the "Properties" section. Possible Errors: [service].Error.Failed void Release() Cleans up agent, assumes that agent is already unregistered, so not needed to unregister. Properties ========== uint32 Uid [Read Only] Integer representing the internal representation of histroy message id. string Type [Read Only] string representing the type of the history message. Type can be one of the following three alternatives. "outgoing" - it is an outgoing history message "incoming" - it is an incoming history message "missed" - It is a history message for missed call string LineIdentification [Read Only] string representing the LineIdentification , for outgoing message it is the phone number dialed. For incoming message it is the CLIP, or COLP if received by the underlying implementation. String Message [Read Only] string represents the text message. string LocalSentTime [Read Only] String representing local sent time. string SentTime [Read Only] String representing sent time. string StartTime [Read Only] String representing start time of the call string EndTime [Read Only] String representing end time of the call dict Information [Read Only] dict representing modem path from which this message originates "Modem" - will fetch object path of the modem

Hi Denis, by modem makes no sense. That might change at any time. For example even if you get a phone replacement. So not really helpful. The IMSI I can see, but isn't it better then just to include the IMSI into the report send to the history application. Not that I actually like sending the IMSI around so much :( Regards Marcel