If an IllyVoIP incoming number reaches a Yealink phone, a supported phone can reject calls presented without caller identity. This guide uses the documented Local Anonymous Rejection setting on the SIP-T73U. Check your exact model’s documentation if its controls differ.
This is an endpoint setting. It is not an IllyVoIP account-wide spam filter, and it does not block every unwanted caller. An unwanted call that presents a number may still pass, while a legitimate caller who withholds their identity may be rejected.
1. Confirm the incoming route before changing the phone
- Check that the IllyVoIP number is active and its saved destination reaches this phone’s SIP line.
- Make an agreed baseline incoming test with an identified caller. Confirm that this phone rings normally.
- Identify the account slot on the Yealink that receives those calls. On a phone with several accounts, changing the wrong slot may have no effect on your IllyVoIP line.
- Confirm you have permission to administer the device. If provisioning manages it centrally, arrange the setting with its administrator.
If ordinary incoming calls already fail, resolve that first. Otherwise you cannot tell whether a later silent phone means anonymous rejection worked or the existing incoming route is still broken. Check Do Not Disturb separately: that is a different control.
2. Enable the documented local setting
- Open the phone’s local web interface from the trusted management network and sign in as its administrator.
- For the SIP-T73U, open Account → Basic and choose the account used for IllyVoIP.
- Find Local Anonymous Rejection, enable it and save the change.
- Reopen the same account to confirm the saved value. Keep a note of its previous setting so you can reverse the change.
Yealink documents local rejection separately from a server-controlled mode. Do not copy activation codes from another telephone provider or assume IllyVoIP offers an equivalent server feature. The local phone can respond with SIP 433 when rejecting an anonymous call; the caller’s eventual experience also depends on the route around that phone.
3. Test anonymous and identified calls separately
- Arrange a test with someone who can deliberately withhold their caller identity through their own supported service. Do not use a production customer as an unannounced test.
- Call the IllyVoIP number and observe this exact endpoint. Note whether it rings and what the caller experiences.
- Make a second call with a normal presented identity to check that expected calls still ring.
- If your number uses a queue, forwarding or another workflow, check that workflow’s behavior too. Rejection at one endpoint does not prove every other endpoint will remain silent.
Keep the tests brief and review applicable charges. A caller’s name being absent is not necessarily the same as their telephone identity being withheld. Record the actual presentation rather than treating every unfamiliar number as anonymous.
4. Reverse or troubleshoot the result
If legitimate callers need to reach you with withheld identity, return to the same account setting, restore its previous value and save. Repeat the identified-call baseline and, if appropriate, the anonymous test. Do not change caller ID, outbound country restrictions or purchased-number routing just to undo a local rejection setting.
- Anonymous calls still ring: verify the model, selected account, saved setting and whether the incoming call actually has a presented identity.
- All calls fail: check registration, incoming routing and Do Not Disturb; do not assume this selective setting explains every failure.
- Another device rings: inspect the number’s broader route and other endpoints.
- The setting reverts: ask whether an administrator’s provisioning profile owns it.
For Support, include the model and firmware, test time, public call reference and whether the caller deliberately withheld identity. Do not send passwords or unmasked phone configuration exports. This guide describes a documented device feature used on an IllyVoIP route, not a certified result for every phone or network.
Related guides
- Set up a Yealink desk phone with IllyVoIP
- Check the destination when your IllyVoIP number does not ring
- Turn off Do Not Disturb on a Yealink T54W and check incoming IllyVoIP calls
- How to contact Support and request test credit
Reference
Current instructions and technical reference: Yealink model documentation.
Reviewed 12 October 2026 against the current IllyVoIP controls, implementation and applicable references. Available options depend on account permissions and service state.