CONTINUOUS CALL RECORDING

• US 20170064075A1
• Filed: 08/25/2015
• Published: 03/02/2017
• Est. Priority Date: 08/25/2015
• Status: Active Grant

• Current Assignee: Arlington Technologies, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: Avaya Incorporated
• Inventors: Chatterjee, Manish
• Granted Patent: US 9,992,331 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 65/1046 Call controllers; Call servers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1083 In-session procedures
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04M 3/12 Marking faulty circuits "busy"; Enabling equipment to disengage itself from faulty circuits ; Using redundant circuits; Response of a circuit, apparatus or system to an error
• CPC Class Codes: H04M 3/2254 in networks
• CPC Class Codes: H04M 3/42221 Conversation recording systems at the subscriber's set H04M1/656

Abstract

In order to allow for redundant call recording, a first message is received by a first media recorder indicating that a second media recorder is recording a media stream of a communication session between a plurality of communication devices. The first message includes a unique identifier for the communication session between the plurality of communication devices. A determination is made that the second media recorder is unable to continue to record the media stream. In response to determining that the second media recorder is unable to record the media stream, the first media recorder sends a second message, to a Session Border Controller (SBC), that includes the unique identifier for the communication session between the plurality of communication devices. The SBC streams the media stream to the first media recorder. The first media recorder receives the media stream and records the media stream.

Claims

1. A method comprising:

receiving, at a first media recorder, a first message indicating that a second media recorder is either recording a media stream of a communication session between a plurality of communication devices, receiving a media stream of the communication session between the plurality of communication devices, or going to start receiving the media steam of the communication session between the plurality of communication devices, wherein the first message includes a unique identifier for the communication session between the plurality of communication devices;

determining that the second media recorder is unable to continue recording the media stream;

in response to determining that the second media recorder is unable to continue recording the media stream, sending a second message, to a Session Border Controller (SBC), that includes the unique identifier for the communication session between the plurality of communication devices; and

receiving, at the first media recorder, the media stream via the SBC.

2. The method of claim 1, wherein the unique identifier is at least one of a Global Session Identifier (GSID) and a Universal Call Identifier (UCID).

3. The method of claim 1, wherein the second message is a one of a Session Initiation Protocol (SIP) INVITE message, a SIP INVITE with replaces header, a SIP PUBLISH message, and a SIP NOTIFY message and further comprising:

receiving, at the SBC, the second message;

retrieving the unique identifier for the communication session between the plurality of communication devices from the second message;

identifying the media stream of a communication session between the plurality of communication devices based on the unique identifier; and

in response to identifying the media stream between the plurality of communication devices based on the unique identifier, sending the media stream to the first media recorder.

4. The method of claim 1, further comprising:

recording the media stream received at the first media recorder.

5. The method of claim 1, wherein determining that the second media recorder is unable to record the media stream comprises at least one of:

receiving a third message from the second media recorder that the second media recorder is unable to record the media stream; and

not receiving a response from the second media recorder.

6. The method of claim 5, wherein the third message is at least one of a SIP NOTIFY and a SIP PUBLISH.

7. The method of claim 1, wherein determining that the second media recorder is unable to record the media stream is based on at least one of:

the second media recorder failing, the second media recorder not having enough media space, the second recorder no longer receiving the media stream, and a network failure.

8. The method of claim 1, wherein the first message is at least one of a SIP NOTIFY message and a SIP PUBLISH message.

9. The method of claim 1, further comprising:

establishing, by the first media recorder, a communication session with the second media recorder;

downloading, by the first media recorder, a portion of the media stream that was recorded by the second media recorder; and

compiling a recording of the media stream using the portion of the media stream that was recorded by the second media recorder and a portion of the media stream recorded by the first media recorder.

10. A first media recorder comprising:

a user agent configured to receive a first message indicating that a second media recorder is either recording a media stream of a communication session between a plurality of communication devices, receiving a media stream of the communication session between the plurality of communication devices, or going to start receiving the media steam of the communication session between the plurality of communication devices, wherein the first message includes a unique identifier for the communication session between the plurality of communication devices, wherein the user agent is further configured to send a second message, to a Session Border Controller (SBC), that includes the unique identifier for the communication session between the plurality of communication devices in response to determining that the second media recorder is unable to continue recording the media stream; and

a media recording application configured to determine that the second media recorder is unable to continue recording the media stream and receive the media stream.

11. The first media recorder of claim 10, wherein the unique identifier is at least one of a Global Session Identifier (GSID) and a Universal Call Identifier (UCID).

12. The first media recorder of claim 10, wherein the second message is a one of a Session Initiation Protocol (SIP) INVITE message, a SIP INVITE with replaces header message, a SIP PUBLISH message, and a SIP NOTIFY message and further comprising further comprising:

the SBC configured to receive the second message, retrieve the unique identifier for the communication session between the plurality of communication devices from the second message, identify the media stream of a communication session between the plurality of communication devices based on the unique identifier, and in response to identifying the media stream between the plurality of communication devices based on the unique identifier, send the media stream to the first media recorder.

13. The first media recorder of claim 10, wherein the first media recorder is further configured to record the media stream received at the first media recorder.

14. The first media recorder of claim 10, wherein determining that the second media recorder is unable to record the media stream comprises at least one of:

receiving a third message from the second media recorder that the second media recorder is unable to record the media stream; and

not receiving a response from the second media recorder.

15. The first media recorder of claim 14, wherein the third message is at least one of a SIP NOTIFY and a SIP PUBLISH.

16. The first media recorder of claim 10, wherein determining that the second media recorder is unable to record the media stream is based on at least one of:

the second media recorder failing, the second media recorder not having enough media space, the second recorder no longer receiving the media stream, and a network failure.

17. The first media recorder of claim 10, wherein the first message is at least one of a SIP NOTIFY message and a SIP PUBLISH message.

18. The first media recorder of claim 10, wherein the first media recorder is further configured to:

establishing a communication session with the second media recorder, download a portion of the media stream that was recorded by the second media recorder, and compile a recording of the media stream using the portion of the media stream that was recorded by the second media recorder and a portion of the media stream recorded by the first media recorder.

19. A method comprising:

receiving, at a first media recorder, a first message indicating that a second media recorder is either recording a media stream of a communication session between a plurality of communication devices, receiving a media stream of the communication session between the plurality of communication devices, or going to start receiving the media steam of the communication session between the plurality of communication devices, wherein the first message includes a dialog identifier for a communication session between the second media recorder and a Session Border Controller (SBC);

determining that the second media recorder is unable to continue recording the media stream;

in response to determining that the second media recorder is unable to continue recording the media stream, sending a second message, to the SBC, that includes the dialog identifier for the communication session between the second media recorder and the SBC; and

receiving, at the first media recorder, the media stream.

20. The method of claim 19, wherein the second message is one of a Session Initiation Protocol (SIP) INVITE message, a SIP INVITE with replaces header, a SIP PUBLISH message, and a SIP NOTIFY message.