tdoyle@4grc.com wrote:
> Hello list.
>
> My name is Trent Doyle and I am a System Admin with a small cable
> company. We would like to investigate the feasability of doing voip.
> We have the older cisco 724 ubrs. We also got a couple of cisco 26xx
> and 36xx routers. Just curious what else we would need to get
> telephony side up and going.
trent,
it depends on what you are wanting to do with voip - if you define what
are you trying to accomplish, then it is easier to recommend tools. it
is also dependent on how much you (or your coworkers) want to learn, and
how much you can/will spend. if you have a lot of money, then cisco's
'solution in a box' would be your easiest bet (nothing against cisco
products, i use them, but i don't need all of them ;) ).
some basic equipment needs:
voice gateway(s) - you connection from ip to pstn. could be a 26/36xx
with fxo ports - if you want to sell voip service to your customers, then
you would probably need to go with a bigger box (as5xxx, nuera, etc).
another, but more expensive alternative, is a softswitch of some sort
(if you are wanting to offer voip services)
you also have to have your ip infrstructure in place - if you have links
which are oversubscribed, then you need to get bigger pipes, or implement
some qos
for sip, you will need a sip proxy. some softswitches offer this,
otherwise there are numerous free alternatives (vocal, asterisk, etc), or
you can buy cisco's. if you will only use h323, then you don't need a
sip box, but sip offers some nice features and seems to have a bit better
quality on lower-bandwidth applications, ymmv
for a cisco-centric view of voip network design and security (including
equipment), see http://snurl.com/38c0 (url snipped for brevity) - it is
the cisco safe ip telephony blueprint. i personally wouldn't do/use
everything they recommend, but that is just me. like most guidelines,
use what you need
if you give us a better idea of what you are trying to do, we can
probably make better recommendations
hth
/joshua
> Thanks in advance.
>
> Trent
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
"Walk with me through the Universe,
And along the way see how all of us are Connected.
Feast the eyes of your Soul,
On the Love that abounds.
In all places at once, seemingly endless,
Like your own existence."
- Stephen Hawking -
> Hello list.
>
> My name is Trent Doyle and I am a System Admin with a small cable
> company. We would like to investigate the feasability of doing voip.
> We have the older cisco 724 ubrs. We also got a couple of cisco 26xx
> and 36xx routers. Just curious what else we would need to get
> telephony side up and going.
trent,
it depends on what you are wanting to do with voip - if you define what
are you trying to accomplish, then it is easier to recommend tools. it
is also dependent on how much you (or your coworkers) want to learn, and
how much you can/will spend. if you have a lot of money, then cisco's
'solution in a box' would be your easiest bet (nothing against cisco
products, i use them, but i don't need all of them ;) ).
some basic equipment needs:
voice gateway(s) - you connection from ip to pstn. could be a 26/36xx
with fxo ports - if you want to sell voip service to your customers, then
you would probably need to go with a bigger box (as5xxx, nuera, etc).
another, but more expensive alternative, is a softswitch of some sort
(if you are wanting to offer voip services)
you also have to have your ip infrstructure in place - if you have links
which are oversubscribed, then you need to get bigger pipes, or implement
some qos
for sip, you will need a sip proxy. some softswitches offer this,
otherwise there are numerous free alternatives (vocal, asterisk, etc), or
you can buy cisco's. if you will only use h323, then you don't need a
sip box, but sip offers some nice features and seems to have a bit better
quality on lower-bandwidth applications, ymmv
for a cisco-centric view of voip network design and security (including
equipment), see http://snurl.com/38c0 (url snipped for brevity) - it is
the cisco safe ip telephony blueprint. i personally wouldn't do/use
everything they recommend, but that is just me. like most guidelines,
use what you need
if you give us a better idea of what you are trying to do, we can
probably make better recommendations
hth
/joshua
> Thanks in advance.
>
> Trent
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
"Walk with me through the Universe,
And along the way see how all of us are Connected.
Feast the eyes of your Soul,
On the Love that abounds.
In all places at once, seemingly endless,
Like your own existence."
- Stephen Hawking -