Application Form [pdf]

This document pretains to SPC-NEW-20070913-00014 for New Application on a Signaling Point Code filing.

IBFS_SPCNEW2007091300014_592555

Approved by OMB 3060−1028 INTERNATIONAL SIGNALLING POINT CODE FILING PER NETWORK PER CODE APPLICANT INFORMATION Enter a description of this application to identify it on the main menu : Syniverse Technologies, Inc. − ISPC Request, Philadelphia, PA 1. Applicant Name: SYNIVERSE TECHNOLOGIES, Phone Number: 813−637−5940 INC. DBA Name: Fax Number: 813−637−5731 Street: 8125 Highwoods Palm Way E−Mail: david.robinson@syniverse.com City: Tampa State: FL Country: USA Zipcode: 33647 − 1776 Attention: Mr David J Robinson 1

2. Contact Name: David Robinson Phone Number: 813−637−5940 Company: Syniverse Technologies, Inc. Fax Number: 813−637−5731 Street: 8125 Highwoods Palm Way E−Mail: david.robinson@syniverse.com City: Tampa State: FL Country: USA Zipcode: 33647 −1776 Attention: David Robinson Relationship: Same 3. Network Location:Please supply any needed attachments Attachment 1: SVR_Transmittal Phi City: Philadelphia Attachment 2: Attachment 3: State: PA Estimated Implemention Date: 10/01/2007 4. Code assignments held in excess of 12 months without implementation must be returned to this Administrator for Yes No reassignment. Unless this office is specifically notified of the actual implementation of assignments, it will be assumed that those implementations did not occur and such assignments will be available for reassignment. I have read and understand these conditions. 2

5. I am aware that all ISPC assignments are provisional and that nobody has a property right in a ISPC. I am aware Yes No that the Commision may take an assigned ISPC and reassign it to another person. 6. I am aware that once a carrier has been granted its signalling point code, it must file annual International Traffic Yes No Data Reports (Section 43.61), which are due only July 31 each year, and the annual Circuit Status Reports (Section 43.82), whcih are due on March 31 each year. Unless a carrier that has been granted a point code has notified this office that it has nothing to report, its failure to file either of these reports will be interpreted as inactive operation and could, therefore, result in the loss of the carrier’s point code assignment. 7. Are you a current holder of a 214 license (international telecommunication common carrier)? If yes, enter the 214 file number: ITC2142005042000154 If no, please explain: WILLFUL FALSE STATEMENTS MADE ON THIS FORM ARE PUNISHABLE BY FINE AND / OR IMPRISONMENT (U.S. Code, Title 18, Section 1001), AND/OR REVOCATION OF ANY STATION AUTHORIZATION (U.S. Code, Title 47, Section 312(a)(1)), AND/OR FORFEITURE (U.S. Code, Title 47, Section 503). 3

FCC NOTICE REQUIRED BY THE PAPERWORK REDUCTION ACT The public reporting for this collection of information is estimated to average less than 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the required data, and completing and reviewing the collection of information. If you have any comments on this burden estimate, or how we can improve the collection and reduce the burden it causes you, please write to the Federal Communications Commission, AMD−PERM, Paperwork Reduction Project (3060−1028), Washington, DC 20554. We will also accept your comments regarding the Paperwork Reduction Act aspects of this collection via the Internet if you send them to jboley@fcc.gov. PLEASE DO NOT SEND YOUR RESPONSE TO THIS ADDRESS. Remember − You are not required to respond to a collection of information sponsored by the Federal government, and the government may not conduct or sponsor this collection, unless it displays a currently valid OMB control number or if we fail to provide you with this notice. This collection has been assigned an OMB control number of 3060−1028. THE FOREGOING NOTICE IS REQUIRED BY THE PAPERWORK REDUCTION ACT OF 1995, PUBLIC LAW 104−13, OCTOBER 1, 1995, 44 U.S.C. SECTION 3507. 4


Document Created: 2019-04-12 05:20:51
Document Modified: 2019-04-12 05:20:51
© 2024 FCC.report
This site is not affiliated with or endorsed by the FCC