[cisco-voip] Getting started in SIP...

[Nick Matthews]

A few notes:

There are three ways to get a SIP trunk:
-The MPLS/T1/WAN carrier is also your SIP provider
-Using MPLS or QoS WAN to get to your SIP provider (different carriers)
-Using whatever you can run IP over to get to your SIP provider

The first is the optimal solution.  It is probably also the most
costly.  With the cost comes the guarantee that any quality problems
boil down to one person to blame.
The second is pretty good, and should work fine.  Your IP provider may
blame the SIP provider, but at the end of the day your IP provider has
QoS they have promised you.
The third is likely going over a cable modem/DSL at a small site, or
if you currently have a data circuit with no voice QoS.

IMO, the first and second are what you're looking for if you have
anything other than a small site.  If you have a small site, the third
can be very cost compelling and quality is compromised.

If you just want to see it, you can go out to any of the hundreds of
SIP carriers online and sign up for an account.  They will give you a
username/password/DID combination most likely.  You may be able to use
IP based authentication as well.  You can then run this SIP trunk over
any data line you wish.

It's usually a cost driven thing.  Most sites have entirely too many
analog/T1 lines for their size, that exist only in a worst case
scenario.  With SIP you can centralize those, and between allowing a
burstable amount of traffic over the SIP trunk, and centralizing
multiple time zones with different peaks, you can reduce your overall
trunk capacity pretty significantly.  It can also be quite a bit more
flexible because we're talking MPLS and Ethernet rather than T1
cables.

-nick

On Tue, Apr 6, 2010 at 6:50 PM, Dennis Heim <Dennis.Heim at cdw.com> wrote:
> It also matters what size of sites you are using. I am more comfortable with
> SIP trunks for small sites. It also have to do with what type of connection
> your last mile is. If you got fiber to the prem, then BW really will not be
> as big of an issue, as opposed to have a couple of T’s.
>
>
>
> Dennis Heim
> Network Voice Engineer
> CDW  Advanced Technology Services
> 11711 N. Meridian Street, Suite 225
> Carmel, IN  46032
>
> 317.569.4255 Office
> 317.569.4201 Fax
> 317.694.6070 Cell
>
> dennis.heim at cdw.com
> www.berbee.com
>
>
>
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
> Sent: Tuesday, April 06, 2010 1:46 PM
> To: Robert Kulagowski
> Cc: Cisco VOIP
> Subject: Re: [cisco-voip] Getting started in SIP...
>
>
>
> I think you'll get quite a few opinions on this, here are mine:
>
> SIP is not as "cost effective" as you might think, unless you already have
> internet access from your SIP provider. Typically, your ISP will want to
> limit the amount of voice on the link so you will have to purchase more bw
> and it will sit idle.
> SIP is not as "feature rich" as current PRI technology is, so there will be
> issues with conferencing, holding, faxing, etc.
>
> These opinions are based on our local SIP providers (and about 6-12 months
> ago at that).
>
> Things to think about:
>
> what equipment will you need to run this SIP trunk (3945, CUBE, DSPs, etc?)
> what features will you lose/gain if you move to SIP
> what are the full costs
> what about reliability, quality, etc?
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it.
>                               - LFJ (with apologies to Mr. Popeil)
>
>
> ----- Original Message -----
> From: "Robert Kulagowski" <rkulagow at gmail.com>
> To: "Cisco VOIP" <cisco-voip at puck.nether.net>
> Sent: Tuesday, April 6, 2010 1:21:37 PM GMT -05:00 US/Canada Eastern
> Subject: [cisco-voip] Getting started in SIP...
>
> Are there things that folks are doing to get familiarized with SIP
> trunking from providers without committing to a 1 year contract?  Is
> there a way to experiment "in house" that is applicable once you get a
> SIP trunk from a provider?  Still trying to determine if there's a
> cost justification in moving from a TDM-style PRI configuration to a
> SIP trunk configuration.  Or is it not a cost justification that's
> driving this train?
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>