Configurable call recording policy

US9363368B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9363368-B2
Application numberUS-201314048937-A
CountryUS
Kind codeB2
Filing dateOct 8, 2013
Priority dateOct 8, 2013
Publication dateJun 7, 2016
Grant dateJun 7, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

In one embodiment, a communication is established between two endpoints. The communication session may be a video call or an audio call. The communication session may be managed by a call manager using, for example, voice over internet protocol and session initiation protocol. One of the endpoints initiates recording the communication session. The call manager facilitates recording the communication session based on a recording policy associated with the initiating endpoint. The recording policy may specify far end recording, near end recording, or a prioritized order of far and near end recording. The call manager selected an anchor network device for copying the communication session based on the recording policy.

First claim

Opening claim text (preview).

We claim: 1. A method comprising: establishing, by a processor, a communication session between a first endpoint and a second endpoint; receiving a trigger message to record the communication session; and selecting, by the processor, an anchor network device to direct network traffic to perform a recording of the communication session based on a recording policy, wherein the recording policy specifies that when a device profile is indicative of a gateway, a near end device is selected to perform the recording of the communication session and when the device profile is indicative of a phone, a far end device is selected to perform the recording of the communication session. 2. The method of claim 1 , further comprising: accessing profile information for the second endpoint, wherein the anchor network device is configured to direct network traffic to record the communication session based on the recording policy and the profile information. 3. The method of claim 1 , further comprising: extracting the recording policy from the trigger message, wherein the recording policy is associated with the first endpoint. 4. The method of claim 1 , further comprising: generating a command including an identification value for the anchor network device to record the communication session. 5. The method of claim 1 , wherein the recording policy describes recording capabilities or preferences of the first endpoint. 6. The method of claim 1 , wherein the trigger message includes an address for a repository configured to store the recording of the communication session. 7. The method of claim 6 , wherein establishing the communication session comprises: generating an invite message for the repository for storing the recording of the communication session, wherein the invite message includes an address of the first endpoint or an address of the second endpoint. 8. An apparatus comprising: a memory configured to store a recording policy and at least one device profile; a communication interface configured to receive a request to record a communication session; and a controller configured to access the recording policy and direct network traffic to perform a recording of the communication session based on the recording policy, wherein the recording policy includes a primary anchor device and a secondary anchor device, wherein the recording policy specifies that when the device profile is indicative of a gateway, the primary anchor device is selected to perform the recording of the communication session and when the device profile is indicative of a phone, the secondary anchor device is selected to perform the recording of the communication session. 9. The apparatus of claim 8 , wherein request to record the communication session is received from the primary anchor device or the secondary anchor device. 10. The apparatus of claim 8 , wherein the controller is configured to generate an invite message for a repository device, wherein the repository device is configured to store the recording of the communication session. 11. The apparatus of claim 8 , wherein the invite message includes an address of the primary anchor device or an address of the secondary anchor device. 12. The apparatus of claim 8 , wherein the controller is further configured to compile each device profile based on responses from the primary anchor device, secondary anchor device or a combination thereof. 13. The apparatus of claim 8 , wherein the recording policy includes a repository preference, wherein the repository preference includes an address of a repository, a name of the repository or a combination thereof. 14. The apparatus of claim 13 , wherein the repository preference includes a series of alternate repositories for storing a recording. 15. A non-transitory computer readable medium including instructions that when executed are configured to cause a processor to: establish a communication session between a first endpoint and a second endpoint; access a recording policy associated with the first endpoint or the second endpoint; identify an anchor point based on the recording policy, wherein the recording policy specifies that when a device profile of the anchor point is indicative of a gateway, a near end device is selected and when the device profile is indicative of a phone, a far end device is selected; and generate a control message for the anchor point to forward the communication session for recording. 16. The non-transitory computer readable medium of claim 15 , the instructions further configured to cause the processor to: receive a request to record the communication session from the first endpoint. 17. The non-transitory computer readable medium of claim 16 , wherein the anchor point is the second endpoint. 18. The non-transitory computer readable medium of claim 15 , wherein the recording policy lists the first endpoint and the second endpoint. 19. The non-transitory computer readable medium of claim 15 , wherein the first endpoint is a phone and the second endpoint is a gateway.

Assignees

Inventors

Classifications

  • Conversation recording systems (at the subscriber's set H04M1/656) · CPC title

  • Call or contact centers supervision arrangements · CPC title

  • Call monitoring, e.g. for law enforcement purposes; Call tracing; Detection or prevention of malicious calls · CPC title

  • Automatic arrangements for answering calls; Automatic arrangements for recording messages for absent subscribers; Arrangements for recording conversations (centralised dictation systems H04M11/10) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9363368B2 cover?
In one embodiment, a communication is established between two endpoints. The communication session may be a video call or an audio call. The communication session may be managed by a call manager using, for example, voice over internet protocol and session initiation protocol. One of the endpoints initiates recording the communication session. The call manager facilitates recording the communic…
Who is the assignee on this patent?
Cisco Tech Inc
What technology area does this patent fall under?
Primary CPC classification H04M3/42221. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jun 07 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).