<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.6980.93">
<TITLE>[Hen] OneNet services</TITLE>
</HEAD>
<BODY>
<DIV id=idOWAReplyText14228 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>The University of Oklahoma's
Norman campus is currently using Nortel's VoIP services. The platform was
a decision based upon hardware cost (a line card for the existing phone switch)
and recurring O&M costs (easier to support a single, unified platform than
to try to integrate two separate systems). We currently utilize our VoIP
services both on and off campus. Our off-campus sites include our Tulsa
campus, remote sites with T-1 connections, and SOHO's with broadband
services.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Deploying VoIP has been relatively painless
for the majority of our campus. The only issues were related
to:</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>1) QoS over "low speed" (i.e. <T-1
and >25 users) links. We quickly learned that having routers instead of
"dumb bridges" (e.g. NetToNet T-1 or DSL units) on each end of these links
became a valuable asset. We were able to tune QoS parameters to allow VoIP
traffic to have highest priority across low-speed links. QoS over high
speed links isn't required, and can cause a slight decrease in network
performance (vendor dependent) if enabled.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>2) The initial roll-out of VoIP would
not work behind firewall'd/PAT'd connections. Nortel has since provided a
fix for this issue, but I still urge anyone attempting to roll out VoIP to
ensure that their phones will work behind the most popular SOHO
firewalls.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>3) The first VoIP phones that we
deployed did not support VoIP. This has since changed, and we are looking
into mid-span PoE devices to retrofit areas which do not have network equipment
that provide in-line PoE. Future purchases of network hardware will
include PoE support (Nortel supports Cisco proprietary or IEEE standard
PoE). To date, wattage output per port has not been an issue, but the
future phones (color with video conferencing capabilities) may require more
power than our existing switches can supply.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Hope this helps others in their VoIP
decisions.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>-Zane</FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> hen-bounces@lists.onenet.net on behalf of
Johnson, Bill<BR><B>Sent:</B> Tue 12/28/2004 4:20 PM<BR><B>To:</B>
Hen@lists.onenet.net<BR><B>Subject:</B> [Hen] OneNet
services<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>How many of you are currently doing VoIP? Are you using it "on
campus"<BR>or "between campuses" or "both"?<BR><BR>Also, can you give a few
details about your experience deploying you<BR>system? The comments you
share may be a big help to others on this list<BR>who are considering doing
so.<BR><BR><BR>Bill Johnson<BR>Director of Network Operations -
OneNet<BR>Director - Netrad Infrastructure for CASA<BR>President - Oklahoma
Distance Learning Association<BR>405-225-9444<BR>cell 405-919=1718<BR>video
164.58.250.185<BR><BR>_______________________________________________<BR>Hen
mailing list<BR>Hen@lists.onenet.net<BR><A
href="http://lists.onenet.net/mailman/listinfo/hen">http://lists.onenet.net/mailman/listinfo/hen</A><BR></FONT></P></DIV>
</BODY>
</HTML>