- Joined
- Mar 31, 2025
- Messages
- 7
- Reaction score
- 3
We are experiencing a persistent issue where the “Hold” button in the 3CX Webclient remains greyed out, even though the device is fully provisioned and all relevant control settings are enabled.
action_uri.allow_ip_list = any
features.pickup_directed_call.enable = 1
Setup Details:
- 3CX Version: v20 (latest build)
- Phones tested:
- Yealink T58W (150.87.0.15)
- Yealink T46S (66.86.0.15)
- Provisioning:
- Via SBC (custom template applied manually via Extension > Phone Provisioning)
- Factory reset + clean provisioning
- Remote Control + SIP Notify = enabled
- Webclient device:
- Shows “Deskphone” selected correctly
Confirmed Working:
- Calls and transfers from Webclient work
- Phone responds to SIP (manual Hold on device works)
- Calls show correctly in Webclient with control buttons
Issue:
- “Hold” button stays grey in all cases
- PCAP trace confirms:
→ No SIP NOTIFY is sent at all when “Hold” is clicked
→ Therefore: the phone never receives the command
Additional Notes:
- Custom provisioning template includes:
action_uri.allow_ip_list = any
features.pickup_directed_call.enable = 1
- Confirmed applied and active
- No errors in 3CX logs (no Notify failures or blocked events)
- Confirmed from PCAP: no SIP NOTIFY packets sent during Hold action
- Reproduced on multiple models and extensions, using fresh provisioning
Our ask:
- Is this a known limitation or regression in Webclient CTI/SIP Notify control?
- Is this specific to Yealink firmware 150.87.x.x (T58W) or more general?
- Can Webclient call control be forced or unlocked manually per extension/device?