Abstract: Some embodiments of the present invention provide a method and system for correlating information regarding an interactive communication. A session application record is provided to store information of a session that represents an interactive communication that is at least between two endpoints. An application programming interface (API) is provided for users to create and manipulate session application records. Application specific data or customized data can be stored with the session application record using a tag that includes a name and value pair. One session application record can be associated with another session application record by using a relation. Any information that is gathered during a session can be accessible even when one of the endpoints is replaced by another endpoint.

Abstract: A unified session detail records of a multi-hop session is provided. The multi-hop session may be established through multiple nodes in a VoIP network. Each node may generate session detail records for the legs of the multi-hop session that are connected to the node. The nodes on the path of the multi-hop call may send the record to a single node to consolidate the session detail records of the legs of the multi-hop call in the single node so that the single node can provide unified session detail records of the multi-hop session. By providing unified session detail records, the user does not need to track down the nodes that are on the path of the multi-hop call to obtain the session detail records of the multi-hop session.

Abstract: Some embodiments of the present invention provide a method and system for correlating information regarding an interactive communication. A session application record is provided to store information of a session that represents an interactive communication that is at least between two endpoints. An application programming interface (API) is provided for users to create and manipulate session application records. Application specific data or customized data can be stored with the session application record using a tag that includes a name and value pair. One session application record can be associated with another session application record by using a relation. Any information that is gathered during a session can be accessible even when one of the endpoints is replaced by another endpoint.