US 9,071,684 B2Granted

Media forking

AssigneeCisco Technology, Inc.

InventorsJanet Helen Byron, Mohammed Taher Shaikh, Vipin Palawat, Paul Antinori, Mohanan Chalilputhenpurayil, Rashad Azhar

Life of this patent

Estimating the term…

patentgrep

Loading patent…

Abstract

In an example embodiment, a Voice over IP (VoIP) system that provides for media forking at the caller's (ingress) gateway. The gateway receives data with a first address on a recording server for sending forked caller stream media and a second address on the recording server for sending forked called party stream media. The gateway sends forked media from the caller stream to the first address and forked media from the called party media to the second address. This provides a recording from the caller's perspective. By using this technique, the recording can include for example call transfer data and interactive voice response (IVR) data.

Claims30

Dependent claims

An apparatus, comprising:

an interface configured to send and receive data;
and
logic coupled with the interface;
wherein the logic is configured to receive a Session Initiation Protocol (SIP) INVITE message via the interface from an ingress gateway to establish a call between an associated caller device operatively coupled with the ingress gateway and an associated called party device operatively coupled with the apparatus;
wherein the logic selectively forwards a new call request to intelligent contact management logic responsive to receiving the SIP INVITE message;
wherein the logic is configured to receive data from the intelligent contact management logic to connect a call between the associated caller device and the associated called party device, the data from the intelligent contact management logic further comprising data with instructions to record the call;
wherein the logic is responsive to the data with instructions to record the call to select a recording server;
wherein the logic is responsive to selecting a selected recording server to send two SIP INVITE messages to the selected recording server via the interface, the first SIP INVITE message requesting a first address for sending a near-end caller stream generated by the associated caller device for recording a near-end caller stream at the first address of the selected recording server and the second SIP INVITE message requesting a second address for sending a far-end called party stream generated by the associated called party device for recording the far-end called party stream at the second address of the selected recording server;
and
wherein the logic is responsive to receiving the first and second addresses for the near-end and far-end streams respectively to send a SIP RE-INVITE message via the interface to the ingress gateway for forking and replicating at the ingress gateway the caller and called party streams for recording at the selected recording server respectively at the first and second addresses, wherein the SIP RE-INVITE message comprises three Session Description Protocol (SDP) m-lines, the first m-line comprising data representative of the called party SDP data, the second m-line comprising an Internet Protocol (IP) address, port and codec for recording the caller stream and the third m-line comprises an IP address, port and codec for recording the called party stream.

7 more elements

Logic encoded in a non-transitory, tangible computer readable medium for execution by an associated processor, and when executed operable to:

receive a Session Initiation Protocol (SIP) INVITE message via an interface from an ingress gateway to establish a call between an associated caller device operatively coupled with the ingress gateway and an associated called party device;
forward a new call request to intelligent contact management logic responsive to receiving the SIP INVITE message;
receive data from the intelligent contact management logic to connect a call between the associated caller device and the associated called party device, the data from the intelligent contact management logic further comprising data with instructions to record the call;
select a recording server responsive to the data with instructions to record the call;
responsive to selecting a selected recording server, send two SIP INVITE messages to the selected recording server via the interface, the first SIP INVITE message requesting a first address for sending a near-end caller stream generated by the associated caller device for recording a near-end caller stream at the first address of the selected recording server and the second SIP INVITE message requesting a second address for sending a far-end called party stream generated by the associated called party device for recording the far-end called party stream at the second address of the selected recording server;
and
responsive to receiving the first and second addresses for the near-end and far-end streams respectively, send a SIP RE-INVITE message via the interface to the ingress gateway for forking and replicating at the ingress gateway the caller and called party streams for recording at the selected recording server respectively at the first and second addresses, wherein the SIP RE-INVITE message comprises three Session Description Protocol (SDP) m-lines, the first m-line comprising data representative of the called party SDP data, the second m-line comprising an Internet Protocol (IP) address, port and codec for recording the caller stream and the third m-line comprises an IP address, port and codec for recording the called party stream.

4 more elements

A method, comprising:

receiving a Session Initiation Protocol (SIP) INVITE message via an interface from an ingress gateway to establish a call between an associated caller device operatively coupled with the ingress gateway and an associated called party device;
forwarding a new call request to intelligent contact management logic responsive to receiving the SIP INVITE message;
receiving data from the intelligent contact management logic to connect a call between the associated caller device and the associated called party device, the data from the intelligent contact management logic further comprising data with instructions to record the call;
selecting a recording server responsive to the data with instructions to record the call;
responsive to selecting a selected recording server, sending two SIP INVITE messages to the selected recording server via the interface, the first SIP INVITE message requesting a first address for sending a near-end caller stream generated by the associated caller device for recording a near-end caller stream at the first address of the selected recording server and the second SIP INVITE message requesting a second address for sending a far-end called party stream generated by the associated called party device for recording the far-end called party stream at the second address of the selected recording server;
and
responsive to receiving the first and second addresses for the near-end and far-end streams respectively, sending a SIP RE-INVITE message via the interface to the ingress gateway for forking and replicating at the ingress gateway the caller and called party streams for recording at the selected recording server respectively at the first and second addresses, wherein the SIP RE-INVITE message comprises three Session Description Protocol (SDP) m-lines, the first m-line comprising data representative of the called party SDP data, the second m-line comprising an Internet Protocol (IP) address, port and codec for recording the caller stream and the third m-line comprises an IP address, port and codec for recording the called party stream.

4 more elements

Dependencies are inferred from the claim text.

Facts

Application: 12/620,166Filed 17 Nov 2009
Published: US 2011/0116492 A119 May 2011
Granted: 30 Jun 2015
Term ends: Not estimatedThe source records don’t support an estimate.

Classification14 codes

H04M 3/42221
Systems providing special services or facilities to subscribers: conversation recording systems
H04L 65/103
Media gateways: in the network
H04L 65/1063
Architectures or entities: application servers providing network services
H04L 65/1094
In-session procedures: inter-user-equipment sessions transfer or sharing