RE: IP Phone Advise

  • From: "Ray Dzek" <rdzek@xxxxxxxxxxxxxxx>
  • To: "'[ISAserver.org Discussion List]'" <isalist@xxxxxxxxxxxxx>
  • Date: Fri, 2 Apr 2004 09:34:31 -0800

ISA, and just about any other firewall currently available, has very
poor support for VOIP.  My recommendation would be to put in dedicated
VPN to both locations if it is possible.  Try and choose a carrier that
will honor QOS or 802.1p packet tagging to ensure the best voice
quality.  If you use softphones, you can then use the PC to establish
the VPN back to the main office, otherwise you need to use a hardware
VPN solution on your gateway router in each location.

I know that the vendors I am currently using all use VOIP from their
homes on regular home DSL or Cable Modem service using hardware VPN back
to their main office.  They have been using a mix of hard IP phones and
PC based softphones.  In both cases it is hard to tell, if you can tell
at all, that they are using VOIP.  

Our current configuration has 14 VOIP users at our main office in CA and
10 VOIP users in UT.  The 2 sites are connected via VPN over IP on a
single dedicated T1 in each location (Not through ISA).  Due to a goof
in the order process our Cisco 2611's did not have the correct IOS when
we went live.  So we were not able to use QOS or 802.1p for the first
couple of weeks.  Frankly, since we made the change and fixed the goof,
I can't tell any difference.   And the folks using VOIP from home over
DSL or cable modems are certainly not using packet tagging.

For the 10 remote VOIP users in UT, plus their regular network traffic,
we currently average about 200Kb/s.  This does not count video
conferencing.  

Best of luck!  Now that we have VOIP, the users don't know why we didn't
do it much sooner.

Ray Dzek
Network Operations Supervisor
Specialized Bicycle Components
PH:  408-782-5420
FX:  408-782-5421 

-----Original Message-----
From: Amy Babinchak [mailto:amy@xxxxxxxxxxxxxxxxxxxxxxxxxx] 
Sent: Friday, April 02, 2004 5:37 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] IP Phone Advise


http://www.ISAserver.org

I have a client that is replacing their phone system and is likely to go
with a system that has at least some IP phones. They have 3 locations
and full time people that work from home and plan to expand into 2 more
locations soon so IP makes some sense for them. It will be much cheaper
for them to purchase a single phone system and maintain it from one
location. They are running SBS2003 and Citrix servers. Everyone connects
to the main office there are no servers at the other locations. 

We've got lots of bandwidth at every location the remotes have 768 or
1000 SDSL and main office has 2.0 cable. Everyone has a static IP
address. No bandwidth problems yet. 

Here are my concerns: Everyone needs to maintain good bandwidth. I'm
thinking that a separate Internet line for the phones would be a good
idea. Not only could it provide some redundancy in case of failure but
it would preserve the existing bandwidth for applications. If I can't
convince them of this or if I have to use the same cable as the computer
systems then I'm also concerned about the ISA server. Should I run the
phones through the ISA? Is there a reason to have IP phones behind a
firewall?

Thanks,

Amy 


------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist
ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp
ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com No.1
Exchange Server Resource Site: http://www.msexchange.org Windows
Security Resource Site: http://www.windowsecurity.com/ Network Security
Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
rdzek@xxxxxxxxxxxxxxx To unsubscribe send a blank email to
$subst('Email.Unsub')



Other related posts: