[VoiceOps] New to VoIP

Sorensen, Marty Marty_Sorensen at adp.com
Mon Jun 21 17:48:20 EDT 2010


In the fullness of time, we have discovered the billing is a big, thorny, gnarly deal to do correctly.  Taxes, surcharges, FUSF reporting and remittance, FCC forms.  Just to do it correctly chews up head count and time.  Would recommend using an outside voip billing service if you can at the start.  

-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Eric Hiller
Sent: Monday, June 21, 2010 2:25 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] New to VoIP

>From my experience setting up a CLEC using open source software is not the
way to go, and I am typically all for open source and design much of my
ISP side around it. If you actually plan on growing I would recommend a
true switch though, it simply takes too much time to roll your own
solution and it will never be as reliable as some of the gear out there.
However, you will also end up spending a minimum of $300k I would
estimate.

-Eric

> On 06/21/2010 02:49 PM, Jon Radel wrote:
>
>> Well mostly. As an example, Acme Packet SDs have very expensive
>> (comparatively speaking, at least) content addressable memory (CAM)
>> wherein lives the lookup table for all active SIP sessions, thus
>> allowing the hardware to deal with a much higher volume of RTP packets
>> than a general purpose computer of the same general size and "power"
>> could hope to process, not to mention making it more resilient to DoS
>> attacks.
>
> CAM-like memory, and also ASICs to assist in processing of media and
> the CPU work involved in packet forwarding.
>
> There's no question that pound-for-pound, a high-end SBC can handle a
> whole lot more concurrent calls (with media) than general PC hardware
> with a general purpose task-switching OS with a general purpose PCI
> bus, general purpose I/O scheduler, and a userspace process doing a
> lot of the work.
>
> However, a) you may not need that and b) depending on what it is
> exactly that you intend to do, it may be quite possible to design a
> topology that does not involve relaying media at all most of the time
> (which is where proxies tend to be useful), in which case the case for
> the open-source option is substantially bettered.
>
> --
> Alex Balashov - Principal
> Evariste Systems LLC
> 1170 Peachtree Street
> 12th Floor, Suite 1200
> Atlanta, GA 30309
> Tel: +1-678-954-0670
> Fax: +1-404-961-1892
> Web: http://www.evaristesys.com/
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>


_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops


This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.



More information about the VoiceOps mailing list