<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3132" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>Agreed. This is our first remote office, so we are still going
with local trunks in order to ensure a successful deployment. </FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>However, I will be watching the number of local calls closely,
both inbound and outbound and do some calculations.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Of course, this all means the WAN stays up, if it goes down,
then we're in trouble. ;)</FONT></DIV>
<DIV> </DIV>
<DIV>--------------------------------------------------------------------------------<BR>Lelio
Fulgenzi, B.A.<BR>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario
N1G 2W1<BR>(519) 824-4120 x56354 (519) 767-1060 FAX
(JNHN)<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<BR>"Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo
buffalo." WJR<BR></DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=jason.aarons@us.didata.com
href="mailto:jason.aarons@us.didata.com">Jason Aarons (US)</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=bills@tns.its.psu.edu
href="mailto:bills@tns.its.psu.edu">Simon, Bill</A> ; <A
title=lelio@uoguelph.ca href="mailto:lelio@uoguelph.ca">Lelio Fulgenzi</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>Cc:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Thursday, June 14, 2007 7:06
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: [cisco-voip] opting out of
local trunks in lieu of low cost long distance</DIV>
<DIV><BR></DIV>Using VoIP (H323/SIP Trunks) at a half-penny per minute
termination can<BR>sometimes be cheaper than a local trunk. Depends on
location. For<BR>example in rural Kansas a voice PRI is still $900 a month,
that a lot of<BR>half-pennys.<BR><BR>-----Original Message-----<BR>From: <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A><BR>[mailto:cisco-voip-bounces@puck.nether.net]
On Behalf Of Simon, Bill<BR>Sent: Thursday, June 14, 2007 5:44 PM<BR>To: Lelio
Fulgenzi<BR>Cc: <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>Subject:
Re: [cisco-voip] opting out of local trunks in lieu of low cost<BR>long
distance<BR><BR>I know there are regulations involved with doing toll-bypass
over IP but<BR><BR>this is the first time I've heard of someone wanting to
purposefully <BR>incur tolls by way of VoIP...<BR><BR>Lelio Fulgenzi
wrote:<BR>> <BR>> Just wondering if anyone out there with remote
sites in different <BR>> calling areas have opted out of local trunks in
liue of low cost long <BR>> distance? That is, route calls local to the
remote office over the WAN<BR><BR>> and out the HQ trunks.<BR>>
<BR>> Granted this is really only available in those areas that have high
<BR>> bandwidth to the remote site, but many educational institutions have
<BR>> high b/w links due to research networks. 100Mbps to remote sites
is<BR>not <BR>> unheard of and now 1Gpbs are also
available.<BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR>-----------------------------------------<BR>Disclaimer:<BR><BR>This
e-mail communication and any attachments may contain<BR>confidential and
privileged information and is for use by the<BR>designated addressee(s) named
above only. If you are not the<BR>intended addressee, you are hereby
notified that you have received<BR>this communication in error and that any
use or reproduction of<BR>this email or its contents is strictly prohibited
and may be<BR>unlawful. If you have received this communication in
error, please<BR>notify us immediately by replying to this message and
deleting it<BR>from your computer. Thank you.<BR><BR></BLOCKQUOTE></BODY></HTML>