Table of Contents

Integrating with Calix Cloud

Mitchell Paul-Soumis Updated by Mitchell Paul-Soumis

Read Time: 11 mins

The native Calix Cloud integration is currently available on a Closed Beta basis. If you would like access to this Beta feature, please reach out to your Client Relations Manager to determine eligibility.

The Calix Cloud integration exists as an automated solution for record synchronization between your Sonar instance and the Calix Cloud suite. With Calix Cloud, you can view monitor and manage a wide range of Customer Premises Equipment, such as initiating reboots and updating firmware, while also having access to intelligent recommendations and tracking for your subscribers based on Calix’s data. Leveraging this data, and the customer data you have in Sonar, can facilitate service upgrades, hardware upselling, and churn prevention.

Prerequisites

Before you get started with the Calix Cloud integration, the relevant permissions need to be enabled to unlock both the visibility and control permissions of this page.

If you're a Super-Admin of your Sonar instance, no permission changes are required for your account. For more information on Roles and Permissions overall, please review this linked article.

Navigate to Settings → Security → Roles and either choose to edit an existing Role or create a new Role. When the next page populates, locate the permissions reflected in the screenshot below and add it if applicable to that Role.

Setting up the Calix Cloud Integration

This integration relies on API communication to your Calix Cloud account. Because of this, setting up the integration requires configuration in your Calix Cloud account, in addition to configuration within Sonar.

The integration requires an API user to exist in your Calix account, so it's crucial that you perform the Calix Cloud setup before trying to set up the Calix Integration in Sonar.

Creating a Calix Cloud User for the Integration and Assigning the API Role

This information is being pulled directly from the Calix Cloud Help documentation. More information on the various pages and user permissions are included there. For assistance generating a Calix user, contact Calix support.
To Create a Calix Cloud user
  1. Go to Administration → Users
  2. Click Add Users
  3. Complete the required fields, and then click Save
To Assign a Role to the New User
  1. Go to Administration > Users.
  2. Click the pencil associated with the user.
  3. In the Add/Delete Roles field, begin typing "API user role" for the role to appear.
  4. Select the "API user role" from the list, and click Add.
  5. Click Save
Allowing the Sonar Instance to Access Your Calix Cloud

With your user created, and the role assigned, we'll now add Sonar as an authorized application.

  1. Log in at developers.calix.com with the newly created API user
  2. Once you're logged in, click on Apps in the top-right corner
  3. Click on Add app
  4. For the Sonar Calix Cloud Integration, the created app requires:
    1. An App Name
    2. An Optional Description
    3. Subscriber Service selected as the API
  5. Click Add app at the bottom of this modal
  6. Wait for authorization from Calix
    The authorization process will vary from account to account, and app to app. For more information on their criteria, please reach out to Calix directly.
  7. Once the app has been approved, return to the developer portal, and click on the app to expand it. Take note of the locations of the X-Calix-ClientID and the Client Secret, as these will be required to complete the integration.

Connecting the Calix Integration in Sonar

The final set up step for this integration is done in Sonar.

  1. Access the integration by going to Settings → Integrations → Calix Cloud Settings, then click on the “Create Calix Cloud Integration” button in the top-right
  2. In the modal that appears, the first of three pages requires information from your Calix-approved app created in the developer portal.
    1. The Enabled checkbox defines whether the integration will operate. If this box is unchecked, synchronization and audits will not occur for this Calix Cloud integration.
    2. The Client ID, which maps to the X-Calix-ClientIDfield shown in the approved app added in your developer portal
    3. The Client Secret, which maps to Client Secret the field shown in the approved app in your developer portal
    4. The Username, which must be the username of the API user you created in your Calix Cloud account
    5. The Password, which must be the password for the API user you created in your Calix cloud account
    6. The Company, which is an optional field. Leaving this field blank will set it to be the default integration for your entire instance. Selecting a company will have the integration run against accounts belonging to the company only.
  3. The second page is where you define which Inventory Model(s) and the field of that model that maps to the associated Calix Device ID field. For more information on Field Mapping, and how Calix works with Sonar inventory devices, check out the Calix Integration: Overview article.
    Whatever field you select for Device ID, that field should be set as a Required Field on the Inventory Model, ensuring that a value is present. Submitting and empty value can result in errors, leading to unknown devices and unmatched records.
    Despite not being specified here, the Inventory Category related to the integration's associated Inventory Models will determine how its Device ID field information is synchronized to the Calix Cloud.
    How your Model Category is Used
    For the integration to inform the "Flow Endpoint Matching Options" record in Calix Cloud, your associated Inventory Models must have a Model Category of either RG or ONT configured. Categories are managed in Settings → Inventory → Categories. Because the Category Name field is user-configured, it is important to match this syntax exactly, or the integration will not pass through the related Device ID data successfully. Before initial sync, you can edit the Name on an existing Category to adhere to the required syntax, or opt to create a new Category, and edit the configured Category association(s) by visiting Inventory → Manage Items, and clicking Edit Details on the existing Models you wish to change.



    The RG Category will map to "Endpoint Matching Option 1" in the Calix Cloud, while ONT will map to "Endpoint Matching Option 2".
  4. The final page of the Calix Cloud Integration set up allows you to map Custom Fields in your Sonar instance that would be associated with your accounts to Subscriber fields in your Calix Cloud. This ensures that any essential information is included in both your Sonar instance and your Calix Cloud instance.
    Only Custom Fields belonging to the “Account” type will be available to select on this page.

Overview

The Calix Cloud integration has two pages, the Overview page that you land on as soon as it's accessed, and the Audit page, that contains details about your Calix Cloud audits and any unmatched accounts.

You can access the Calix Cloud Integration by going to:

  1. Settings
  2. Integrations
  3. Calix Cloud Settings

Landing Page

The Landing Page shows you information related to your existing Calix Cloud integration.

  1. Page Selector: This lets you switch between the Overview page (the visible page), and the Audit Results page.
  2. Filter Panel: This panel contains various filters that can be applied, as well as a text-based search bar, to drill down and limit the data to only what you are interested in viewing. Through the Simple/Advanced toggle, you can perform a simple or advanced search. And through Saved Views, you can select from prepopulated filter configurations to be automatically enabled; along with prepopulated views, this section also holds any private saved views you've created, and any public saved views in your instance. For more information on using filters, take a look at our Filtering: Simple vs Advanced article.
  3. ID: This column will list the ID of the Calix Cloud integration. This value will increment as more integrations are added.
  4. Enabled: This column will provide a “Yes” or “No” for each Calix Cloud Integration you've configured for your instance.
  5. Company: This column will list which company the Calix Cloud integration is associated with.
  6. Audited: This column will provide a “Yes” or “No” for whether the integration has ever been Audited through Sonar.
  7. Last Sync: This column will show the last date and time that a full synchronization to your Calix Cloud account occurred.
    The incremental, automatic synchronizations will not update this column, even though they're occurring every time a change is made to your Sonar accounts.
  8. Sync Status: This column shows the current status of any ongoing Synchronization occurring on the Calix Cloud integration. The Sync Status will update dynamically as it progresses.
  9. Sync Message: This column displays information related to the ongoing Audit or Synchronization.
  10. Action buttons: By default, the Action button will show either “Sync” or “Audit”, depending on what stage you're at in adding a Calix Cloud integration.
    An Audit must be completed on any new Calix Cloud integration before synchronization can occur.

Audit Results

The Audit Results page will show information on any unmatched or mismatched accounts between your Sonar instance and your Calix Cloud account.

If you perform an audit and no results appear on this page, it means there are no errors with the accounts between both platforms.
How Audit Matching Works

When an Audit runs, its purpose is to match the Account records in your Sonar instance to the Subscriber records in the Calix Cloud. If a Sonar Account ID does not match the Calix Subscriber ID, the subscriber that exists on the Calix Cloud will be flagged. If these values match, then the subscriber record doesn't need to be manually linked to an account and will be synced using the detected match.

  1. Page Selector: This lets you switch between the Overview page, and the Audit Results page (the current visible page).
    1. If an Audit was run and had unlinked accounts, the number of accounts will be reflected in the Page selector.
  2. Filter Panel: This panel contains various filters that can be applied, as well as a text-based search bar, to drill down and limit the data to only what you are interested in viewing. Through the Simple/Advanced toggle, you can perform a simple or advanced search. And through Saved Views, you can select from prepopulated filter configurations to be automatically enabled; along with prepopulated views, this section also holds any private saved views you've created, and any public saved views in your instance. For more information on using filters, take a look at our Filtering: Simple vs Advanced article.
  3. ID: This column will list the ID of the Audit result. This value will increment as more audits are run.
  4. Company: This column will list which company the unmatched account is associated with is associated with.
  5. Calix Subscriber ID: The Calix Subscriber ID column will provide you with the address and account ID information of the Calix account details that are not matched to an existing subscriber in Sonar.
  6. Actions: This column allows you to Link an unmatched account from Calix to an existing account in Sonar. You can also expand the side panel using the > arrow to see more details about the unmatched account.

Synchronizing your Data

Performing the first manual Synchronization can be done at any time after an audit is complete. For each integration, manual synchronization is only required to initiate the connection. Further synchronizations will occur routinely and automatically in near real-time. This means that as account or service changes are made in your Sonar instance, they will automatically be reflected in Calix Cloud. There is, however, a caveat to synchronization.

If you configure multiple integrations, such as one for Company A, in addition to your initial, Default integration, then manual synchronization will need to be performed again. This is true of each new integration you add, even if no data exists for the new company yet. Once the manual synchronization has completed, and data is reassigned to the correct company's integration, automatic synchronization will resume.

Ramifications of Synchronizing your Integration

The Calix Cloud Integration is an authoritative connection from Sonar to your Calix Cloud instance. For this reason, it's important to understand how syncing your data can affect your data. Any time you start a sync, you'll receive this warning message:

Warning: You are about to perform a full sync with the Calix Cloud subscriber service. Please confirm that any audited accounts have been reviewed and/or linked. Any unlinked Calix subscriber accounts will be deleted.

What this warning means is that if you have any unmatched data, even if it hasn't been audited, that data will be erased from Calix Cloud. This can have a considerable impact on your service delivery if you aren't careful. For this reason, it's essential to diligently Audit and match any accounts that only show up in your Calix Cloud subscriber service.

Custom Report to Flat File Data Sync (legacy)

If you are looking for documentation on the legacy data sync method, you can review those instructions here.

This approach has officially been replaced by the native API-driven integration. Sonar and Calix highly recommend configuring the native Calix Cloud Integration in favor of the legacy the report method.

If you are currently using this method, switching from the Flat File Data Sync to our native API integration is easy. First, reach out to Calix Support to ensure that the timing of the pipeline transition is handled optimally. Once Calix gives you the all-clear, all you need to do is disable the scheduled SFTP delivery on the associated Looker report, then follow this guide from top to bottom.

How did we do?

Contact