Skip to content
Thirdlane

Redirect Servers

Redirect Servers enable Zero Touch Provisioning: a brand-new or factory-reset phone, straight out of the box, automatically finds your provisioning server without anyone typing in a URL. Vendors such as Fanvil, Snom, and Yealink run cloud “redirect” (RPS) services that map a phone’s MAC address to a provisioning server address; on first boot the phone asks the vendor’s redirect service where to provision from, and the vendor points it at your server. This screen registers your provisioning server with those vendor redirect services so you can ship phones directly to remote users and have them configure themselves on power-up - no on-site tech and no manual setup.

Redirect Servers section allows you to configure Redirect Servers provided by the supported phone vendors. Four providers are available: Fanvil, Snom, Yealink RPS (Legacy), and Yealink YMCS. Yealink appears twice because both its original RPS service and its newer YMCS platform are supported; the older one is labelled Legacy in the provider list.

Create/Edit Redirect Server

Name. Assign a unique name to Redirect Server.

Provider. Select the phone manufacturer providing the server.

Description. Add a brief server description.

Provisioning Server Address. Specify the address of our provisioning server, typically the same as the management server where the Configuration Manager is running.

Region. Shown for Yealink YMCS only. Selects the YMCS region your account belongs to - US, EU, or AU.

Access credentials by manufacturer:

Fanvil and Snom: Require a User name and Password. Yealink RPS (Legacy) and Yealink YMCS: Require an Access Key ID and Access Key Secret.

Best practices

  • Obtain vendor RPS credentials first. Each vendor issues the account credentials (username/password for Fanvil and Snom, Access Key ID/Secret for Yealink) that authorize you to manage MAC-to-server mappings; set up that vendor account before configuring the redirect server here.
  • Point phones at a reachable, HTTPS provisioning URL. The Provisioning Server Address is what phones will contact worldwide on first boot, so it must be publicly resolvable and, for security, use HTTPS - phones pull credentials during provisioning.
  • Match the redirect vendor to your hardware. A redirect server only helps phones of that vendor; register one per vendor you deploy.
  • Zero Touch is best for remote/bulk rollouts. For a handful of on-site phones, manual provisioning may be simpler; the payoff of redirect servers grows with distance and device count.
  • Provisioning Settings - the provisioning server, protocols, and credentials phones use once redirected.
  • Phone Models - the model definitions and templates that build each phone’s config.
  • Managed Devices - provision phones for individual users.