Explanation/Reference:
Reference: http://www.cisco.com/c/dam/en/us/td/docs/telepresence/infrastructure/vcs/admin_guide/ Cisco_VCS_Administrator_Guide_X7-2.pdf Explanation: Search history The Search history page(Status> Search history)lists the most recent 255 searches that have taken place since the VCS was last restarted.
About searches
Before a call can be placed, the endpoint being called must be located. The VCS sends and receives a series of messages during its attempt to locate the endpoint being called; these messages are each known as searches. An individual call can have one or more searches associated with it, and these searches can be of different types.
The type of search message that is sent depends on whether the call is for SIP or H.323, and whether the call request was received locally or from an external zone, as follows:
H.323 calls that are placed locally: two messages are sent-the first is an ARQ which locates the device

being called, and the second is the call Setup which sends a request to the device as king it to accept the call. Each message shows up as a separate search in the Search history page, but only the Setup message is associated with a particular call.
H.323 searches originating from external zones: an LRQ will appear in the Search history page.

SIP: a single message is sent in order to place a call :this is either a SIP INVITE or a SIP OPTIONS.

Search details
The Search details page lists full information about either an individual search, or all searches associated with a single call (depending on how you reached the page) The information shown includes:
the subzones and zones that we researched

The call path and hops

Any transforms that were applied to the alias being searched for

use of policies such as Admin Policy or User Policy(Find Me)

Any policy services that were used