• United States
Managing Editor

AT&T exits local stage

Jul 02, 20042 mins

Recent rulings on wholesale policy force carrier to leave seven states

Plus: Qwest’s nationwide VoIP service for business and Verizon’s national transparent LAN service.

AT&T will no longer compete for traditional local and long-distance voice customers in seven states across the U.S. AT&T says a government decision earlier this month allows RBOCs to raise local access line wholesale rates, which essentially forced the carrier out of these particular markets. The states affected are Ohio, Missouri, Washington, Tennessee, Louisiana, Arkansas and New Hampshire. The carrier says it will continue to support its existing customers and offer business services in all of these markets. It will also continue to offer its consumer AT&T CallVantage VoIP service, which uses DSL and cable modem Internet access lines.

Qwest unveiled a nationwide network-based VoIP service for businesses. Through a Web interface, customers of the carrier’s OneFlex service can “point-and-click” to choose features such as conference calling, add new users and set up voicemail. OneFlex will be available to business customers in Boise, Idaho; Denver; Minneapolis; and Phoenix in mid-July. By the end of 2004, the service will be rolled to 22 other metropolitan areas. Qwest will expand OneFlex to additional markets in 2005.

Verizon’s Enterprise Solutions Group launched a national transparent LAN service to provide point-to-point connectivity between business sites over a shared backbone. The MPLS-based service is available in 18 bandwidth options ranging from 10M bit/sec to 600M bit/sec. Verizon’s new service is available now in select Northeast and mid-Atlantic areas and will expand this the summer to the South and West. It will ultimately reach 35 markets across the country, the carrier says.

Managing Editor

Jim Duffy has been covering technology for over 28 years, 23 at Network World. He covers enterprise networking infrastructure, including routers and switches. He also writes The Cisco Connection blog and can be reached on Twitter @Jim_Duffy and at

More from this author