Trading Partner Profile for Porting between Sprint and ...



TRADING PARTNER PROFILE (TPP)

Purpose: The purpose of the Trading Partner Profile is to exchange contact and connectivity information required to port with Trading Partners. There are two sections to the profile:

o Initial Set-Up: How to establish porting as a Trading Partner.

o Porting Business & Support Information: What information is required for optimal customer port experience?

Please return Trading Partner Profile, to: Julie Rochester: jrochester@

SECTION 1: INITIAL SET-UP

A. GENERAL TRADING PARTNER INFORMATION

|O |Item | | |

|P | | | |

|E | | | |

|R | | | |

|A | | | |

|T | | | |

|I | | | |

|O | | | |

|N | | | |

|S | | | |

| |Company Name | |X |

| |Wireless or Wireline | |X |

| |Operating Company No. (OCN) | |X |

| |Administrative OCN | |X |

| |Service Provider ID (SPID) | |X |

| |LSMS SPID (Can be SS7 provider) | |X |

| |LSR Version ID | |X |

| |FOC Version ID | |X |

| |WICIS Version ID | |X |

| | | | |

| | |

| |Monday – Saturday | |When will you (Carrier) accept and process port |

| | | |requests? |

| | | | |

| | | | |

| | | | |

| | | | |

| |Sunday | |When will you (Carrier) accept and process port |

| | | |requests? |

| |Holidays | |What Holidays will you (Carrier) NOT accept and |

| | | |process port requests? |

B. PORT RESOLUTION CENTER

Sprint is available to support error/reject resolution subject to the following:

|Item | | |

|Port Resolution Center: | | |

|Primary contact name |Ex: Port Resolution Center |X |

|Contact Description |Ex: Port Resolution Center |X |

|Phone Number (Carrier Support) | |X |

|Phone Number (Customer Support) | |X |

|FAX Number | |X |

|Email address | |X |

|Hours of Operations support: |

|Monday – Saturday | |X |

|Sunday | |X |

|Holidays | |X |

C. WLNP CARRIER ACCOUNT MANAGER

Carrier point-of-contact for establishing a porting relationship, as well as ongoing porting account management. This contact information should NOT be shared with your Port Resolution Center. 

|Item | | |

|Carrier Point of Contact | |X |

|Primary Contact Name | |X |

|Title | |X |

|Address | |X |

|City | |X |

|State | |X |

|Zip | |X |

|Work Phone Number | |X |

|Mobile Number | |X |

|Fax | |X |

|E-Mail Address | |X |

| | | |

|Alternate Contact Name | |X |

|Title | |X |

|Address | |X |

|City | |X |

|State | |X |

|Zip | |X |

|Work Phone Number | |X |

|Mobile Number | |X |

|Fax | |X |

|E-Mail Address | |X |

D. SPIDs/OCNs

Trading Partner OCNs for SOA SPID of “X” and LSMS SPID of “A”:

NOTE: Please list all 4 Digit OCN’s per NPAC SOA SPID. If you have more than one SOA SPID, please indicate which OCN’s belong to each.

|OCN: |OCN: |OCN: |OCN: |OCN: |OCN: |OCN: |OCN: |

| | | | | | | | |

| | | | | | | | |

| | | | | | | | |

| | | | | | | | |

| | | | | | | | |

Trading Partner OCNs for SOA SPID of “X” and LSMS SPID of “B”:

|OCN: |OCN: |OCN: |OCN: |OCN: |OCN: |OCN: |OCN: |

| | | | | | | | |

| | | | | | | | |

| | | | | | | | |

| | | | | | | | |

| | | | | | | | |

Trading Partner OCNs for SOA SPID of “Y” and LSMS SPID of “C”:

|OCN: |OCN: |OCN: |OCN: |OCN: |OCN: |OCN: |OCN: |

| | | | | | | | |

| | | | | | | | |

| | | | | | | | |

| | | | | | | | |

| | | | | | | | |

E. CONNECTIVITY

Do you have an agreement with a Clearinghouse vendor or Service Bureau? If YES, please provide the vendor name and contact information. If you are using a Clearinghouse,

|C |Item | | |

|O | | | |

|N | | | |

|N | | | |

|E | | | |

|C | | | |

|T | | | |

|I | | | |

|V | | | |

|I | | | |

|T | | | |

|Y | | | |

| | |

| |Vendor Name |Example: TSI | |

| |Contact Name |Network Operations Center | |

| |Contact description |Network Operations Center | |

| |Phone number #1 |800-892-2888 | |

| |Phone number #2 |813-273-3440 | |

| |FAX number |813-273-3570 | |

| |Email address |Netops@ | |

| |Other |Hotline@ | |

If NO Clearinghouse or Service Bureau, please provide contact information for Connectivity.

|C |Item | | |

|O | | | |

|N | | | |

|N | | | |

|E | | | |

|C | | | |

|T | | | |

|I | | | |

|V | | | |

|I | | | |

|T | | | |

|Y | | | |

| | |

| |Contact name |N/A | |

| |Contact description |N/A | |

| |Phone number #1 |N/A | |

| |Phone number #2 |N/A | |

| |FAX number |N/A | |

| |Email address |N/A | |

| |Other |N/A | |

F. TRANSPORT MODE

This following sections marked in RED are required only if Trading Partner is NOT using a Clearinghouse vendor or Service Bureau for connectivity & transmission of port requests.

|C |Item | | |

|O | | | |

|R | | | |

|B | | | |

|A | | | |

| |Porting Method: Primary, Secondary, N/A | | |

| |ICP Package/Application | | |

| |(“send to”) | | |

| |ICP Physical Server | | |

| |(“receive from”) | | |

| |Failover ICP Server | | |

| |Application Port Information | | |

| |Naming Service / IOR | | |

| |DLCI (Frame Relay usage) | | |

| |LDAP Provider | | |

| |Security Requirements | | |

| |Security Requirements | | |

| |Firewall Requirements | | |

| |SSL Requirements | | |

| |Proprietary Requirements | | |

| |Service IDL version | | |

| |Implementation OMG standard compliant? | | |

| |…OMG CORBA Standards Supported … |

| |Vendor |Product Name/Version |OMG CORBA Version |IIOP Version |

| | | | | |

| | | | | |

| | | | | |

| | | | | |

|F |Item | | |

|A | | | |

|X | | | |

| |Porting Method: Primary, Secondary, N/A | | |

| |FAX number | | |

| |Backup FAX number | | |

|E |Item | | |

|- | | | |

|M | | | |

|A | | | |

|I | | | |

|L | | | |

| |Porting Method: Primary, Secondary, N/A | | |

| |Specific E-Mail Requirements | | |

|O |Item | | |

|T | | | |

|H | | | |

|E | | | |

|R | | | |

| |Porting Method: Primary, Secondary, N/A | | |

| |Other Communication Requirements | | |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download