<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body style="font-family: Arial; font-size: 13px;" bgcolor="#FFFFFF"
text="#000000">
<div id="QCMcontainer" style="font-family:Arial;font-size:13px;">Can't
speak to the legal aspects of TEHO in the US, but to your second
point preventing TEHO is the entire purpose of Geolocation/Logical
Partitioning feature introduced in 8.x. <br>
All customers I've seen using this feature so far are in India. <br>
<br>
<a class="moz-txt-link-freetext" href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/dialplan.html#wp1228408">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/dialplan.html#wp1228408</a><br>
<br>
<br>
<span style="color:#000000;" class="headerSpan">
<div class="moz-cite-prefix">
<hr tabindex="0"><font style="font-size:x-small" face="Tahoma"><!--@A@--><b>From:</b>
Joshua Marsh <a class="moz-txt-link-rfc2396E" href="mailto:jmarsh@compunet.biz"><jmarsh@compunet.biz></a><!--@A@--><br>
<!--@D@--><b>Sent:</b> Thu, Oct 11, 2012 1:43:15 PM<!--@D@--><br>
<!--@R@--><b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><cisco-voip@puck.nether.net></a><!--@R@--><br>
<!--@C@--><b>CC:</b>
<!--@C@--><br>
<!--@S@--><b>Subject:</b> [cisco-voip] Is TEHO Now Illegal?<!--@S@--><br>
</font><br>
</div>
</span>
<blockquote style="border: medium none ! important; padding-left:
0px ! important; padding-right: 0px ! important; margin-left:
0px ! important; margin-right: 0px ! important; font-size:
medium;" cite="mid:CC9C6151.27048%25jmarsh@compunet.biz"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>
<div>
<div style="text-align: left; "><font
class="Apple-style-span" color="#333333"
face="Arial,verdana,sans-serif"><span
class="Apple-style-span" style="border-collapse:
collapse; font-size: 12px;">
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica">Hello, all.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica"> </p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica">This post is in regards to a
recent letter from CenturyLink (CL) warning a
customer that TEHO is no longer allowed, based on
the FCC's 11-161 ruling. It appears that CL's
interpretation of this ruling is that TEHO w/o
inter-carrier compensation is not allowed and can
result in termination of service.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica"><br>
</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica">Here is a quick summary of
highlights from that letter: </p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica">"CL has filed tariff changes that
impact the services provided to ISDN primary rate
service subscribers . . . FCC released an order on
intercarrier compensation (FCC 11-161, released Nov
18, 2011) that clarified . . . VOIP PSTN Traffic.
...What is defined as Toll-PSTN Traffic must be
compensated at applicable interstate switched access
charges. CL has filed tariff changes that make
clear that ... PR services may not be used for the
exchange of Toll VOIP=PSTN traffic . . . this notice
is being sent to inform you that Customer must begin
using services received consistent w/ the FCC's
order and applicable law. For customers using
PRS/PRI services from CL, Toll VOIP-PSTN traffic may
not be exchanged . . . we will take action not
limited to cancellation of services . . .</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica"> </p>
</span></font><span class="Apple-style-span"
style="border-collapse: collapse; color: rgb(51, 51,
51); font-family: Helvetica; font-size: 12px; ">So I did
read a bit of the 752 page document from the FCC, but
I'm still a bit stumped here. First off, they define
“VoIP-PSTN traffic” as “traffic</span><font
class="Apple-style-span" color="#333333"
face="Arial,verdana,sans-serif"><span
class="Apple-style-span" style="border-collapse:
collapse; font-size: 12px;">
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica">exchanged over PSTN facilities
that originates and/or terminates in IP format.” It
appears that CL's interpretation of this is that a
company cannot do TEHO across their different
markets where they have dial tone. This has a huge
effect on our dial plan design as well as how our
customers do business.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica"><br>
</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica">We do what I'm sure a lot of you
do as well: use a global dialing plan and exensive
route filters to make TEHO work across a nation-wide
footprint. Has this been stopped in the name of
competition? Are there any other Netpros who've
seen similar letters? What is your take on this?
Do we need to go undo our dial plans and turn-off
TEHO? Even if we turn-off TEHO, a couple of users
forwarding their phones could circumvent this.</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica"> </p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica">Thanks much,</p>
<p style="margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica">J</p>
<div><br>
</div>
</span></font></div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</div>
</body>
</html>