Yealink
      Back to home
      1. Luminate Knowledge Base
      2. HARDWARE
      3. Yealink

      Yealink - General Information

      This article includes general information about provisioning Yealink devices on the platform.

      LOGO-yealink - Atlona® AV Solutions – Commercial & Education

      Provisionable Devices

      There are three different Yealink code structures you'll see when making/editing a Yealink device definition.

      • Yealink - this is known as M1 syntax by Yealink. It applies to T2x devices running 60 series firmware or older. It is no longer maintained.
      • Yealink2 - this is known as M2 syntax by Yealink. It applies to the original T3x devices introduced around 2010. It is no longer maintained.
      • Yealink3 - this is known as M7 syntax by Yealink. This format is maintained and the only SNAPbuilder enabled Yealink syntax. It applies to the following devices
        • T2x devices with 71 series or higher firmware
        • the new T3x series (introduced in 2020)
        • T4x devices
        • T5x devices
        • CP conference phones
        • W series DECT stations.

      Compatibility Notes

      • Yealink firmware versions below 81 do not support Retry After xxx in the 503 message and will not failover in that condition. Set Core system Parameter Send503RetryAfter to 0 for compatibility with older Yealink firmware.
      • Yealink fallback methods of geo-redundancy support only limited functionality (no BLF, MWI). As such SRV may be the preferable geo-redundancy method.

      Become a Yealink Partner

      http://www.yealink.com/partner.html

      Provisioning URL

      The following methods can be used to point the devices to the Endpoints Module.

      1. Use the Luminate Provisioning Tool.
      2. Log into the device's admin interface and navigate to Settings > Auto Provision. Set the Server URL field to http://portal.luminatewholesale.com/cfg, then set the username and password.
      3. Use DHCP options 159 or 160.
      4. Use Yealink RPS - contact your Yealink partner manager to sign up for Yealink RPS.

      BLF and Directory

      • Phone linekeys and sidecars are provisionable via the Builder.
      • Directories are provisionable via the Builder.

      Shared Line Appearance (SLA)

      • The Endpoints Module can configure SLA on the Yealink.
      • SLA testing was not performed with recent device firmware.

      Geo-Redundancy

      • By default, Yealink uses dual registration for geo-redundancy.
      • The following overrides are recommended to enable BLF and MWI to function after failover (note that these are set by default):
      account.1.outbound_proxy.1.failback_subscribe.enable="1"
      account.1.sip_server.1.failback_mode="2"
      account.1.sip_server.1.only_signal_with_registered="1"

      Transport

      • TCP, UDP, and TLS transport can be selected.
      • If you're using SRV with TLS ensure you have a DNS Record like _sips._tls.core1.acmecorp.com. (note the _sips where many other devices use _sip)
      • To enable SRTP use the override account.X.srtp_encryption where X is the registration index and value 0 is off, 1 is optional, 2 is mandatory.