[cisco-voip] Is TEHO Now Illegal?

Fri Oct 12 12:15:18 EDT 2012

I think it's carrier stuff, the FCC won't knock on your door if you have an end user forwarding his phone -jason

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Heim, Dennis
Sent: Friday, October 12, 2012 11:51 AM
To: Adam Frankel (afrankel); Joshua Marsh
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Is TEHO Now Illegal?

This seems like more reason to go SIP. I don't think its illegal, I think its that Century Link wants additional compensation.

Dennis Heim
Sr. UC Engineer
World Wide Technology
Office: 314.212.1814
Email: dennis.heim at wwt.com<mailto:dennis.heim at wwt.com>
www.wwt.com<http://www.wwt.com/>

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Adam Frankel (afrankel)
Sent: Thursday, October 11, 2012 8:48 PM
To: Joshua Marsh
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Is TEHO Now Illegal?

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.
All customers I've seen using this feature so far are in India.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/8x/dialplan.html#wp1228408
________________________________
From: Joshua Marsh <jmarsh at compunet.biz><mailto:jmarsh at compunet.biz>
Sent: Thu, Oct 11, 2012 1:43:15 PM
To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> <cisco-voip at puck.nether.net><mailto:cisco-voip at puck.nether.net>
CC:
Subject: [cisco-voip] Is TEHO Now Illegal?

Hello, all.

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.

Here is a quick summary of highlights from that letter:

"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 . . .

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

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.

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.

Thanks much,

J

_______________________________________________

cisco-voip mailing list

cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>

https://puck.nether.net/mailman/listinfo/cisco-voip

itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20121012/fac503aa/attachment.html>