Syniverse Porting GUI

Syniverse Porting GUI

What is the Syniverse Porting GUI?
Secure way to quickly and easily submit port requests to
a Syniverse WLNP Service Bureau or Clearinghouse
customer.
Access to more than 90 different carriers with more than
100 SPIDs.
Used to submit either simple or complex port requests to
wireless carriers
• NPDI = B, wireless to wireline
• NPDI = A, wireless to wireless
2

Benefits
TP GUI brings a faster response and an easier porting
process.
Enter just the data that wireless carriers need to produce
a response.
Porting form makes it easy to create and submit
requests.
Basic validations completed by system before submitting
your request so time is saved troubleshooting mistakes.
3

Accessing the System
4

Logging In To Crossroads
https://crossroads.syniverse.com
5

First Time Logging In
6

Change Your Password
7

Crossroads Home Page
Select the LNP Tab to access the Porting GUI
8

LNP Tab
To learn how to use the LNP
GUI review the Syniverse
Porting GUI training guide
Access online Help, download a pdf file,
or contact the Syniverse Port Center
9

Create a New Port Request
If you have more than one SPID
click the “Select SPID” link
10

Selecting Your SPID
From the dropdown box choose your
company SPID for which you are
submitting the port request for.
Then click the “Select” button
11

Required fields
…if ONSP is on WICIS 4.0
*Does not support one day porting
12

Required Fields – NPDI = A
(wireless to wireless)
Request Number
(format: NNSPIYYJJJXXXXXX)
• NNSP = your SPID
• I = any number from “0” to “9”,
corresponding to the “system” sending the
request – you can use ‘0’ since your
submitting the request manually.
• YY = the year in 2-digit format (e.g. “10”)
• JJJ = Julian Date, which is the number of
the day of the year , “001” through “366”.
• January 29 th = Julian date “029”
• June 14 th = Julian date “165”
• XXXXXX = a sequential number so the
request is unique .This portion of the
request number can be 1-6 digits long.
Version ID
• unique number for each version of request
(don’t skip though)
OLSP’s Account Number or
SSN/Tax ID for subscriber
13

Required Fields – NPDI = A
(wireless to wireless)cont…
Old Network Service
Provider
Desired Due Date & Time
(format: MM/DD/YY HH:MM)
Agency Authorization Date
& Name
Initiator Identification
Implementation Contact &
Phone
First & Last Name or
Business Name
Street, City, and Zip Code
Ported TN(s)
14

Required Fields – NPDI = B
(wireless to wireline)
Request Number (a.k.a. PON)
(when using letters please
Capitalize)
Version ID
SSN/Tax ID or OLSP’s
Account Number for
subscriber
Old Network Service
Provider
Desired Due Date & Time
(format: MM/DD/YY HH:MM)
15

Required Fields – NPDI = B
(wireless to wireline)cont…
Agency Authorization Date
& Name
Initiator Identification
Implementation Contact &
Phone
First & Last Name or
Business Name
Street, City, and Zip Code
Ported TN(s)
16

Required fields
…if ONSP is on WICIS 5.0
*Supports one day porting
17

Required Fields – NPDI = A
(wireless to wireless)
Request Number
(format: NNSPIYYJJJXXXXXX)
• NNSP = your SPID
• I = any number from “0” to “9”,
corresponding to the “system” sending the
request – you can use ‘0’ since your
submitting the request manually.
• YY = the year in 2-digit format (e.g. “10”)
• JJJ = Julian Date, which is the number of
the day of the year , “001” through “366”.
• January 29 th = Julian date “029”
• June 14 th = Julian date “165”
• XXXXXX = a sequential number so the
request is unique .This portion of the
request number can be 1-6 digits long.
Version ID
• unique number for each version of request
(don’t skip though)
• Must be 00 when sending an Initial Port
Request
SSN/Tax ID or OLSP’s
Account Number for
subscriber
18

Required Fields – NPDI = A
(wireless to wireless)cont…
Old Network Service
Provider
Desired Due Date & Time
(format: MM/DD/YY HH:MM)
Agency Authorization Date
& Name
Implementation Contact
Phone
Zip Code
Ported TN(s)
19

Required Fields – NPDI = B
(wireless to wireline)
Request Number (a.k.a. PON)
(when using letters please
Capitalize)
Version ID
• Must be 00 when sending an Initial Port
Request
OLSP’s Account Number or
SSN/Tax ID for subscriber
Old Network Service
Provider
20

Required Fields – NPDI = B
(wireless to wireline)cont…
Desired Due Date & Time
(format: MM/DD/YY HH:MM)
Implementation Contact
Phone
Zip Code
Ported TN(s)
21

Add Ported TN(s)
After completing
required fields select
the Number
Portability Details
box to add your
Ported TN(s)
22

Add Ported TN(s)
Select the “Add” button and enter the
Ported NBR. If submitting a multi-line
request click the “Add” button a
second time. When complete click
the X to close the box.
If not entering 2 nd , 3 rd , 4 th ,
(etc.) TN please remove
the blank entry by clicking
on the trash can.
23

Submit Port Request
After entering all required
information click the Submit
button
24

Validation Errors
Any required fields that are missing of filled out
incorrectly will cause a Validation Error.
A notice will appear identifying which required
fields were missing or filled out incorrectly.
Simply correct the specified fields and click the
Submit button again.
25

Port Request Results
Upon successfully submitting your port
request you will receive this message.
Once the ONSP supports one day porting, the
text of this message will reflect the expected
response times for one day porting.
Click Create Port Request to
submit another request or exit
the system
26

Creating a Supplemental Request
Click the “Create Sup Request” link
27

Enter Request Number
Enter the Request Number
(or PON) exactly how you
entered it on the initial
request and click “Submit”
28

Select Supplement Type
Select the Supplement
Type from the drop
down box
29

Update & Sup Request
Update, correct or add
data in fields as
necessary, enter
information into the
Remarks field and click
“Sup Request”
30

Supplemental Request Results
Upon successfully submitting your port
request you will receive this message.
Once the ONSP supports one day porting, the
text of this message will reflect the expected
response times for one day porting.
31

Help
Help is available on the LNP Tab by clicking the link,
“For Help, please click here”.
For questions about submitting a Port Request or
getting a response contact the Syniverse Port Center at
1-888-338-7678
For questions about accessing the Porting GUI contact
Syniverse Customer Support at 1-800-892-2888 or email
at CustomerSupport@syniverse.com.
32

Q&A
How do I get responses?
A Your responses will arrive the same way they do today. So, if you
currently send LSRs and receive responses (FOCs/Rejects) via e-
mail you will still receive the responses via e-mail to the same
address you get them at today. If you send and receive via fax
then the responses will come to your fax number in use today.
How do I handle fall out?
A If you submit a request and receive a Reject it means your
request failed data validation at the wireless carrier. Usually this
means the phone number and validation data (account number,
password/PIN, or social security/tax ID) in the request did not
match the phone number and comparable data in the old service
provider’s customer record database. To resolve this issue you will
create and submit a supplemental request and send it to
Syniverse via TP GUI.

Q&A
Can I get a status on a port request?
A Once you click “submit”, a properly entered request will be sent
to the wireless carrier without manual processing by Syniverse
and you will receive an immediate “success” message on the GUI
screen. In most cases, when porting from a large wireless carrier,
you will receive a response within a few moments. If the wireless
carrier has a manual process to review the request and produce
the response then the response will take longer. Since the
relatively few large wireless carriers have many customers in
most cases you’ll be porting with one of them and you’ll probably
receive a response before you need a status. Once the wireless
carrier responds – whether they’re a large automatic carrier or
smaller manual responding carrier – you’ll receive that response
automatically so Syniverse would not have any additional
information available to provide in a status. If a response for a
port submitted via the Porting GUI is overdue please check with
your trading partner.
34

Q&A
Who can use it?
A Any fax-based wireless, or wireline or VoIP carrier can ask for
access to the Porting GUI. Once the carrier has been set up for
access, any authorized user of that company can submit a request
(a user is authorized by the company administrator).
Why doesn’t its data entry form look like an LSR? Where
are the other fields normally on a LSR?
A To increase the speed of data entry you need to enter only those
fields required for Syniverse to create a valid wireless port
request. There is no need to enter other data from an LSR that is
not needed in a wireless port request.
Does it work for port outs from my carrier (NPDI = “C”)?
A No, not at this time. Syniverse will continue to port requests to
you as we do today (email, fax, EDI or your GUI). You will still
send responses to us as you do today.

Q&A
How secure is the Porting GUI?
A Syniverse takes data safety and security very seriously. Without a
matching and valid user ID and password a user cannot log into
Crossroads. Crossroads provides HTTPS-based security and
infrastructure for all Syniverse web-based application interfaces.
When a user logs into Crossroads the user’s log in ID is tied to a
company ID number and SPID that provides the user access to
only authorized applications (in the case of most wireline carriers
this will only be the Porting GUI). Also, since the User ID is tied to
a company number they are only able to submit requests from
that company and its SPID(s).
36