Found when using autoprovisioning templates for Yealinks, it was breaking the Directed Call Pickup feature when pressing a ringing extensions BLF key, found that removing these lines restored functionality.
account.1.dialoginfo_callpickup = 1
features.pickup.direct_pickup_code = *8
features.pickup.direct_pickup_enable = 1
features.pickup.blf_visual_enable = 1
features.pickup.group_pickup_code = *81
features.pickup.group_pickup_enable = 1
Hi Erik, thanks for helping
Hi Erik, thanks for helping. Gotta love the 40 year old installs :( I attribute to me including Group pickup as being exhausted.
I tried replacing Pickup with PickupChan and it seemed to break it altogether (BLF & dialing *8ext# manually) so I'm assuming it may need more changes?
Here's what I see before making the changes to script calling ext 103 from ext 105 and attempted to do a directed call pickup via BLF with ext 104 that has a DSS key programmed..
> Extension Changed 103[subscriptions-demo] new state Ringing for Notify User 104-demo
-- Called SIP/103-demo
-- SIP/103-demo-0000a146 is ringing
> Extension Changed 103[subscriptions-demo] new state Ringing for Notify User 104-demo
[2018-01-30 13:43:19] NOTICE[2314][C-00002bfe]: chan_sip.c:25778 handle_request_invite: Trying to pick up 103@subscriptions-demo
[2018-01-30 13:43:19] NOTICE[2314][C-00002bfe]: chan_sip.c:25778 handle_request_invite: Trying to pick up 103@subscriptions-demo
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
> Extension Changed 104[subscriptions-demo] new state InUse for Notify User 103-demo
[2018-01-30 13:43:19] NOTICE[2314][C-00002bfe]: app_directed_pickup.c:302 pickup_exec: No target channel found for 103@subscriptions-demo.
> Extension Changed 104[subscriptions-demo] new state Idle for Notify User 103-demo (queued)
here is the script
here is the script
[bgnv-directed-call-pickup]
use=feature
friendlyname=Directed call pickup
description
Pickup ringing extension by dialing a feature code plus extension
args=1,Invoking feature code length,text,false,true
body
exten => s,1,PickupChan(SIP/${MACRO_EXTEN:${ARG1}}${TL_DASH}${tenant})
exten => s,n,Playback(privacy-incorrect)
exten => s,n,Hangup
I used the new script and
I used the new script and still receiving busy tone when trying to press the ringing BLF. I'm wondering if I'm missing something else.
One thing I notice is that it shows "103" on the screen after pressing it, when it would say "*8103" after removing dialoginfo_callpickup & features.pickup.enable=1
[2018-01-30 15:41:30] NOTICE[2314][C-00002fd7]: chan_sip.c:25778 handle_request_invite: Trying to pick up 103@subscriptions-demo
[2018-01-30 15:41:30] NOTICE[2314][C-00002fd7]: chan_sip.c:25778 handle_request_invite: Trying to pick up 103@subscriptions-demo
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
[2018-01-30 15:41:30] NOTICE[2314][C-00002fd7]: app_directed_pickup.c:302 pickup_exec: No target channel found for 103@subscriptions-demo.
> Extension Changed 104[subscriptions-demo] new state InUse for Notify User 103-demo
> Extension Changed 104[subscriptions-demo] new state Idle for Notify User 103-demo (queued)
make sure you 'core set
make sure you 'core set verbose 3' because im not seeing the string being dialed
Its set to 3, I see a
Its set to 3, I see a 'declined' and get a busy tone on the yealink I'm pushing the BLF dss button on that's assigned to 103.
-- Called SIP/103-demo
-- SIP/103-demo-0000b707 is ringing
[2018-01-30 17:09:01] NOTICE[2314][C-0000321d]: chan_sip.c:25778 handle_request_invite: Trying to pick up 103@subscriptions-demo
[2018-01-30 17:09:01] NOTICE[2314][C-0000321d]: chan_sip.c:25778 handle_request_invite: Trying to pick up 103@subscriptions-demo
== Using SIP RTP TOS bits 184
== Using SIP RTP CoS mark 5
[2018-01-30 17:09:01] NOTICE[2314][C-0000321d]: app_directed_pickup.c:302 pickup_exec: No target channel found for 103@subscriptions-demo.
We encountered the same issue
We encountered the same issue with directed call pickup on Yealink phones (receiving 'declined', busy tone and not seeing *8 prepended to the extension. After much experimentation we discovered that disabling Dialog Info Call Pickup fixed the issue. Seems like a Yealink issue.
Change the following from 1 to 0 in yealink_line.cfg & yealink_dect_line.cfg:
account.${LINE}.dialoginfo_callpickup = 0
No need to remove the other settings...
Thanks! Erik had e-mailed me
Thanks! Erik had e-mailed me this but I was too sick to function. Just tested today and worked perfectly.
you probably do not have the correct script defined for directed call pickup. _*8. need to use PickupChan() and NOT Pickup(). This feature was fully tested. Deleting those entries will invalidate the ability to use pickup for phones NOT part of your BLF list. Do you have a dialplan dump of what happens with those still defined and you press the ringing line?
and before you ask WHY the wrong script is the default for directed call pickup, it was to maintain backward compatibility from 40yr old installations. It has not been the correct method since Asterisk 1.6.2. Group pickup has NOTHING to do with directed call pickup. Why would you remove that?