TITLE: Contribution on Vertical Service Codes (VSC) Action Item ATIS PTSC Austin Meeting February 21, 2017 Contribution TITLE: Contribution on Vertical Service Codes (VSC) Action Item SOURCE*: Hala Mowafy (Ericsson) ISSUE NUMBER: S0148 _______________________________ Abstract   This presentation aims to progress PTSC’s response to the Strike Force action item on reporting robocalls using VSCs. Pros and Cons of using existing or new VSCs were discussed in PTSC-2016-00234R1. NOTICE This contribution has been prepared to assist the ATIS PTSC. This document is offered to the Committee as a basis for discussion and is not a binding agreement on Ericsson or any other company. The requirements are subject to change in form and numerical value after more study. Ericsson specifically reserves the right to add to, or withdraw, the statements contained CONTACT: Hala Mowafy email: hala.mowafy@ericsson.com

Strike Force Action Item Background Detect Report Mitigate Strike Force Action Item "Use of Vertical Service Codes (VSC) for Reporting Unwanted Calls"; Evaluation of possible vertical service code use (* code) or other mechanisms (PTSC-2016-234R1) 4Q2017 PTSC   PTSC #0148 Overview Reporting robocalls is an important element of the overall mitigation construct Part of the consumer empowerment is to make reporting tools available Action Item above Traditional call management services have relied on invoking *XX codes (or VSCs) to perform similar functions, such as tracing a call *XX codes have been exhausted, but *2XX codes are available. Will need New requirements New development

TDM : Re-using *57: Pros and Cons Mission and Target Industry Segments Summary of Issues This action item is looking at the use of VSCs for TDM, VoIP and Wireless. The following summarizes the pros and cons for each technology, as well as outlining the alternatives. Call Trace VoIP and Wireless Call Trace allows the recipient of a call to initiate a trace of the last call by dialing *57 after ending the call. The Call Trace information (i.e., Calling Party Number, date and time associated with the call) is retained and - upon customer’s request - is made available for further use by the carrier and/or law enforcement. A new VSC *2XX It is feasible to develop new VSCs and the corresponding services in the IP environment (VoIP or Wireless). New Requirements - new requirements: joint PTSC-INC efforts. NANP approval. New Development – depends on each service provider’s timeline Web portals – carrier-specific and FTC or FCC websites for robocall reporting Smart phone apps – capture the incoming number, have the app on the phone report it to an App Server, etc. in charge of assembling offending TNs for further processing (add to black list, or investigate origin via traceback techniques, etc.) Call Centers TDM : Re-using *57: Pros and Cons If no new development is planned for legacy TDM, it has been suggested that *57 be also used to report robocalls (as well as harassing calls) Pros – no new development; may also be more intuitive for consumer to use Cons – combining functions under one code does not serve the purpose of reporting robocalls in a timely manner for inclusion in blocking mechanisms. Procedures to distinguish records created to report robocalls as opposed to tracing harassing calls could be difficult. Alternatives 3

Preparing a Response to the Action Item VoIP Wireless TDM Plan to use and develop *XXX code for reporting robocalls? If not, are there any reporting alternatives available? Please list one or two examples.