FOP2 Community Forum

Hi Nicolás, Thank you for the response and tip. -however I understand this in regards to assigning the users to the group - and is being done via the freepbx module (fopadmin 1.2.6) using fop2 version http://fop2.com/file.php?file=20. The button and user scripts run fine and if I really wanted to I could just not use the fop2admin and edit how I like.. But in this case the client of mine wishes to use the fop2admin and I havent had this problem with it in the past. You would think its a mismatch version issue, but I'm using what is recommended. --One thing I can note that is different is that this client is using the demo version currently - this hickup has stalled them from ordering at this time. Let me ask, the registration has no bearing on using the group display feature does it? (if everything is under 15 buttons) Because as is when we use the fop2admin - the whole page is blank. *only when we use fop2admin (versions of everything is above) Kind Regards and Thanks tuketu

Parking lot support is implemented in 2.10. You need to create a context in asterisk's dialplan: [fop2-park] exten => _X.,1,Set(ARRAY(RETURN_EXTENSION,RETURN_CONTEXT)=${CUT(EXTEN,:,1)}\,${CUT(EXTEN,:,2)}) exten => _X.,n,ParkAndAnnounce(PARKED,,Console/dsp,${RETURN_CONTEXT},${RETURN_EXTENSION},1) exten => _X.,n,Goto(${RETURN_CONTEXT},${RETURN_EXTENSION},1) exten => _X.,n,Hangup The button definition for parking is like this: [PARK/default] type=park extension=700 label=Parking context=parkedcalls

Found the answer in the post below "DAHDI Trunks" - just followed the instructions, restarted fop2 using 'service fop2 restart' (on CentOS) and all is happy and good now.