Abstract:
A method for analysing performance of a media recording system in a telecommunications network comprising the steps of selecting an extension within a telecommunications network, the extension capable of exchanging communication media, designating a time period within which communication records for the extension should be analysed, receiving communications data for the network extension, the communications data comprising data associated with communications involving the extension with the time period, receiving media data for the network extension, the media data comprising data associated with recorded media content of communications involving the extension within the time period, comparing the communications data with the media data to determine the performance of the communications recording system.

Description:
BACKGROUND 
       [0001]    In recent years, regulations have required various business segments, finance, health care, emergency services, insurance, financial trading and others to record all voice calls made or received. Although these businesses make every effort to be compliant, in some cases the call quality, call recording, or some other unforeseen event causes the recording to fail unbeknownst to the business, particularly the case when the voice calls and recording are occurring in the highly complex VoIP environment. This inadvertent missed recording can result in severe fines and penalties when uncovered during an audit. 
       SUMMARY OF THE INVENTION 
       [0002]    Embodiments of the invention provide a call analysis centre that monitors and reports on IPT and call recording systems to protect the business against events where calls are being made but the associated call recordings are not being made. Embodiments of the invention protect and inform the business in the event of:
       Voice Recorder status and issues threatening call recording   PBX status and issues threatening call recording   Network status and issues threatening call recording       
 
         [0006]    Embodiments of the Invention sit atop both the PBX and Voice Recorder, monitoring to assess the call recording metrics from both entities. 
         [0007]    Features 
         [0008]    The embodiment of the invention has the following features:
       Alert per extension on recordings missing completely in a configurable, wall-clock aligned time bucket       
 
         [0010]    Future embodiments of the invention will have the following features: 
         [0011]    Daily Check Feature 
         [0012]    Are the necessary resources available to perform call recording successfully?
       Disk space   Processing power   Necessary software   Necessary firmware/hardware       
 
         [0017]    Call in Progress (In Flight) Feature
       Count of voice streams valid   Mean Opinion Score (MOS) is adequate (e.g. &gt;3.4)       
 
         [0020]    Call Complete Feature
       Verify Voice Recorder media created and of expected size and duration       
 
         [0022]    Call Replay Feature
       Is the MOS adequate   Random replay function to ensure logged calls still have associated and proper media   Analysis of media content to ensure valid audio recording is present in the call recording system       
 
         [0026]    Abandon Feature
       Forced termination of calls failing checks   “Whisper” to business concern end-point with suggested or delayed termination   Alarm but proceed (e.g. emergency calls)   Role dependent call abandonment functionality       
 
         [0031]    Reporting Feature
       Report all recorded calls with appropriate metrics   Call abandonment analysis reports-probable cause and recommended actions   Configurable reports based on roles   Alarm reports   Configurable reporting mechanisms (text, phone, document, notifications)       
 
         [0037]    Cradle to Grave Feature
       Trace a call from when it starts to when it stops, including showing all routed devices, voice and signaling paths and recording functionality.       
 
         [0039]    In a first aspect the invention provides a method for analysing performance of a media recording system in a telecommunications network comprising the steps of: 
         [0040]    selecting an extension within a telecommunications network, the extension capable of exchanging communication media; 
         [0041]    designating a time period within which communication records for the extension should be analysed; 
         [0042]    receiving communications data for the network extension, the communications data comprising data associated with communications involving the extension with the time period; 
         [0043]    receiving media data for the network extension, the media data comprising data associated with recorded media content of communications involving the extension within the time period; and 
         [0044]    comparing the communications data with the media data to determine the performance of the communications recording system. 
         [0045]    Embodiments of the invention comprise the further steps of: 
         [0046]    receiving rules defining whether a communication should be recorded; and 
         [0047]    applying rules to the communications data to create filtered communications data, the filtered communications data associated with communications which should have been recorded; 
         [0048]    wherein the filtered communications data is compared with the media data. 
         [0049]    In embodiments of the invention the step of comparing comprises the steps of matching the communications data to the media data to identify communications data corresponding to recorded media content. 
         [0050]    In embodiment of the invention communications data includes at least one of the following: 
         [0051]    ANI; 
         [0052]    DNIS; 
         [0053]    start time of communication; 
         [0054]    end time of communication: 
         [0055]    duration of communication; 
         [0056]    extension number of parties engaged in the communication; 
         [0057]    time of communication; 
         [0058]    calling extension; 
         [0059]    receiving extension; 
         [0060]    recorder ID; 
         [0061]    call ID; 
         [0062]    location of participants in communication. 
         [0063]    An embodiment of the invention comprises the step of: 
         [0064]    analysing the communications data to identify a communications scenario including a plurality of communications data; 
         [0065]    calculating an expected number of media recordings from the analysed communications data; and 
         [0066]    wherein the step of comparing the communications data with the media data compares the expected number of media recordings with media data. 
         [0067]    In an embodiment of the invention communications scenarios include at least one of: call transfers; and, 
         [0068]    multiparty calls. 
         [0069]    In an embodiment of the invention calls started within a predetermined time of the time interval are disregarded. 
         [0070]    In an embodiment of the invention communications data relating to communications having a duration below a predefined time period are discarded. 
         [0071]    In an embodiment of the invention the performance of the communications recording system is determined on whether the number of expected media recordings matches the number or media records. 
         [0072]    In an embodiment of the invention the step of triggering an alert in dependence on the performance of the media recording system. 
         [0073]    In an embodiment of the invention the extension is associated with a communications device. 
         [0074]    In an embodiment a plurality of extensions are associated with a communications device. 
         [0075]    In an embodiment the communication is an audio communication. 
         [0076]    In an embodiment the communication media comprises speech based audio streams. 
         [0077]    In a second aspect the invention provides a call management system comprising: 
         [0078]    a call processing system configured to connect calls within a communications network; 
         [0079]    a call recording system configured to record call media associated with connected calls within the communications network; 
         [0080]    a first rules database comprising criteria for selecting a first set of calls to be recorded, the first rules database associated with the call processing system; 
         [0081]    a second rules database comprising criteria for selecting a second set calls to be recorded, the second rules database associated with the call recording system; 
         [0082]    an analysis system configured to compare the criteria of the first and second rules databases and determine whether the first set of calls matches the second set of calls. 
         [0083]    In an embodiment the rules of the first and second rules database specify that calls should be recorded in dependence on at least one of: 
         [0084]    time of communication; 
         [0085]    calling party extension; 
         [0086]    receiving party extension. 
         [0087]    In a third aspect the invention provides a method for recording communications on a communications network comprising the steps of: 
         [0088]    receiving a request to connect a communication across the communications network at a call processing system; 
         [0089]    determining whether the communication should be recorded; 
         [0090]    instructing a recording system to record the call in dependence on the determination. 
         [0091]    In a fourth aspect the invention provides a system for analysing performance of a media recording system in a telecommunications network comprising: 
         [0092]    processor for selecting an extension within a telecommunications network, the extension capable of exchanging communication media; 
         [0093]    processor for designating a time period within which communication records for the extension should be analysed; 
         [0094]    receiver for receiving communications data for the network extension, the communications data comprising data associated with communications involving the extension with the time period; 
         [0095]    receiver for receiving media data for the network extension, the media data comprising data associated with recorded media content of communications involving the extension within the time period; 
         [0096]    matching engine for comparing the communications data with the media data to determine the performance of the communications recording system. 
         [0097]    An embodiment comprises: 
         [0098]    memory storing rules defining whether a communication should be recorded; and data filter applying rules to the communications data to create filtered communications data, the filtered communications data associated with communications which should have been recorded; 
         [0099]    wherein the filtered communications data is compared with the media data. 
         [0100]    In an embodiment the step of comparing is performed by the matching engine matching the communications data to the media data to identify communications data corresponding to recorded media content. 
         [0101]    In an embodiment communications data includes at least one of the following: 
         [0102]    ANI; 
         [0103]    DNIS; 
         [0104]    start time of communication; 
         [0105]    end time of communication: 
         [0106]    duration of communication; 
         [0107]    extension number of parties engaged in the communication; 
         [0108]    calling extension; 
         [0109]    receiving extension; 
         [0110]    recorder ID; 
         [0111]    call ID; 
         [0112]    location of participants in communication. 
         [0113]    An embodiment comprises a processor for analysing the communications data to identify a communications scenario including a plurality of communications data and calculating an expected number of media recordings from the analysed communications data; 
         [0114]    wherein the step of comparing the communications data with the media data compares the expected number of media recordings with media data. 
         [0115]    In an embodiment communications scenarios include at least one of: 
         [0116]    call transfers; and, 
         [0117]    multiparty calls. 
         [0118]    In an embodiment calls connected within a predetermined time of the time interval are disregarded. 
         [0119]    In an embodiment communications data relating to communications having a duration below a predefined time period are discarded. 
         [0120]    In an embodiment the performance of the communications recording system is determined on whether the number of expected media recordings matches the number or media records. 
         [0121]    An embodiment comprises an alert means to trigger an alert in dependence on the performance of the media recording system. 
         [0122]    In an embodiment the extension is associated with a communications device. 
         [0123]    In an embodiment a plurality of extensions are associated with a communications device. 
         [0124]    In an embodiment the communication is an audio communication. 
         [0125]    In an embodiment the communication media comprises speech based audio streams. 
         [0126]    In a fifth aspect the invention provides a method for verifying the configuration of a call recording system having a call processing system configured to connect calls within a communications network and a call recording system configured to record call media associated with connected calls within the communications network, comprising the steps of: 
         [0127]    retrieving a first rules database comprising criteria for selecting a first set of calls to be recorded, the first rules database associated with the call processing system; 
         [0128]    retrieving a second rules database comprising criteria for selecting a second set calls to be recorded, the second rules database associated with the call recording system; 
         [0129]    comparing the criteria of the first and second rules databases and determining whether the first set of calls matches the second set of calls. 
         [0130]    In an embodiment the rules of the first and second rules database specify that calls should be recorded in dependence on at least one of: 
         [0131]    time of communication; 
         [0132]    calling party extension; 
         [0133]    receiving party extension. 
         [0134]    In a sixth aspect the invention provides a system for routing communications on a communications network comprising: 
         [0135]    communications routing system configured to receive a request to connect a communication across the communications network at a call processing system; 
         [0136]    processor for determining whether the communication should be recorded; 
         [0137]    transmitter for transmitting and instruction to a recording system to record the call in dependence on the determination. 
         [0138]    In a seventh aspect the invention provides a system for recording communications on a communications network comprising; 
         [0139]    communications recording system, the communications recording system comprising; 
         [0140]    a receiver for receiving an instruction to record a communication; 
         [0141]    processor for determining whether the communication is required to be recorded in dependence on recording rules; and 
         [0142]    recorder for recording the communication in dependence on the communication being required to be recorded. 
         [0143]    In a seventh aspect the invention provides a method for analysing communication records in a telecommunication system comprising the steps of: 
         [0144]    receiving across a telecommunications network communication records data, the communication records data comprising data associated with communications involving predetermined communications devices within a designated time period; 
         [0145]    receiving across a telecommunications network media recordings data, the media recordings data comprising data associated with media recordings from communications involving the predetermined communications devices within the designated time period; 
         [0146]    comparing the communication records data with the media recordings data; and, 
         [0147]    signalling an alert in dependence on the comparison. 
         [0148]    In an embodiment the communication records data identifies whether the predetermined communications device engaged in a communication during the designated time period. 
         [0149]    In an embodiment an alert is signalled if, during the designated time period, the communication records data identifies at least one communication involving the predetermined communications device and the media recordings data comprises no media. 
         [0150]    In an eighth aspect the invention provides a system for analysing communication records in a telecommunication system comprising: 
         [0151]    receiver for receiving network communication records data across a telecommunications network, the communication records data comprising data associated with communications involving predetermined communications devices within a designated time period; 
         [0152]    receiver for receiving media recordings data across a telecommunications network, the media recordings data comprising data associated with media recordings from communications involving the predetermined communications devices within the designated time period; 
         [0153]    processor for comparing the communication records data with the media recordings data; and, 
         [0154]    means for signalling an alert in dependence on the comparison. 
         [0155]    In an embodiment the communication records data identifies whether the predetermined communications device engaged in a communication during the designated time period. 
         [0156]    In an embodiment an alert is signalled if, during the designated time period, the communication records data identifies at least one communication involving the predetermined communications device and the media recordings data comprises no media. 
         [0157]    Embodiments of the invention comprise a transmitter for requesting network media recordings data. 
         [0158]    Embodiments of the invention comprise the step of requesting network media recordings data. 
     
    
     
       BRIEF DESCRIPTION OF THE FIGURES 
         [0159]    Preferred forms of the invention are now described by way of example only with reference to the accompanying figures in which: 
           [0160]      FIG. 1  illustrates an architecture of a telephony system; 
           [0161]      FIG. 2  illustrates an architecture of a telephony system; 
           [0162]      FIG. 3  is a flow diagram showing steps performed by an embodiment; 
           [0163]      FIG. 4  illustrates data captured from call recording records; 
           [0164]      FIG. 5  illustrates a first call scenario; 
           [0165]      FIG. 6  illustrates a second call scenario; 
           [0166]      FIG. 7  illustrates a third call scenario. 
       
    
    
     DETAILED DESCRIPTION 
       [0167]    Overview 
         [0168]    Embodiments of the present invention relate to recording systems for recording communications in a communication network. Preferably the network is a telephone network recording audio data relating to telephone calls. 
         [0169]    Embodiments of the invention operate in a telephone network in which calls to certain extension numbers, devices or individuals are required to be recorded, for example due to regulatory requirements. For example, embodiments of the invention may be integrated onto the telephone network of a financial services company, in which calls to and from certain individuals are required to be recorded. Typically, banking regulations require calls involving brokers or traders engaging with external third parties to be recorded. 
         [0170]    In some telephone systems not all calls are required to be recorded. Embodiments of the invention implement rules to determine whether or not a call should be, or should have been, recorded. In some environments, only a subset of calls are required to be recorded for compliance or regulatory purposes, this may be defined by geographical site or by business unit. Embodiments of the invention map site or business units to a set of extension numbers, given by a dial plan number mapping. Rules for recording may include white lists and black lists to define extension numbers to include and exclude from call recording assurance alerting. Embodiments of the invention enable the system to be user configurable. 
         [0171]    Embodiments of the invention capture call detail records associated with the call, for example ANI (Automatic Number Identification, DNIS (Dialled Number Identification Service), start time, call duration, extension number, agent ID, recorder ID, call ID, UCID (Universal Call ID), site ID. Rules are applied to the call data to determine whether or not a call is required to be recorded. Rules may be configured for the specific network and include recording requirements based on individual extension number, device ID, business area and time of day. Call records relating to calls which should be recorded are identified. 
         [0172]    In embodiments call recording is implemented in a call recording system. The call recording system creates a media file and a session record for each recorded call. Embodiments of the invention determine whether or not a call should be recorded based on the rules. In further embodiments, all calls may be recorded. 
         [0173]    Embodiments of the invention include a call matching system which receives call records for calls which should have been recorded. The call matching system interrogates the call recording system and matches the session records with the call records. Various matching rules are implemented to provide visibility of which calls are recorded successfully and those which are not recorded successfully. In the event that a session record does not exist for a call which should have been recorded the system raise an alarm. 
         [0174]    Embodiments of the invention provide alerting on missed call recordings and other critical failure points in call recording integration. This provides the ability to automate auditing and compliance activities within an enterprise, for example contact centre business or trading floor. 
         [0175]    The call matching system includes a range of system exclusion rules that are designed to exclude internal system transaction and avoid false positive alerts. Examples include call detail records that are utilized for record events to the call recording system. Other call recording records can be excluded, including zero duration calls and short duration calls based on a configurable parameter set in the call recording system. 
         [0176]    Multi-Line Support for Call Recording Assurance 
         [0177]    In embodiments, the call recording system can handle recording of multi-line phones, such as those with a primary ACD line and a secondary private line. Such phones enable multiple extension lines to be directed to a single phone unit. The call matching algorithm handles derivation of complex call scenarios using primary and secondary lines on a single phone. This is required to handle complex call types, including hold, transfer and conference scenarios. This mapping mechanism can be derived. 
         [0178]    Embodiments of the invention work across a number of different call recording integration models including:
       Phone side recording, in which calls are recorded at the device;       
 
         [0180]    This recording model forks the media from each agent phone in the environment.
       Trunk side recording, including TDM/IP based systems       
 
         [0182]    This recording model uses a physical network tap on the TDM to record the information trunk side.
       Passive TAP recording,       
 
         [0184]    This recording model copies the network traffic of the Network switch to the recorder.
       SIP based recording systems, including the use of SIPREC standards       
 
         [0186]    This recording model forks the media at the Session Border Controller 
         [0187]    Embodiments of the call matching system map calls involving each extension into individual configurable time buckets for alerting. In complex call scenarios, for example conference calls, call transfer and call holding, multiple call records are created and there is not a 1-1 match between call detail records and call session records. 
         [0188]    The bucket size is a configurable parameter, based on the underlying delays of the call recording session recording as well as the call generation system producing call detail records. Embodiments handle complex scenarios including multi-line support, inbound calls, followed by a series of holds, transfers and conferences. 
         [0189]    Embodiments of the invention are able to group complex call scenarios together, and only alert on the complete transaction and not provide false positive alerts on partial results within the call types. 
         [0190]    Embodiments of the invention operate in systems where calls are recorded at different locations in the network. Embodiments analyse different call scenarios, for example when calls are placed on hold, calls are rerouted, or when a conference is established to include more than two parties. 
         [0191]    Worksheet Feature 
         [0192]    Embodiments of the invention detect issues with badly configured integrated routing equipment. This can be utilized to automatically detect business rule configuration mismatches between the call recording system and the call processing system. Such errors could be present due to manual installation errors that cause call recording to fail in this environment. This allows automatic determination of configuration mis-matches between the call recording system and the call processing system. 
         [0193]    End to End Monitoring of Critical Integration Points 
         [0194]    Embodiments of the invention can be utilized to monitor critical application level failures in the call recording system, this can be integrated with alerts which can be utilized to provide alerts on the key integration links between the systems. 
         [0195]    The critical integration points include interaction with the PBX, ACD or Turret system, as well as the geographical distribution of call recording systems into data centre and site architectural components respectively. 
         [0196]    Voice Quality Feature 
         [0197]    Embodiments of the system monitor the call session data records and alert when in- flight Mean opinion score (MOS) score to the call recording system is inadequate. This feature can be important for centralized call recording models that require longer IP transport of the RTP media involved in the call, with the chance of introducing packet loss, jitter or latency which will degrade the quality of the recording. 
         [0198]    Cradle to Grave Feature 
         [0199]    This feature traces a call from when it starts to when it stops, including showing all routed devices, end to end voice and signalling paths and recording functionality across session border controllers (SBCs), PBX/ACD devices all the way to the end phone or agent device. This feature can be used to correlate which devices have been involved in calls without valid call recordings. 
         [0200]    Active Call Recording Test 
         [0201]    In addition to passive call recording capability, embodiments of the invention incorporate active call recording to validate critical parameters of the call including:
       Whether valid CTI attached data is available for the call;   Whether the file is of the correct file size and contains valid audio recording sample.       
 
         [0204]    This can be done utilizing the passive data feed from the call processing system. This can be utilized as an automatic mechanism for providing validation, in combination with the active call recordings described earlier. 
         [0205]    Archiving Validation Test 
         [0206]    Embodiments of the invention provide the capability to validate whether there is a valid media archive for a sample call scenario. This can be done by validating the file archive is valid off the storage area network (SAN) or content addressable storage system(s) utilized by the call recording system, such as NetApp or EMC Centura. This archiving validation can utilize old call sample data to identify calls to validate against the archiving system. 
         [0207]    Description of the Figures 
         [0208]    An embodiment of the invention is now described with reference to the accompanying drawings.  FIG. 1  illustrates the signalling and media links between components of the architecture of a telephony network. At step  1  an incoming call arrives at SBC  210 . 
         [0209]    On receipt of the call at step  2  the SBC signals the PBX. The signalling includes details such as the destination party. PBX  220  identifies the target communication device and signals the target communications device  230  at step  3  that it should establish a media connection to SBC  210 . Communication device  230  signals back to the PBX at step  4  and at step  5  the PBX sends signalling back to the SBC  210  to enable media connection to communications device  230 . At step  6  communications device  230  and SBC  210  establish a media connection. After completion of step  6  the external caller is connected with communications device  230  and the parties can communicate. 
         [0210]    The PBX is connected to memory  240  to store information about calls. The information is stored as a Call Detail Record (CDR). The CRD includes various information relating to the call including: ANI, DNIS, Start time, End time, Call duration, Extension number of the party engaged in the call, agent ID (for example if an employee is registered with the physical device), Recorder ID, Call ID, UCID, Site ID. 
         [0211]    The telephony network architecture can be extended to include recording components for recording and storing communication media from telephone calls.  FIG. 2  illustrates a telephone network including a call analysis centre  340 , call routing architecture  320  and recording system  360 . Call routing architecture  320  includes private branch exchange (PBX)  311 , Session Border Controller (SBC)  317 , routing gateway  315  and communications device  312 . Storage device  360  includes media recorder  362 , database  361  and media archive  313  as well as controller  363 . 
         [0212]    Media recorder  362  within recording system  360  can receive media streams for recording from SBC  317 , gateway  315  and communications device  312 . PBX  311  and SBC  317  can signal controller  363  to indicate when a media stream should be recorded. Controller  363  controls when media recorder  362  records the incoming media streams. Recorded media is stored in media archive  313 . Details about the media file are stored in database  361  as session data records. Session data records include information relating to the call including details of the communication device, the media file and the time the file was created. In some cases, further information about the call is stored in in the session data record in database  361 . In some cases database  361  includes a link to the associated media file. The session metadata record may be stored as a separate file from the media file or may be stored as part of the media file, for example in the header. 
         [0213]    Call analysis centre  340  receives call detail records from PBX  311  relating to communications involving communication device  312 . 
         [0214]    Call analysis centre  340  pulls or receives session data records from database  361  and may pull copies of the recorded media from storage device  361 . The call analysis centre compares the call detail records from the PBX  311  with the session data records of the storage device  361  to determine whether calls are being correctly recorded. 
         [0215]    In the example of  FIG. 2 , rules relating to whether or not a call should be recorded can be implemented in the PBX  311 , SBC  317 , gateway  315  or device  312  and also in controller  363 . On receipt of an instruction to record a call, controller  363  can apply its business rules to the instruction to determine whether to record the call. In situations where the business rules of the call routing architecture are configured differently from those in the recording system  360 , the call routing system may identify a call to be recorded which is not identified for recording by the recording system  360 . In this situation the call recording system may apply its own rules and not record the call. The situation may arise, for example if the call recording system and the call routing architecture are provided by different vendors or when business rules in the call recording system and the call routing architecture have not been updated simultaneously. 
         [0216]    The system includes a matching engine for automatically detecting business rule configuration mismatches. The system compares the rules of the call recording system and the PBX, or call routing system. The system may be configured to compare the rules automatically at predefined time periods or may be triggered manually. This system is utilized for detecting inconsistencies with badly configured or integrated PBX/ACD/Turret equipment. This can be utilized to automatically detecting business rule configuration mismatches done manually by users and other issues that cause call recording to fail in this environment. This allows automatic determination of configuration mis-matches between the call recording system and the call processing system. 
         [0217]      FIG. 3  is a flow diagram showing the steps taken in a telephone network implementing an embodiment of the invention. The steps of  FIG. 3  are implemented in architecture of  FIG. 2 . At  410  call data is collected at the PBX or SBC. As discussed above, the call data can include multiple fields including ANI, DNIS, start time, call duration, extension number, agent ID, recorder ID, call ID, UCID, site ID. 
         [0218]    The business rules relating to recording requirements are loaded into PBX  311 /SBS  317 . Before call data is passed to call analysis centre  340  it is filtered. As discussed above there are several options for identifying whether or not a call should be recorded. The first filter run on the data is to identify whether the extension number belongs to an agent or a device identified on a whitelist or a blacklist. Whitelists identify extensions which are to be recorded; blacklists identify extensions which are not to be recorded. 
         [0219]    Blacklists and whitelists are effective when regulatory requirements apply generically across business units or geographical sites and different extension ranges are applied to those different business units or geographical sites, given by a dial plan number mapping. In an example where calls involving financial traders are required to be recorded, if the traders on a trading floor of a bank are all provided with extension numbers starting with 2 0, then a whitelist is created identifying all extension numbers starting with digits 2 0. 
         [0220]    Continuing with the example, if regulations require that certain business units within the bank are generally exempt from being recorded, blacklists can be created identifying extension ranges excluded from recording. For example if the back office settlements team are not required to have their calls recorded by regulation and that business unit has the extension 3 0 then all extensions starting with extension 3 0 can be included on a blacklist and automatically filtered from being recorded. 
         [0221]    Embodiments of the system are designed to enable whitelists and blacklists to be individually configured such that any number can be included, and not just those within specific extension ranges. 
         [0222]    At  430  additional business rules are applied to the call data. Business rules can operate to filter calls based on other call related parameters. In an example, if trading floor phones are only required to be recorded during market hours, a call received between 0800 and 1600 the call is required to be recoded. However, a call received between 1600 and 0800 it is not required to be recorded. 
         [0223]    Further business rules, for example, based on calling party, direction of the call, duration of the call can be applied. The rules can be configured specifically for the requirements of the network. 
         [0224]    Call detail records are transmitted to the call analysis centre  340 . The data is filtered so as only to include call data records of calls which are required to be recorded. In further embodiments all call detail records may be transmitted to the call analysis centre and filtered at the call analysis centre. Alternatively, the call detail records may be filtered at the routing architecture and labelled before being transmitted. The data may be requested by the call analysis centre  340  or transmitted to the call analysis centre  340  periodically. 
         [0225]    Call analysis centre includes processors for executing a call matching algorithm. The algorithm initially applies further system exclusion rules that are designed to exclude internal system transaction and avoid false positive alerts. Examples include call detail records that are utilized for record events to the call recording system. There are also other call recording records excluded, such as zero duration calls and short duration calls based on a configurable parameter set in the call recording system. 
         [0226]    Example of System for Executing Call Analysis 
         [0227]    Call analysis centre  340  obtains call data records and session data records from the PBXs and recording systems via remote application layer interfaces. 
         [0228]    Matching Algorithm 
         [0229]    In an embodiment filtered call information in the form of CDRs is retrieved by the call analysis centre from the PBX. The CDR may be retrieved upon completion of the call or may be retrieved periodically and stored in-memory. Data related to recorded media is pulled from database  361  periodically or at regular time intervals and stored in-memory. Preferably the system analyses specific time frames, buckets. The CDR data for the call and the recorded media includes at least the extension numbers engaged in the call, the duration of the call and the end time of the call. 
         [0230]    The call analysis centre compiles a list of call data relating to calls which should have been recorded in line rules implementing regulatory requirements at  450 . The call analysis centre  340  retrieves data from call recording system at  460  and compares the data of the CDR with the session record relating to the recorded media file for particular communication devices or extensions within the network. The system matches the CDR data with the session data records and flags any situations where the call detail records and session data records do not match. Additionally, the system can interrogate the session data record to determine whether all elements of a call are represented. 
         [0231]    The system is able to handle complex call scenarios in which multiple CDRs correspond to a single session record.  FIG. 4  shows a comparison of CDR and recording records for a communication device on agent extension 1. In  FIG. 4  calls from each extension are mapped into to individual configurable time buckets for alerting. This is due to the lack of a 1-1 match between call detail records and call recording systems, and the need to handle complex call scenarios which generate large numbers of individual session records. 
         [0232]    The bucket size is a configurable parameter, based on the underlying delays of the call recording session recording as well as the call generation system producing call detail records. 
         [0233]    In  FIG. 4  the comparison of session data records and call detail records is made using data at 15 minute wall-clock aligned intervals (buckets). The matching of calls and recordings is based on data taken from CDR records and recorded media records. Zero-duration CDRs and CDRs directed to the call recording devices are ignored, as well as CDR&#39;s with invalid ip addresses in source or destination fields. Each call and recording is assigned to a bucket based on their end time. 
         [0234]    In the first step, the call detail records are collected: 
         [0235]    Data Collection 
         [0236]    1. An extensionmapping (primary to secondary extension mapping) file is input; it is provided by the customer after running an SQL query. 
         [0237]    2. It is assumed that the string extension field (the Extension) in the data always contains the primary extension. 
         [0238]    3. For each recording row that comes in, a hashset of extension strings is created (HashSetExtensions) that is determined by: 
         [0000]    
       
         
               
               
               
             
           
               
                   
               
               
                   
                   
                 Extension in recording 
               
               
                   
                   
                 is not a primary extension 
               
               
                   
                 Extension in recording 
                 in extensionmapping 
               
               
                   
                 is a primary extension 
                 (we try to find the secondary 
               
               
                 Direction 
                 in extensionmapping 
                 extension ourselves) 
               
               
                   
               
             
             
               
                 0 (unknown) 
                 Extension + its 
                 If (Extension = Caller | | 
               
               
                   
                 secondary 
                 Extension = Callee): Extension 
               
               
                   
                 extensions from 
                 else Extension + Caller + Callee 
               
               
                   
                 extensionmapping 
               
               
                 1 (inbound) 
                 Extension + its 
                 If (Extension = Caller | | 
               
               
                   
                 secondary 
                 Extension = Callee): Extension 
               
               
                   
                 extensions from 
                 else Extension + Callee 
               
               
                   
                 extensionmapping 
               
               
                 2 (outbound 
                 Extension + its 
                 If (Extension = Caller | | 
               
               
                   
                 secondary 
                 Extension = Callee): Extension 
               
               
                   
                 extensions from 
                 else Extension + Caller 
               
               
                   
                 extensionmapping 
               
               
                 3 (internal) 
                 Extension + its 
                 If (Extension = Caller | | 
               
               
                   
                 secondary 
                 Extension = Callee): Extension 
               
               
                   
                 extensions from 
                 else Extension + Caller + Callee 
               
               
                   
                 extensionmapping 
               
               
                   
               
             
          
         
       
     
         [0239]    After the call data is collected, a number of requirements are included, for example: 
         [0240]    a. The recording must overlap, i.e. StopTime&gt;=ConnectTime and StartTime&lt;=DisconnectTime. 
         [0241]    b. If the call is inbound: find if there is any overlapping recording with a HashSetExtensions that contains the finalCalledParty (=the Extension that is being reported on). 
         [0242]    c. If the call is outbound: find if there is any overlapping recording with a HashSetExtensions that contains the callingParty (=the Extension that is being reported on). 
         [0243]    d. If the call is internal: 
         [0244]    i. Find if there is any overlapping recording with a HashSetExtensions that contains the finalCalledParty or the callingParty (these are the Extensions that are reported on) 
         [0245]    ii. Find if there is any overlapping recording with a HashSetExtensions that contains the finalCalledParty and find if there is any overlapping recording with a HashSetExtensions that contains the callingParty (these are the Extensions that are reported on) 
         [0246]    e. Update the status for finalCalledParty (inbound, internal) and/or callingParty (outbound, internal) extensions. 
         [0247]    For a certain bucket, for each agent extension (either destination or source, depending on whether the call type is inbound, outbound or internal) the system examines the number of CDRs with endtime within the bucket (#A) and the number of recordings with endtime within the bucket (#B). If there are non-zero values for either #A or #B, the data is presented for this extension in this bucket. 
         [0248]      FIG. 4  illustrates some complex call scenarios. A call can have one or more CDR&#39;s and one or more recordings, depending on the call scenario. Pictured are 5 calls A, B, C, D and E for agent extension 1 (each rectangle is a call for extension 1). 
         [0249]    In the example of  FIG. 4  an alert is generated if the number of valid CDR records is nonzero and the number of media records is zero. Because call recordings may be delayed, the system only queries data with endtimes in the past. For example, at 15:21, if the last known recording&#39;s endtime is 15:06 for any extension, the call analysis centre only queries for at most the 14:45-15:00 bucket or earlier buckets, but not for the 15:00-15:15 bucket. The delay may depend on the call recording device (type, location), the location of the phone within the network and the call load. 
         [0250]    In call A, in the 14:30 to 14:45 bucket a single recording has been made associated with agent extension 1. During the same time period multiple CDRs have been recorded involving agent extension 1. In the example of  FIG. 4  a conference call was initiated including multiple parties to create the multiple parallel CDRs involving agent extension 1. In total 5 CDRs are recorded for agent extension 1 during call A. Each CDR relates to a separate component of the call, as if a separate call was initiated within the call. Since a media recording is present in the 14:30-14:45 bucket for agent extension 1, no alert is raised. 
         [0251]    In the 14:45 to 15:00 bucket, a single CDR is recorded. Two media recordings are made in the same time period. In call B the break in the media recordings could be due to the call being placed on hold. As discussed above with respect to  FIG. 2 , the PBX signals the controller to indicate when a recording should be started and stopped. In the example of  FIG. 4  media recordings at the media recorder  362  are paused when calls are placed on hold. Again, since a recording is present for the CDR in this bucket, no alert is raised by the system. 
         [0252]    The bucket 15:00 to 15:15 involves two calls involving agent extension 1 (calls C and D). Bucket 15:00-15:15 has 2 CDR&#39;s and 1 recordings. It will therefore not generate an alert. If call C was absent, an alert would be generated, which is not correct since all calls would have recordings (just not in the 15-min bucket under consideration). This problem is made less severe if the bucket size is selected to be large enough to have at least one other recording if everything is working properly. The choice of bucket size depends on how many calls are made and their duration. The above problem will occur most obviously in certain call scenarios, when starting a conference for instance, so that the call is split over multiple CDR&#39;s. 
         [0253]    For ‘normal’ calls, a similar boundary problem may exist if the recording stops just before or after the call finishes. The risk of these false alerts is mitigated by allowing a ‘tolerance’ time: the calls are taken in an exact 15-minute bucket, but the recordings in a slightly larger bucket, with a tolerance on either side of the 15-minute bucket. The tolerance is configurable and 2 seconds by default. 
         [0254]    The bucket 15:15 to 15:30 involves two calls, call D and call E. Bucket 15:15-15:30 has 2 CDR&#39;s and 1 recording. An alert will not be generated, although there is a call without recording. If the problem is caused by misconfiguration, it would probably persist into the next bucket and it would alert on it in the next bucket (if there are calls being made). If it is an incident (only one call not recorded), no alert is raised on the incident, which is incorrect. 
         [0255]    In further embodiments the system may raise alerts if a particular call includes a CDR but no media recording. In such cases an alarm would be raised on the 15:15 to 15:30 data due to the lack of media recording for call E. These embodiments will also address the other problems mentioned above. 
         [0256]    In the example of  FIG. 4 , using the alert technique discussed above, for none of the time buckets an alert will be generated. 
         [0257]    Status 
         [0258]    After analysis, each bucket of each extension is given a status. The extension is determined by the finalCalledParty and/or the callingParty in the cdrs. Initially the status of an extension in a bucket is up. 
         [0259]    For each CDR with a disconnect time in the bucket: 
         [0260]    If a CDR has no matching recording:status of extension in bucket changes to: 
         [0000]    
       
         
               
               
               
               
             
           
               
                   
                   
               
               
                   
                 In white list 
                 In black list 
                 Status 
               
               
                   
                   
               
             
             
               
                   
                 x 
                 — 
                 0 (down) 
               
               
                   
                 x 
                 X 
                 3 (inblacklist) 
               
               
                   
                 — 
                 — 
                 2 (notinwhitelist) 
               
               
                   
                 — 
                 X 
                 2 (notinwhitelist) 
               
               
                   
                   
               
             
          
         
       
     
         [0261]    If the white list is empty or absent, all extensions are in the white list lithe black list is empty or absent, no extensions are in the black list 
         [0262]    Alerting 
         [0263]    An alert is raised for an extension if the status of the extension in a bucket is 0 (Down). The alert is cleared if in a later bucket the status &lt;&gt;0. If in all later buckets the status is still 0, we don&#39;t raise new alerts and the text of the alert does not change, so the original bucket in which the alert was raised is still in the alert text. 
         [0264]      FIGS. 5 to 7  illustrate examples of call scenarios. 
         [0265]    Call Transfer Scenario 
         [0266]      FIG. 5  shows the connections between extension numbers 50006 50004 and 50008 in a call transfer situation. The sequence is:
       1. Initial call between 50006 and 50004 at 10:40:54;   2. Consulting transfer (50004 tells 50008 that they are transferring the call. After talking they hang up.   3. Transfer complete (50006-50008)       
 
         [0270]    During the period of 10:42:54 to 10:45:00 50004 is connected to both 50006 and 50008. 
         [0271]    Times of the call timeline and recording timeline are not exactly overlayed every time since there can be time sync differences between systems which the system caters for. 
         [0272]    Conference Call Scenario 
         [0273]      FIG. 6  is for a PBX and call recording system conference call and shows the following sequence:
       1. At 05:08:00 a call is initiated between extensions 1012 and 8064.   2. At 05:10:09 a conference call is initiated between extensions 1012, 8064, 8074 across conference bridge CFB_2 (A separate data record is created for each participant with the conference bridge).   3. At 05:11:24 8064 leaves the conference and 8071 and 1012 are connected until 05:13:31.       
 
         [0277]    In this case extension 8071 is configured for recording. In the example of  FIG. 6  there is a short time delay (0.140 s) between signalling and the initiation of the instruction by the call recording system. 
         [0278]      FIG. 7  shows an inbound call transfer with multiline scenario 
         [0279]    This scenario is for an inbound call from 1012, which is received at 8070 put on hold, then a secondary line 8090 is used to make a call to another extension 8064. Finally a transfer is made to another extension 8081. The sequence is: 
         [0280]    1. Initial inbound call between 1012 and 8070 at 01:17:23; 
         [0281]    2. At 01:19:08 a call is established on second line between 8090 (Second line of phone with primary line 8070) and 8064. 
         [0282]    3. Call Transfer to 8081 at 01:22:02. 
         [0283]    In this case 8070 and 8081 are the extensions configured for recording. 
         [0284]    Embodiments of the Invention include the Following Features: 
         [0285]    Multi-Line Phones 
         [0286]    The call recording system can handle recording of multi-line phones, such as those with a primary ACD line and a secondary private line. There is a configurable mapping file that can be utilized to map primary and secondary phone lines. Multiple entries can be added to handle more than two lines on a single phone. The call matching algorithm handles derivation of complex call scenarios using primary and secondary lines on a single phone (as shown in the example of  FIG. 7  above. This is required to handle complex call types, including hold, transfer, conference scenarios. This mapping mechanism can be derived. 
         [0287]    Worksheet Feature 
         [0288]    As discussed above, in addition to analysing whether calls are being recorded correctly, embodiments of the invention automatically detect business rule configuration mismatches. The comparison is done between the call recording system and the PBX, or call routing system Worksheets are utilized for detecting issues with badly configured integrated PBX/ACD/Turret equipment. This can be utilized to automatically detecting business rule configuration mismatches done manually by users and other issues that cause call recording to fail in this environment. This allows automatic determination of configuration mis-matches between the call recording system and the call processing system. 
         [0289]    Daily Check Feature 
         [0290]    The system monitors performance of its components periodically. In particular, the system performs regular checks on whether it has the necessary resources available to perform call recording successfully, including trunk capacity, licenses, DSP utilization, port capacity, system performance (CPU, Disk, Memory) usage. The performance is compared against predefined performance parameters and if any components operate below the system requirements a signal is raised. 
         [0291]    Voice Quality Feature 
         [0292]    The data stored with the media file includes in-flight Mean opinion score (MOS) score to the call recording system is inadequate. This feature can be important for centralized call recording models that require longer IP transport of the RTP media involved in the call, with the chance of introducing packet loss, jitter or latency which will degrade the quality of the recording. 
         [0293]    End to end monitoring of critical integration points 
         [0294]    Call monitoring can be utilized to monitor critical application level failures in the call recording system, this can be integrated with alerts which can be utilized to provide alerts on the key integration links between the systems. 
         [0295]    The critical integration points include interaction with the PBX, ACD or Turret system, as well as the geographical distribution of call recording systems into data center and site architectural components respectively. 
         [0296]    Cradle to Grave Feature 
         [0297]    This feature traces a call from when it starts to when it stops, including showing all routed devices, end to end voice and signalling paths and recording functionality across session border controllers (SBCs), PBX/ACD devices all the way to the end phone or agent device. 
         [0298]    Reporting Feature
       Report all recorded calls with appropriate metrics   Call abandonment analysis reports-probable cause and recommended actions   Configurable reports based on roles   Alarm reports   Configurable reporting mechanisms (text, phone, document, notifications)       
 
         [0304]    Active call recording test—In addition to passive call recording capability, active call recording can be used to validate critical parameters of the call including:
       Whether valid CTI attached data is available for the call.   Whether the file is of the correct file size and contains valid audio recording sample.       
 
         [0307]    This can be done utilizing the passive data feed from the call processing system. This can be utilized as an automatic mechanism for providing validation, in combination with the active call recordings described earlier. 
         [0308]    Archiving Validation Test 
         [0309]    This provides the capability to validate whether there is a valid media archive for a sample call scenario. This can be done by validating the file archive is valid off the storage area network (SAN) or content addressable storage system(s) utilized by the call recording system. This archiving validation can utilize old call sample data to identify calls to validate against the archiving system. 
         [0310]    It will be clear to those skilled in the art that embodiments of the present invention provide a system in which recorded call media files can be mapped to call data. Embodiments apply recording rules in call routing systems and call recording systems and determine whether calls have been correctly recorded. Further embodiments compare recording rules between call recording systems and call routing systems to identify configuration errors and inconsistencies. 
         [0311]    It will be clear to those skilled in the art that references to calls in the description and claims include communications including telephone calls or other audio calls or video calls.