Endpoint activation troubleshooting tips
This guide provides help with troubleshooting during endpoint activation (sometimes referred to as provisioning) . General issues covers issues that can occur with any video endpoint model or method of activation, and Activate Endpoint app (selected Cisco and Poly devices) is relevant for app users.
In addition, there's help with specific vendor-related issues here:
- Cisco/Tandberg endpoints troubleshooting
- Poly/Polycom endpoints troubleshooting
- Avaya endpoints troubleshooting
- Lifesize endpoints troubleshooting
For information, here's an overview of what happens when you activate your video endpoint.
General issues
Here's help with issues that can occur with any video endpoint model or method of activation.
If activation has failed and you're not sure why, or if you just want to check your video endpoint's DNS configuration, follow the guidance below. (If your video endpoint's DNS configuration is incomplete or is not configured to resolve public DNS records, it won't be able to resolve the address for the Pexip provisioning server.)
Step one: Check that your hardware endpoint has DNS servers
First, check that the hardware endpoint has been configured with DNS servers.
If the device already has DNS servers, or if activation fails after adding the new DNS servers, try the next step.
Step two: Check that your device can resolve public DNS records
With DNS servers in place, the next thing to do is test that the device can resolve public DNS records.
For example, on Cisco devices running CE and TC based software, you can run a command that sends some ICMP packets to the Pexip provisioning server. If the response shows that the same number of packets were received as transmitted, this means the device can successfully resolve the Pexip provisioning server address.
To run the command:
- Connect to the device using SSH.
-
Run the command below (prov.vp.vc is the Pexip provisioning server):
systemtools network ping prov.vp.vc
Here’s an example of a successful DNS response:
ping: prov.vp.vc (46.137.184.162), 3 packets, timeout 2 seconds.
3 packets transmitted, 3 received, 0% packet loss, avg rtt 136.430 ms
If the command fails, you need to check that the DNS settings have the correct values.
If you're sure the DNS servers are the correct ones, or if activation fails after correcting the DNS servers, please see step three below.
Step three: Seek help from your local IT administrator
Next, please contact your local IT administrator for help. If they can run the network test from the same VLAN as the endpoint, they can get a report on the network's suitability for provisioning hardware endpoints and this may help diagnose the problem. The network test is available via the Activate Endpoint app and can be run as a standalone feature by any vendor.
See Testing your network for suitability with the Pexip Service.
You may also want to check these other things that can cause provisioning to fail:
- Geo IP filters erroneously filtering out Pexip IP addresses.
- Content or web filters preventing communication.
Customizing activation / provisioning
You can fine tune some of the endpoint configuration values provided by our activation / provisioning service.
Please contact your Pexip authorized support representative to request a change to the following values on a company-wide or endpoint-specific basis:
Cisco only
- Custom Phonebook / Directory
Cisco, Poly Group Series, Poly Trio, Poly G7500, Poly X Series
- Custom NTP Server
Trio, G7500, X Series only
- Endpoint Software Update Custom URL
- Enable Automatic Update (during maintenance hours 04:00 - 06:00)
Activate Endpoint app (selected Cisco and Poly devices)
You can check if your Cisco/Poly device uses the app for activation here: Videoconferencing units compatible with Pexip subscriptions.
If the Activate Endpoint app reaches 70% complete and then times out, this could be because the hardware endpoint can't resolve the address for Pexip's provisioning server. The first thing to check is the DNS configuration.
Step one: Check that your hardware endpoint has DNS servers
First, check that the hardware endpoint has been configured with DNS servers.
If the device already has DNS servers, or if activation fails after adding the new DNS servers, try the next step.
Step two: Check that your device can resolve public DNS records
With DNS servers in place, the next thing to do is test that the device can resolve public DNS records.
For example, on Cisco devices running CE and TC based software, you can run a command that sends some ICMP packets to the Pexip provisioning server. If the response shows that the same number of packets were received as transmitted, this means the device can successfully resolve the Pexip provisioning server address.
To run the command:
- Connect to the device using SSH.
-
Run the command below (prov.vp.vc is the Pexip provisioning server):
systemtools network ping prov.vp.vc
Here’s an example of a successful DNS response:
ping: prov.vp.vc (46.137.184.162), 3 packets, timeout 2 seconds.
3 packets transmitted, 3 received, 0% packet loss, avg rtt 136.430 ms
If the command fails, you need to check that the DNS settings have the correct values.
If you're sure the DNS servers are the correct ones, or if activation fails after correcting the DNS servers, please see step three below.
Step three: Seek help from your local IT administrator
Next, please contact your local IT administrator for help. If they can run the network test from the same VLAN as the endpoint, they can get a report on the network's suitability for provisioning hardware endpoints and this may help diagnose the problem. The network test is available via the Activate Endpoint app and can be run as a standalone feature by any vendor.
See Testing your network for suitability with the Pexip Service.
You may also want to check these other things that can cause provisioning to fail:
- Geo IP filters erroneously filtering out Pexip IP addresses.
- Content or web filters preventing communication.
If you have launched the Activate Endpoint app directly from your desktop, you can view the screens and run the network test, however, activation functionality is not available until you use your unique activation URL to launch the app. This is because launching the app from the URL automatically loads your subscription details into the app.
You can open your unique activation URL (example below) either via an endpoint activation email from Pexip, or a company administrator can do it from MyPages. For more help, please see how to activate your endpoint using the app.
Windows users
If you're using Microsoft Windows and all you can do is scroll through the Activate Endpoint app properties to be able to run the app as administrator. Here's how:
screens, you may need to update the- Close the app and locate its executable file.
- Right click on the binary file and select .
- Select .
- Select and save the changes.
- Re-open the app and re-try. If the problem persists contact your account manager at your local certified Pexip Partner for help.
When the Activate Endpoint app gives the message below, it typically indicates that the video endpoint's firmware needs updating or the unit does not have cryptographic capabilities.
To resolve the issue, please upgrade the firmware and then rerun the Activate Endpoint app. For more information on firmware versions supported for activating endpoints for use with the Pexip Service, see Videoconferencing units compatible with Pexip subscriptions.
If the problem persists after upgrading, please contact your Pexip authorized support representative for help.