Zoom Phone Integration

Add an integration between Phonism and Zoom.

Zoom integration

Phonism's integration with Zoom simplifies device management for VoIP phones, maintaining seamless synchronization of hierarchy, users, phones, and VoIP credentials across both platforms. The integration optimizes device configurations for Zoom operations, ensuring smooth functionality and enhanced user experience.

Use this guide to add an integration between Phonism and Zoom. 

Feature prerequisites

You must have an active Phonism account with the hierarch feature and account-level super admin user access.

Your Zoom account needs to have “Other” phone support enabled.  This must be requested of your Zoom account manager via email. Once enabled, complete the Zoom Onboard process at http://app.phonism.com/integration/zoom . 

ADD ZOOM INTEGRATION100

Open

1. Search for the Phonism integration on the Zoom Marketplace click

2. Sign-in to your Zoom account and authorize the integration.

3. When redirected to Phonism, log in and continue onboarding by following the on-screen wizard. The wizard guides you through:

   1. Log in to Phonism.

   2. Check for Zoom Authorization.

   3. Check permissions available in Zoom.

   4. Summarize the assets to be synchronized.

   5. Finalize setup and begin synchronization.

Open

Once the integration is configured, Phonism begins synchronizing assets in a new branch of your Phonism Hierarchy and automatically creates new tenants within that branch, representing each one of your Zoom sites. Zoom Phone users and devices are created in the corresponding tenants in Phonism.

TWO-WAY SYNC OF SITES, USERS, AND ZOOM PHONE DEVICES

Assets created or deleted in Zoom are automatically created or deleted in Phonism.

• Creating a new site in Zoom results in a new tenant being created as part of your Zoom hierarchy in Phonism.

• New Zoom Phone users have an equivalent Phonism user created at their tenant.

• New Zoom Phone devices added as “Other” in Zoom are added in Phonism at their tenant.

• New Phonism tags are available that can be configured to be dynamically resolved for a particular phone and its assigned Zoom Phone user. These values are ingested and mapped from Zoom Phone.

// Where X is the Line Number (e.g. line 2)

line.X.authorization_id

line.X.sip_server_1

line.X.sip_server_1_port

line.X.outbound_proxy_1

line.X.outbound_proxy_1_port

Assets managed from Phonism are synced to Zoom with the following restrictions:

• No tenant can be created under a Zoom integration domain.

• Any created user appears as pending at Zoom until the user accepts the invitation.

• Zoom admin and owner users can’t be deleted.

• Users can only be assigned to a maximum of three phones.

• VoIP credentials are read only.

• User assignment is required when a phone is created.

• Phones created in Phonism appear as the “Other” device in Zoom Phone.

AUTOMATIC DEVICE CONFIGURATION

For select devices (device list TBD *do we need to add a list here?*), when a Zoom integration is added to your Phonism account, Phonism templates are automatically added at the root of your Zoom integration. These templates are optimized for Zoom service, incorporating best practices and ensuring the device is configured to a ring-ready state. For automatic template application to occur, you must do the following:

1. Navigate to the root of your Zoom Integration in Phonism.

2. Select the Templates tab.

3. Review each template that was automatically imported.

4. Update the template State and set it to Auto Apply so that all relevant devices under this hierarchy will have these templates applied.

APPLY TAGS TO PHONES

Now that the assets are synchronized, create a Phonism template per brand/model(s) as auto-apply, so that the values of the dynamic synchronized tags from Zoom are pushed to the phone’s config.

DEACTIVATE ZOOM INTEGRATION

1. In Phonism, navigate to the Domain where your Zoom integration is.

2. Go to the Integrations tab and select the Trash icon to delete the integration by following the on-screen wizard.

FREQUENTLY ASKED QUESTIONS

Question: What should I do if a new asset is taking a long time to load on the system? 

Answer: Pushing new assets to Zoom may take a few moments, depending on system load. If an asset isn’t created in Zoom within 3-5 minutes from creation in Phonism, contact support.

Question: How are assets mapped between Phonism and Zoom?

Answer: In Phonism, our tenant is the equivalent of a Zoom site. All sites and assets belonging to those sites are mapped to the corresponding tenants in Phonism. 

Question: Why aren’t all of my devices appearing in Phonism?

Answer: Only devices identified as “Other” in Zoom Phone are created in Phonism.

Question: How are assets mapped between Phonism and Zoom?

Answer: In Phonism, our Tenant is the equivalent of a Zoom Site. All Sites and assets belonging to those Site will be mapped to the corresponding Tenants in Phonism.

Question: Does the integration auto-update?

Answer: Yes, Phonism periodically checks for updates from Zoom and syncs any changes.

Question: Can I add sites directly in Phonism?

‍Answer: No, all sites MUST be added in Zoom first.

Question: Can I add users directly in Phonism?

Answer: Yes, users can be added from Phonism and it will be synced on Zoom.

Question: Can I add phones directly in Phonism?

Answer: Yes, phones can be added from Phonism and it will be pushed to Zoom. Can be done by adding manually a single phone, by importing a config file or by a bulk import of CSV file.

Question: Not all of my devices appear in Phonism

Answer: Only devices identified as “Other” in Zoom Phone will be created in Phonism.

REGISTER MITEL PHONES

You can create, upload, and provision SSL certificates so that Mitel phones can successfully register against Zoom Phone over TLS 1.2. This is a requirement for Zoom Phone service. This solution is applicable to all Mitel devices supported in Phonism.

Create a Mitel-compatible certificate for Zoom Phone

1. Download SSL certificates. Download the following SSL Certificates from Zoom Phone's Knowledge Base: some text

   • DigiCert Global Root CA

   • DigiCert Global Root G2

   • DigiCert TLS RSA4096 Root G5

2. Combine certificates. Open a text editor and combine the content of each of the three .pem files you downloaded into a single file. Save this file with a memorable name like zoom_phone_trusted_certs.pem.

Your combined file will look something like this:

-----BEGIN CERTIFICATE-----

MIIDrzCCApegAwIBAgIQCDvgVpBCRrGhdWrJWZHHSjANBgkqhkiG9w0BAQUFADBh

...

-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----

MIIDjjCCAnagAwIBAgIQAzrx5qcRqaC7KGSxHQn65TANBgkqhkiG9w0BAQsFADBh

...

-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----

MIIFZjCCA06gAwIBAgIQCPm0eKj6ftpqMzeJ3nzPijANBgkqhkiG9w0BAQwFADBN

...

-----END CERTIFICATE-----

Upload certificate file in Phonism. In Phonism, navigate to Resources > Assets. Select Add Certificate File to upload your newly created .pem file. 

4. Configure devices for retrieval. Once uploaded, you can configure your devices to retrieve this file from Phonism when provisioning. To configure a Mitel phone or template, follow these steps:some text

   • Set the following setting in either the Phone or Template Custom Configuration: sips trusted certificates: {{zoom_trusted_cert_pem}}.

   • Replace {{zoom_trusted_cert_pem}} with the {{tag}} corresponding to your newly uploaded certificate.

   • This Tag can be found when editing a configuration value in Phonism and selecting the Variables submenu.

This Tag has a pattern of {{AUX.filename.pem}}. Thus, if you named your file zoom_phone_trusted_certs.pem, your tag would look like {{AUX.zoom_phone_trusted_certs.pem}}. 

Select Save on the Phone or Template to commit your changes.

When configuration is generated for your Mitel phone, the device is configured to request and install your uploaded certificate file on next provision.

Mitel Zoom Phone custom configuration

The following custom configuration can be used to configure a Mitel phone for registration on Zoom Phone. This configuration can be used in a Template or Phone in Phonism.

This configuration heavily utilizes Phonism Tags to dynamically inject the correct values for a specific phone. When using this configuration in addition to our Zoom integration, all the tag values for SIP parameters are automatically pulled from Zoom and require no effort on your part. 

Values for automatic resolution via tags include line username, password, SIP server, outbound proxy, and port.

Custom configuration: 

contact rcs: 0

diagnostics: 1

https client method: "TLS 1.2"

https validate certificates: 0

https validate expires: 0

https validate hostname: 0

sip customized codec: payload=9;ptime=30;silsupp=on,payload=8;ptime=30;silsupp=on,payload=0;ptime=30;silsupp=on

sip dial plan: "x+#|xx+*"

sip digit timeout: 3

sip dtmf method: 2

sip line1 auth name: {{line.1.authorization_id}}

sip line1 dtmf method: 2

sip line1 outbound proxy port: {{line.1.outbound_proxy_1_port}}

sip line1 outbound proxy:{{line.1.outbound_proxy_1}}

sip line1 password: {{line.1.password}}

sip line1 proxy ip: {{line.1.sip_server_1}}

sip line1 proxy port: {{line.1.outbound_proxy_1_port}}

sip line1 registrar ip: {{line.1.sip_server_1}}

sip line1 registrar port: {{line.1.outbound_proxy_1_port}}

sip line1 registration period: 90

sip line1 user name: {{line.1.username}}

sip user name: {{line.1.username}}

sip auth name: {{line.1.authorization_id}}

sip outbound proxy port: {{line.1.outbound_proxy_1_port}}

sip outbound proxy: {{line.1.outbound_proxy_1}}

sip password: {{line.1.password}}

sip proxy ip: {{line.1.sip_server_1}}

sip proxy port: {{line.1.outbound_proxy_1_port}}

sip registrar ip: {{line.1.sip_server_1}}

sip registrar port: {{line.1.outbound_proxy_1_port}}

sip rport: 1

sip rtp port: 3000

sip services port: {{line.1.outbound_proxy_1_port}}

sip session timer: 90

sip srtp mode: 1

sip transport protocol: 4

sips persistent tls: 1

sips trusted certificates: {{zoom_trusted_cert_pem}}

sips trusted certificates: {{AUX.zoom_trusted_cert_pem}}

static.trusted_certificates.url = {{AUX.zoom_trusted_cert_pem}}

tcpdump port: 5061

time server1: 1.aastra.pool.ntp.org

time server2: http://2.aastra.pool.ntp.org

time server3: 3.aastra.pool.ntp.org

watchdog enable: 1