Today’s article is a big one: how to troubleshoot registration issues with your CBSD. Please see below for more details.
My device isn’t registering
Troubleshooting registration issues starts with identifying which method you are using to register your CBSD. There are two methods to register a CBSD with the SAS: Single-step registration, and Multi-step registration. A single-step registration request contains all the information the SAS requires to register a device in the registration request itself. With multi-step registration, you first use the SAS Portal to create a device, and then send a registration request from the CBSD to complete the registration process.
Please note that there is no way to register a CBSD using just the SAS Portal.
Single-step registration is a functionality that is usually built into the CBSD itself. If your attempts at single-step registration are unsuccessful, it is likely that one or more fields have incorrect information. Please make sure that your user ID field contains the user ID your organization used during your onboarding to Google SAS or that you have used historically, not the CPI ID that was provided to your CPI when they completed their training program. Please also make sure that your CPI is using the CPI ID they received from their Training Program Administrator (TPA) in the CPI ID field and not their email address. There should be no additional whitespace in any of the parameters in your CBSD’s User interfaceI. If the SAS is returning a 103 error indicating that the CPI credentials are invalid, please have your CPI reach out to their TPA to confirm that their CPI credentials are valid and are being used correctly.
If you are using a combination of the SAS Portal and registration requests from the CBSD for device registration, you are using multi-step registration. The first thing to check when troubleshooting multistep registration is confirming that your CBSD is signed in the SAS Portal. If your device’s config state is listed as “Pending Registration”, the CBSD configuration has been signed. If the status is “Draft” or “Ready for CPI”, the CBSD configuration has not yet been signed by a CPI. The CBSD will not be able to be registered until the CBSD configuration has been signed. If your CBSD has been signed in the SAS Portal, but it is still having issues registering, first make sure that your CBSD is sending registration requests. A CBSD that does not send a registration request to the SAS cannot be registered. There are 3 common reasons why your CBSD would fail to register even after sending registration requests to the SAS:
- The requests were sent to the wrong URL.
- Your device was not signed in the SAS Portal before the registration request was sent. Try sending a new registration request from the CBSD to test for this.
- There is a mismatch between the information in the SAS Portal and the information in the registration request. The user ID, FCC ID, and serial number need to match exactly in both the SAS Portal and the registration request. If any of those three parameters mismatch, the SAS cannot merge the information in the SAS Portal with the registration request. These mismatches are usually due to typos. Common typos include:
- Including additional whitespace in the user ID sent in the registration request
- Including additional whitespace in the Serial Number in the SAS Portal
- Including additional whitespace in the FCC ID in the SAS Portal
- Providing a CPI ID as the user ID in the registration request.
- Providing an email address as the user ID in the registration request
We recommend entering information into your CBSD’s UI character by character to avoid accidentally including additional whitespace in any of the parameters. If you are certain that all the information in the registration request exactly matches what is in the SAS Portal and your registration requests are still failing, try deleting the CBSD from the SAS Portal and re-creating it.
For more information about registering a device with Google’s SAS, please see the following Help Center articles: