Using the Call Journaling feature, you can capture the call history data.

The Call Journaling High Availability feature provides full redundancy of the call log data, including data storage and retrieval. Call log data is redundant for Session Manager user communities with only one Session Manager because call log data is stored on up to two Session Managers per Data Center, for multiple Session Managers in a Data Center. Irrespective of the number of Session Managers configured, the user’s call log data is still available from other Session Manager instances. Although call logs are not maintained on Branch Session Manager, any Session Manager instance in service records missed calls while an endpoint is registered to the Branch Session Manager.

Before Release 8.0.1, when you change the primary, secondary, or both Session Managers, the existing call history was preserved. However, the new Session Manager moves the call logs from the old primary, secondary, or both Session Managers to the new primary, secondary, or both Session Managers. With Session Manager Release 8.0.1 or higher, the call history movement to new Session Managers is not required since all the call log data is stored on up to two Session Manager instances per Data Center.