Skip to main content

CALLPICKUPMARK loses global scope...

Posted by phauwert on Tue, 12/08/2009

When setting a feature code to use the TL-Directed-CallPickup script, we notice that PICKUPMARK is empty... Yes.. we are invoking the feature code while another extension IS ringing. You can see the PICKUPMARK being set from TL-STDEXTEN but Directed Call Pickup doesn't seem to see it. Any thoughts?


Submitted by eeman on Wed, 12/09/2009 Permalink

provide more info, for all i know you're running the exact version of asterisk that has a problem with directed call pickup

Submitted by phauwert on Thu, 12/10/2009 Permalink

Running 1.4.26-RC5. Watching asterisk monitor... On dialed extension stdexten script shows __PICKUPMARK being set with (some ext - some tenant) which is correct...

However when dialing *88NNN to pick it up the TL-Directed-Callpickup script echos back "PICKUPMARK" instead of what should have been the globally set value of PICKUPMARK.

exten => s,n,Pickup(${MACRO_EXTEN:${ARG1}}${TL_DASH}${tenant}@PICKUPMARK)

Hope this helps.

Submitted by eeman on Thu, 12/10/2009 Permalink

then you probably have a bad version of asterisk.. you shouldnt be using release candidates anyway. Upgrade to 1.4.27.1 and see if the problem continues.

Submitted by phauwert on Fri, 12/11/2009 Permalink

Upgraded to 1.4.28.1 thanks.... Works now.