Verizon Wireless told FCC that problem of unintentional 911 calls wasn’t widespread on its network, in part because it asked its vendors that used one-touch calling feature to deactivate it for emergency calls. FCC Wireless Bureau Chief Thomas Sugrue asked AT&T Wireless, Verizon Wireless and VoiceStream recently to provide information on steps they were taking to cut down on problem of inadvertent 911 calls. Those calls can occur when preprogrammed 911 buttons on wireless phones are pressed accidentally and emergency dispatcher is dialed automatically. National Emergency Numbering Assn. (NENA) has estimated that significant percentage of 911 calls are unintentional and it asked carriers in Dec. to provide information on what they had done or were willing to do to address problem. Verizon told Sugrue in Aug. 21 response it agreed “most if not all” accidental 911 calls occurred when 1 or 9 key on phones preprogrammed with emergency 911 “one-touch” dialing were pressed by accident. “We believe this problem is not widespread among Verizon Wireless’ equipment base,” carrier said. Company said it hadn’t required handset vendors to provide that one-touch feature. Some vendors included it in handful of models several years ago, but they comprised “only 8 of the 32 models we offer for purchase,” Verizon said. To follow up on Jan. deactivation request, company said it sent letter to vendors in March to make sure they shipped handsets with that feature turned off. It said all vendors confirmed they had done so, with exception of model by Samsung, which manufacturer said had one-touch feature that couldn’t be disabled. Samsung told Verizon it was developing software to turn feature off. Finally, Verizon said it had decided not to offer any new handset model that had one-touch 911 feature. “We have thus modified our product specifications so that they prohibit manufacturers from including the one- touch emergency 911 dialing feature in future models,” carrier said. Separately, VoiceStream told FCC in Aug. 22 letter that it had responded to NENA request for information in March and was trying to raise consumer awareness to prevent inadvertent 911 calls. VoiceStream informed NENA that all of its handsets came from manufacturer without 911 speed dialing being enabled. Carrier said it was working with CTIA on industrywide subscriber awareness program. It also said it was modifying guides for new subscribers to address issue. “Additionally, we will be putting a message directly on customers’ bills and also providing bill inserts specifically addressing the issue of unintentional 911 calling,” VoiceStream said. Carrier said it also listed 911 calls on customer bills so they could see whether they were making such calls by accident.

SBC told FCC it wasn’t trying to delay implementation of Enhanced 911 Phase 2, but was moving ahead to ensure that Phase 2 “can proceed without delay.” In Aug. 20 filing, SBC disputed several concerns raised by Sprint to FCC last week, particularly that SBC wanted to delay Phase 2 implementation in Mich. until Jan. 2003 when effective Phase 2 tariff would be in place. SBC told agency that Sprint took out of context its June 5 letter to Oakland County, Mich., Sheriff’s Dept. Sprint had cited letter in which SBC suggested that public safety groups meet with wireless carriers in state to negotiate commitment not to pursue implementation of FCC decision on cost recovery until alternative source of funding for LEC 911 service provider costs had been found. SBC countered in FCC filing that letter cited by Sprint was just part of discussion between SBC Ameritech and Mich. PSAP (Public Safety Answering Point) Tariff Task Force on issues related to Phase 2 cost recovery, not Phase 2 implementation. SBC said task force approached it and asked it to delay tariff filing for Phase 2 cost recovery because group wanted to jointly approach state lawmakers to amend state 911 law. Existing statute lets wireless carriers charge callers 52 cents, of which 25 cents is used by wireless carriers to recover 911-related costs. However, SBC said law didn’t let wireline carriers recover their costs from 911 fund, meaning SBC Ameritech Mich. had to recover costs from PSAPs through state tariff. SBC had proposed to task force that it delay filing proposed tariff if certain conditions were met, including having agreement of wireless carriers. SBC told FCC that task force rejected offer, so it planned to file proposed cost recovery tariff with Mich. PSC by late Sept. “SBC is unaware of any aspect of the Phase 2 scheme devised by the Commission that would deny SBC Ameritech the right to recover its costs associated with implementing that plan,” filing said. Sprint provided details last week to FCC about SBC’s discussions in Mich. and proposed interface agreement created by BellSouth related to E911. Sprint said FCC Wireless Bureau had sought more detailed information as part of follow-up to carrier’s quarterly E911 implementation report. Sprint had told Commission that documents showed that some providers of automatic location information databases planned to circumvent FCC decision on cost recovery and create additional hurdles to Phase 2 rollout.

Verizon Wireless floated plan to FCC for proposed change that it said would help to alleviate problem that has been standing in way of its meeting Enhanced 911 Phase 2 deadline of Dec. 31. Verizon asked Commission to stipulate that carrier wouldn’t be in violation of such deadlines in cases in which public safety answering point (PSAP) couldn’t yet receive and use more detailed Phase 2 location data because LEC or PSAP hadn’t completed necessary upgrades to their facilities. Verizon said in Aug. 19 filing that action was “urgently needed” due to Dec. 31 deadline for filling certain valid E911 Phase 2 requests by PSAPs. Last fall, FCC issued order in response to request for clarification by Richardson, Tex., about what constituted “valid” PSAP request for E911 service. FCC said such requests were valid if any upgrades needed on PSAP network would be completed within 6 months of request and if PSAP had made “timely request” to LEC for trunking and other facilities needed for E911 data to be transmitted in first place. Verizon said its request would meet order’s goal of requiring licensees to begin Phase 2 deployment “in advance of actual PSAP readiness.” It touched on what had been more frequent E911 theme of carriers -- that LEC readiness was growing problem in terms of E911 readiness. Verizon said that since Richardson order was handed down in Oct., certain LECs had failed to upgrade their automatic location information (ALI) databases in timely way to pass those data to PSAPs, meaning Verizon hadn’t been able to provide “Phase 2 service to many PSAPs in the 6-month time frames” set out in its E911 Phase 2 waiver. Despite “best efforts” of public safety agencies and wireless carriers, Verizon Wireless said: “Phase 2 implementation cannot be completed without upgraded facilities and services provisioned by PSAPs from LECs and their own vendors.” It urged FCC to amend rules so carriers wouldn’t be deemed noncompliant for failing to meet E911 deadline if PSAP couldn’t receive or use Phase 2 data by deadline. Verizon sought 90 days to complete its work and testing after PSAP becomes ready. “In particular, no such violation should occur where such incapability is due to the LEC’s inability or unwillingness to provision facilities/service for the PSAP or is due to delays in upgrading the PSAP’s” on-site equipment, Verizon Wireless said. It said problem was that once it completed changes such as network upgrades for Phase 2 service, providing such E911 data required LEC to upgrade its ALI database. Only then could PSAP and wireless carrier take final steps to complete Phase 2 service, Verizon said. In many areas where it needs LEC service for that process, it said needed upgrades either weren’t complete or wouldn’t be finished until regulatory approval of tariff or PSAP acceptance of contract, “which may take months.” In case of SBC, Verizon said it had completed ALI database upgrades in some markets where carrier had Phase 2 requests, but had “failed to do so in most markets.” Verizon charged that SBC had turned down request to meet last month, saying it instead planned to file wholesale tariffs or negotiate interconnection agreements changes in its region. “To date, BellSouth has thus far offered merely to test its Phase 2 upgrades and only in South Carolina,” Verizon Wireless said. It said it hadn’t been able to move ahead to test Phase 2 service with BellSouth, delaying Phase 2 rollout in markets such as Orlando, Miami, Atlanta, New Orleans. Verizon said Qwest had said it should be able to deploy Phase 2 upgrades in its territory in Sept. as long as needed tariffs were accepted. Carrier said in several states in Qwest territory, tariff wouldn’t be filed until Sept.

Back-and-forth continues at FCC over role of LECs in providing Enhanced 911 services, with Sprint providing Wireless Bureau this week with documents it requested on arrangements with SBC and BellSouth. Sprint said that as part of its quarterly E911 implementation report filed earlier this month, bureau had sought copies of proposed interface agreement created by BellSouth and letter issued by SBC in June, both of which Sprint mentioned in its report. Sprint argued documents showed some providers of automatic location information (ALI) databases planned to “circumvent the FCC’s decisions on cost recovery and create additional roadblocks to Phase 2 implementation.” Wireless Bureau recently directed several large ILECs to make publicly available information related to interconnections needed for E911 deployment, with answers due Aug. 28. Sprint PCS in past has raised concerns at FCC on what it had said was lack of progress among LECs in upgrading ALI databases needed to support Phase 2. ALI consists of more specific latitude and longitude information under Phase 2 that’s provided to emergency dispatchers when wireless subscriber dials 911. Of 2 documents, Sprint told FCC: (1) SBC suggested in June 5 letter to Oakland County, Mich., Sheriff’s Dept. that public safety groups meet with wireless carriers in state “to negotiate a commitment not to pursue implementation of FCC’s King County opinion” until alternative funding source for LEC 911 service provider costs had been found. FCC’s King County decision in late July affirmed that 911 selective router maintained by ILECs was dividing line for E911 implementation costs between wireless carriers and public safety answering points. In letter, SBC proposed delay in filing its proposed wireless 911 tariff for Mich. until Jan. 2003. It also said it couldn’t provide Phase 2 service in Mich. without tariff addressing those costs. (2) Proposed BellSouth Phase 2 interface agreement suggested wireless carriers be charged 63 cents per data dip to cover cost of upgrading BellSouth ALI database. That would mean wireless carrier would pay 63 cents for initial transmission of latitude and longitude. Sprint told BellSouth in July 24 letter that it objected to that charge because it was counter to FCC’s decision on appropriate parties that must pay for ALI database upgrades.

Telecom bills were signed into law in S.C., N.C. and Mass. S.C. Gov. Jim Hodges (D) signed bill imposing regulatory requirements on telecom services run by municipalities. Under SB-290, localities can’t subsidize their telecom business from general tax revenue or by transferring funds from other municipal operations. They also can’t offer tax deductions or govt. subsidies as incentives for customers to sign up. Measure also requires municipal telecoms to maintain separate accounts, submit to annual independent audits and to follow same regulations and pay same taxes as private sector telecom carriers. N.C. Gov. Michael Easley (D) signed bill altering business deductions for 911 fees, closing tax loophole. Under SB-1160, corporations can deduct 911 charges from their state income taxes only if they included charges as part of their federal taxable income. Change in law closed loophole that allowed unintended double deduction for 911 charges. Mass. Gov. Jane Swift (R) signed bill (SB-2349) allowing municipalities to modify telephone equipment so fire depts. could monitor 911 calls to speed equipment to fires without waiting to be contracted by 911 dispatchers. Monitoring must be done by fire dept. personnel in secure area.

FCC Wireless Bureau Chief Thomas Sugrue asked AT&T Wireless, Verizon Wireless and VoiceStream to provide information on what steps they were taking to reduce problem of unintentional 911 calls. In separate letters Wed., Sugrue said those calls could occur when preprogrammed 911 buttons on wireless phones were pressed accidentally and emergency dispatcher was dialed automatically. “Although preprogrammed 911 keys were initially considered to be a useful public safety feature for wireless phones, the number of unintentional calls and the burden they place on PSAP [public safety answering point] officials suggests that more harm than good has been brought about by this feature,” Sugrue wrote. National Emergency Numbering Assn. (NENA) has estimated that significant percentage of wireless 911 calls are unintentional. Problem, Sugrue wrote, is that typical PSAP practice is to remain on line to try to ascertain whether call is intentional. If E911 Phase 2 location capability is in place, dispatcher also may have to send emergency services to caller’s location if it can’t be determined over phone whether call was inadvertent. NENA sent letter to several wireless carriers in Dec. asking for information on what each had done or was willing to do to control problem and outlined several solutions for carriers and PSAPs to address together. “We support NENA’s efforts to address the unintentional calls problem and would urge that all wireless carriers, to the extent they have not done so already, take steps to eliminate the problem,” Sugrue wrote. He told each carrier that it hadn’t responded to NENA or provided information on what steps were needed to tackle problem. Sugrue asked for replies within 15 days of company’s receiving letter on information including: (1) Whether carrier had “communicated to its handset manufacturers its desire that mobile phones not be preprogrammed to dial 911 by pushing a single button on the keypad.” (2) Whether it had instructed its employees to deactivate auto-dial 911 feature if it came preprogrammed on certain phones. (3) Whether it provided subscribers with information on problem of unintentional 911 calls for existing and new handsets. (4) Whether it itemized 911 calls on customers’ bills to highlight problem. NENA raised such issues as possible solutions in its Dec. 12 letter to carriers.

N.Y. PSC told e.spire Communications that it couldn’t quit state’s telecom market before service termination date specified by agency rules. E.spire filed petition July 26 seeking permission to cease providing local and long distance service (Case 02-C-0986). PSC rules require minimum 30 days’ notice of intent to exit market, which would set carrier’s termination date at Aug. 26. E.spire sent notices to customers saying service could be discontinued without warning any time after Aug. 2, and at least 7 users complained to PSC that carrier wasn’t giving them enough time to sign up with another provider. PSC said e.spire had “affirmative obligation” to continue service at least through Aug. 26. Agency said it hadn’t determined whether to require that service be continued past Aug. 26, but indicated it was displeased by carrier’s apparent disregard for PSC’s mass termination rules. Leaving customers unexpectedly without service, PSC said, would be contrary to public welfare because customers wouldn’t be able to call 911 or other numbers for emergency assistance.

FCC is to take up item at agenda meeting today (Thurs.) on whether cellular carriers must continue under regulatory requirements that date back to duopoly era of cellphone service, including mandate to provide analog service as long as they have analog customers or roamers. One expectation is that Commission will agree to phase out requirement for AMPS- type (Advanced Mobile Phone Systems) service that started in 1981, with likely phase-out period of 5 years, several sources said. Bush Administration last month called for 5- year transition, period that several large wireless carriers have backed. Several automakers, developers of in-vehicle telematics systems and carriers also recently urged FCC to establish “orderly transition” from analog requirement. Among policy issues that have been closely watched in proceeding is extent to which callers with hearing disabilities could be accommodated because devices such as hearing aids now often aren’t compatible with digital networks. Auto-collision notification systems such as OnStar also rely on AMPS for location-based emergency response because of ubiquity of analog network. Bipartisan group of members of Senate Commerce Committee, including Chmn. Hollings (D-S.C.), also have urged “gradual phase-out of the requirement rather than an immediate elimination.”

Assn. of Public Safety Communications Officials (APCO) and National Emergency Number Assn. (NENA) wrote to FCC Chmn. Powell on group’s continuing concerns about pace of Enhanced 911 rollout, citing LEC upgrades as “the last remaining hurdle in many instances.” FCC Wireless Bureau Chief Thomas Sugrue recently directed largest ILECs to make publicly available certain information on interconnections needed for E911 deployment by Aug. 28. APCO and NENA also told Powell: “We urge the Commission to take affirmative action regarding carriers that are clinging to questionable location technologies and, as a result, are falling well short of implementation deadlines and accuracy requirements.” APCO and NENA said “most troubling problems” that remained for E911 implementation included failure of many LECs to cooperate with public safety answering points and wireless carriers or to provide on-time upgrades to their automatic location information (ALI) databases. Groups recently lauded Wireless Bureau letter to LECs asking for detailed information on their E911 deployment. “However, we believe that the Commission will need to consider taking further action, including adoption of provisions requiring LECs to proceed in a timely manner to provide necessary elements of Phase 2 operation,” groups said. They also urged Commission to take “a hard look” at Phase 2 rollout of E911 by GSM carriers using Enhanced Observed Time Difference (E-OTD) of Arrival technology. APCO said it still had petition of reconsideration pending on agency’s grant 2 years ago of waiver to VoiceStream Wireless. That waiver had extended certain Phase 2 implementation deadlines for carrier and allowed use of E-OTD technology. APCO and NENA raised concerns about implementation progress of VoiceStream, Cingular and AT&T Wireless. They said Cingular and AT&T Wireless recently submitted reports to FCC “indicating major E-OTD test failures, raising further questions regarding its deployment schedule and ultimate accuracy levels.” APCO and NENA called on FCC to resolve its petition for reconsideration and “to require VoiceStream to consider alternative technologies as possible replacements for E-OTD.”

Mass. legislature passed bill to allow state to take $31 million earmarked for E911 upgrading fund and use it to pay Verizon a debt that state owed carrier for operating 911 system. Bill (HB-1751) sent to Gov. Jane Swift (R) would send to Verizon rather than to E911 fund an emergency service surcharge state imposes on local directory assistance calls over 10th call per month. Measure also directs Dept. of Telecom & Energy to devise new funding system for emergency calling service. Another Mass. telecom bill failed to pass by adjournment of 2002 session. Failed bill (SB-2375) would have required telecom contractors to earn trade license similar to electrician’s license before doing installation work on commercial properties. Bill had passed Senate but failed to clear House by adjournment date.