This document provides an overview of configuring 8MS Cloud to enable Resp Org Change (ROC) functionality. It discusses what the ROC is, the ROC screens and APIs available in 8MS, and the advantages of using 8MS over the Somos ROC system. It also outlines the configuration steps needed, including obtaining a Somos login with ROC permissions and filling out a form to grant 8MS access to the Somos system to submit ROC requests.

1. 8MS® Cloud: SaaS for toll-free
provisioning, texting and LCR
ROC Enablement
Part I - Configuration
Mike Gilbert
Senior Account Director

2. Agenda
4/19/2017 © 2017 CSF Corporation 2
1) What is the ROC
2) CSF Implementation Overview
3) CSF Implementation Advantages
4) Configuration Steps
5) Mandatory Date – July 1, 2017
6) Q&A

3. What is the ROC
4/19/2017 © 2017 CSF Corporation 3
In 2016, Somos introduced a centralized Resp Org Change
(ROC) Management System. Specifically, this system was
intended to provide
 A common, consistent set of data required for all Resp
Orgs to ask for toll-free numbers
 A long-term history of all ROC requests
 A web-based user interface to allow Resp Orgs to submit
and manage ROC requests

4. CSF Implementation Overview
4/19/2017 © 2017 CSF Corporation 4
The new 8MS ROC screens and APIs provide the following capabilities:
 The ability to submit a new ROC request using the Submit ROC Request
screen and the ROCNumberRequest API call
 The ability to retrieve and view pending and old (closed) ROC requests using
the ROC Management screen and the ROCRetrieveRequests,
ROCRetrieveRequestDetail and ROCDownloadDocument API calls
 The ability to approve or decline pending incoming ROC requests using the
ROC Management screen and the ROCManageRequest API call
 The ability to remove numbers from pending outgoing ROC requests using the
ROC Management screen and the ROCManageRequest API call
 The ability to cancel pending outgoing ROC requests using the ROC
Management screen and the ROCManageRequest API call
 The ability to add additional documentation to pending outgoing ROC requests
using the ROC Management screen and the ROCUploadDocument API call

5. ROC LOA Screen
4/19/2017 © 2017 CSF Corporation 5

6. ROC Management Screen
4/19/2017 © 2017 CSF Corporation 6

7. ROC Admin
4/19/2017 © 2017 CSF Corporation 7

8. CSF Advantages
4/19/2017 © 2017 CSF Corporation 8
While users could choose to use the Somos ROC user interface, using
the 8MS user interface provides multiple advantages:
 Once logged in to 8MS, there is no need to jump to a separate system;
all ROC features are fully integrated in 8MS.
 8MS provides multiple Entity support, allowing you to view all ROC
port out/port in requests across your many Entities without having to
log out and log back in with a different login.
 8MS provides a single screen to view all details of ROC requests. For
a quick turn-around, this screen allows you to:
 review all requests
 approve or deny incoming requests
 modify or cancel outgoing requests

9. CSF Advantages (continued)
4/19/2017 © 2017 CSF Corporation 9
 8MS provides a single screen to create ROC requests,
making it faster and easier to do so. Simply enter your
number(s), Resp Org, and LOA and then send the request.
 The work-horse of 8MS, the Number List, makes for
seamless port-ins, routing changes, texting activations,
carrier activations, and other batch functions.
 8MS provides a user-specific history of all ROC request
changes, making audit and accountability easy and more
comprehensive.
 8MS provides a comprehensive REST-based API to make
ROC process integration faster and easier.
 8MS ROC Ports are free! 8MS users do not get charged
for ROC transactions.

10. Configuring 8MS for ROC
4/19/2017
© 2017 CSF Corporation
10
Before using the 8MS ROC screens, it is necessary to configure your 8MS
account with a Somos login with ROC permissions.
1. To begin, you must have a valid Somos login with ROC permissions. If
you already have a login on Somos, you may use that one. We strongly
recommend that you create a new login that is dedicated to use within
8MS.
Somos uses password aging when you log onto their system. Should
you choose to use the same Somos login for both 8MS ROC
transactions and for logging onto Somos, at some point, you will log
onto the Somos web site and be forced to change your password. When
this happens, you will also need to update that password on 8MS or
ROC requests from 8MS will fail. If you have separate logins for your
Somos work and for ROC, you will never have to deal with password
aging, since Somos does not enforce password aging from API users.

11. Configuring 8MS for ROC (Continued)
4/19/2017 © 2017 CSF Corporation 11
2. Once you have confirmed that you have a valid Somos login with ROC
permissions, you will need to fill in a form that gives your 8MS system
permission to send ROC requests on your behalf, using your Somos
login. This form is available from the 8MS system; select
Documentation from the menu then and select the ROC Access link.
After filling in the form, email it to 8MS Customer Support at
8mscust@csfcorp.com. The 8MS support team will send your form to
Somos to process, activating your login for 8MS ROC.
Somos ROC permission is managed by Entity. For that reason, on the
Somos form, you must provide one login for each Entity within your
8MS Company.
3. Once the Somos ROC access form has been processed, you will need to
add your login and password to the ROC Administration screen. Saving
this login and password enables 8MS to send ROC requests on your
behalf.

12. 4/19/2017 © 2017 CSF Corporation 12
Portal.somos.com

13. ROC Admin Form
4/19/2017 © 2017 CSF Corporation 13

14. Q&A
4/19/2017 © 2017 CSF Corporation 14

15. Thank You
4/19/2017 © 2017 CSF Corporation 15
Mike Gilbert
Office: 732-302-0222 ext. 6610
Email: mgilbert@csfcorp.com
Support Hotline
732-356-6999
8MSCust@csfcorp.com
Frank Lauria
EVP Sales & Business Development
Office: 732-302-0222 ext. 6608
Mobile: 732-713-3562
Email: Frank.Lauria@csfcorp.com
Matt Noreen
Office: 732-302-0222 ext. 6609
Email: mnoreen@csfcorp.com