<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/telrex-announces-callrex-release-35-voip-call-recording-solution.asp" />
  <link rel="self" type="application/atom+xml" href="http://blog.tmcnet.com/blog/tom-keating/atom.xml" />
  <id>tag:blog.tmcnet.com,2014:/blog/tom-keating//4/tag:blog.tmcnet.com,2007:/blog/tom-keating//4.31714-</id>
  <updated>2014-03-28T20:48:08Z</updated>
  <title>Comments for Telrex Announces CallRex Release 3.5 VoIP Call Recording solution</title>
  <subtitle>VoIP &amp; Gadgets blog - Latest news in VoIP &amp; gadgets, wireless, mobile phones, reviews, &amp; opinions</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.38</generator>
  <entry>
    <id>tag:blog.tmcnet.com,2007:/blog/tom-keating//4.31714</id>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/telrex-announces-callrex-release-35-voip-call-recording-solution.asp" />
    <link rel="service.edit" type="application/atom+xml" href="http://blog.tmcnet.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=31714" title="Telrex Announces CallRex Release 3.5 VoIP Call Recording solution" />
    <published>2007-01-22T16:55:22Z</published>
    <updated>2008-04-10T21:35:14Z</updated>
    <title>Telrex Announces CallRex Release 3.5 VoIP Call Recording solution</title>
    <summary>Telrex today announced CallRex Release 3.5, a business-class VoIP call recording and monitoring solution. For a round-up of VoIP call recording solutions, check out my article here. According to Telrex, the new release features a new distributed-services software architecture which...</summary>
    <author>
      <name>Tom Keating</name>
      <uri>http://blog.tmcnet.com/blog/tom-keating/</uri>
    </author>
    
    <category term="VoIP" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.tmcnet.com/blog/tom-keating/">
      <![CDATA[<a href="http://www.telrex.com">Telrex</a> today announced CallRex Release 3.5, a business-class VoIP call recording and monitoring solution. For a round-up of VoIP call recording solutions, check out <a href="http://blog.tmcnet.com/blog/tom-keating/voip/voip-call-recording.asp">my article here</a>.<br />
<br />
According to Telrex, the new release features a new distributed-services software architecture which adds more scalability, enhanced multi-site support, streamlined storage and archiving, and additional security.<br />
<br />
Telrex claims that CallRex was the first VoIP call recording solution verified to record encrypted VoIP calls for Cisco CallManager 5.0, and CallRex version 3.5 now provides additional security to ensure that call recording files cannot be secretly altered.<br />
<br />
The CallRex 3.5 distributed-services software architecture features separate services for status, control, recording and conversion of VoIP phone calls.  CallRex 3.5 services operate independently and are deployed on industry-standard Windows servers in single- or multi-server configurations.  Together, the CallRex 3.5 services enable the recording, monitoring, retrieval, playback and utilization of call recordings from any location. <br />
<br />
CallRex 3.5 provides multiple options for storing recorded calls, and delivers enhanced archiving features to streamline management and administration.  With CallRex 3.5, call recordings can be stored on a centralized server, stored locally across multiple servers, or stored directly on Network Attached Storage (NAS) or on a Storage Area Network (SAN).  <br />
<br />
As previously mentioned, CallRex claims to be the first IP-based call recording and monitoring solution verified to record encrypted VoIP calls with Cisco Unified CallManager 5.0.  Previously, companies deploying VoIP call recording solutions were forced to disable call encryption in order to record their calls. With CallRex, companies can both record their calls and maintain secure call encryption to meet stringent security, legal and regulatory requirements.  Telrex is a partner in the Cisco Technology Developer Program and has met the interoperability criteria for Cisco Unified CallManager version 5.0.<br />
<br />
CallRex 3.5 delivers digital watermarking security to ensure that call recordings, once created, cannot be secretly altered or edited.  For each recorded call, CallRex digital watermarking generates a unique signature associated with the data file.  Any change made to a call recording disrupts its watermark indicating that tampering has occurred.  Authorized users are able to validate the watermark at any time.  CallRex digital watermarking provides additional security, enhances audit-trail integrity and raises the standards for legal and regulatory compliance.]]>
      
    </content>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2007:/blog/tom-keating//4.31714-comment:23697</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2007:/blog/tom-keating//4.31714" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/telrex-announces-callrex-release-35-voip-call-recording-solution.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/telrex-announces-callrex-release-35-voip-call-recording-solution.asp#c23697" />
    <title>Comment from Scott Dunn on 2007-02-22</title>
    <author>
        <name>Scott Dunn</name>
        <uri>http://www.cpisolutions.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.cpisolutions.com/">
        <![CDATA[<p>Hopefully with the new 3.5 release Telrex has fixed all the bugs.  We have had nothing but trouble with Callrex. From memory leaks to not recording... we have seen over a dozen major bugs.  To add insult to injury the take forever to fix the bugs.  It is like they do not even care about the customer after the product is sold.  I am just hoping the 3.5 version is going to fix them because our clients are very upset. </p>]]>
    </content>
    <published>2007-02-23T01:21:40Z</published>
  </entry>

</feed>
