[VoiceOps] Transnexus LCR

Scott Berkman scott at sberkman.net
Thu May 6 14:00:01 EDT 2010

We also use TransNexus for CDR and are very happy with the product and support.  They are local to us and we have a very good relationship with them.


One of the best things about them is their flexibility and willingness to develop the system(s) to add functions you need if they see it as a benefit to their overall offerings.


If you have any more specific questions feel free to contact me off list.




From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of anorexicpoodle
Sent: Thursday, May 06, 2010 1:03 PM
To: Tim Donahue
Cc: voiceops at voiceops.org
Subject: Re: [VoiceOps] Transnexus LCR


I am running both and have been for years. 

AcmePacket is the leader in the SBC market for a good reason, their product is IMO the best out there, and their TAC and SE team has always been a pleasure to work with. 

TransNexus is a solid product and is about the best solution I have found for gracefully handling routing tables of staggering size, additionally they have a fantastic team over there and are always a pleasure to work with. 

Really, and this is pretty unusual, i don't have any serious negative criticism about either product or the total solution.

Good luck


On Thu, 2010-05-06 at 11:56 -0400, Tim Donahue wrote: 

Hi all,
We are looking LCR packages to deploy as we plan the replacement our existing Netrake SBCs.  The current front-runner for the replacement SBC is AcmePacket.  
We found the LCR software from Transnexus, which according to their website, should be able to work with both our existing infrastructure and our future upgrade.  I was wondering if anyone has any experience (good, bad or other) with Transnexus LCR or SDReporter packages they would be willing to share (on or off-list relpies are welcome) with us.
VoiceOps mailing list
VoiceOps at voiceops.org


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20100506/7c33c890/attachment.html>

More information about the VoiceOps mailing list