2020-02-05 - Yealink RPS Service Policy Update
What Changes Have Been Made?
Any devices that connect to RPS for the second time from a different IP address than they originally connected from may be blocked.
Am I Affected?
If your phones were provisioned for the first time using RPS onsite, you are not affected. This includes new deployments purchased from another vendor or existing equipment provisioned via RPS. If you provisioned your phones using RPS offsite, purchased hardware through your provider that was already pre-provisioned, or have moved you are affected.
How Does This Impact My Service?
Affected customers will not experience any loss in service. However, if you need to factory reset your phones for any reason, the device may be blocked from RPS and will not provision automatically. This does not affect manual provisioning or DHCP options in any way.
How Do I Fix This?
Existing Clients - Channel partners can submit tickets with a list of public IP addresses for their clients. OIT will whitelist each IP address, which will allow the devices to connect to RPS and provision successfully. If you need to factory reset a phone and are unsure whether it is an affected device or not, please submit a ticket with the public IP and we will whitelist it for you.
New Clients - Our onboarding process moving forward will be to request the public IP of any clients purchasing Yealink hardware so we can automatically add them to our RPS whitelist and avoid any future issues.
Resellers - You can find instructions on how to whitelist and unblock your client IPs here
- How to Whitelist an Unblocked Device
- Unblocking a Device