ittchmh / fusionpbx

Automatically exported from code.google.com/p/fusionpbx
0 stars 0 forks source link

Park Extension not correctly working on "Active Extension" page #275

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Call from external to some internal extension
2. Valet park the external call to *6000
3. No parked extension is shown on page "Active Extension", if there are no 
internal extensions active
4. Start internal call from internal extension A to B. The parked call appears 
again.

What is the expected output? What do you see instead?
See the parked call all the time even without active internal extensions.

What version of the product are you using? On what operating system?
fusionpbx from svn (rev 2826)

Please provide any additional information below.

I find it extremely difficult to debug as there is no or only conflicting 
documentation about many features in fusionpbx.

My install of fusionpbx did not add any *6000 valet park extensions at all. The 
docs say it is in /var/www/fusionpbx/includes/install/dialplan/default.xml, but 
that file does not seem to be used any more. Instead I find many small 
snipplets in dialplan/${v_domain}, which, however, do not provide valet_parking.

So I added the valet_park_in and valet_park_out myself. This is working 
correctly. Only problem is in the "Active extensions" screen as described above.

I tried to debug  
/var/www/fusionpbx/app/calls_active/v_calls_active_extensions_inc.php, but that 
was very difficult. I seem to have got it working correctly now, but maybe the 
patch is not the best, but maybe it gives an indication of what I have done.

Original issue reported on code.google.com by MichaelB...@gmail.com on 29 Jun 2012 at 12:40

Attachments:

GoogleCodeExporter commented 9 years ago
Are you using BLF with the valet park?

Original comment by markjcrane@gmail.com on 2 Jul 2012 at 10:09

GoogleCodeExporter commented 9 years ago
Hi Marc

No, I am not using BLF at the moment (although planned for the future).

This bug is purely about the fusionpbx gui. So all action is performed on the 
gui on the active extensions tab.

P.S.: Strange freeswitch behaviour to announce the paking slot to the parked 
leg instead of the the one that has performed the parking. Asterisk inform the 
leg that has requested the parking action about the slot so the guy can unpark 
the call again. With freeswitch the parked guy gets informed on which slot he 
is now parked. Really strange...

Original comment by MichaelB...@gmail.com on 3 Jul 2012 at 5:24

GoogleCodeExporter commented 9 years ago
I'm experiencing the same thing with normal *5900 park.   Parking works and 
we're able to retrieve the call however the Active Extensions page does not 
display the call as being parked.

Original comment by d...@helia.ca on 3 Jul 2012 at 5:39

GoogleCodeExporter commented 9 years ago
I'm not certain I want active extensions to use valet park. I made an 
alternative call park before valet park had presence support. My version 
actually works better at keeping BLF light on until the caller is out of call 
park. My call park is in the dialplan by default in FusionPBX. If we don't use 
mod_valet then I will need to adjust the active extensions page to use my 
version.

Original comment by markjcrane@gmail.com on 11 Jul 2012 at 2:37

GoogleCodeExporter commented 9 years ago
I encountered problem with valet parking but I managed with a workaround:
1. Enabled park_in (changed *5900 to 5900)
2. Enabled park_out (changed to match ^590[123]$)

This line in park.lua doesn't work with *5900 and *590[123]:
90:    park_extension_end = ((park_extension+park_range)-1);  

Original comment by nandy1...@gmail.com on 2 Apr 2014 at 6:42

GoogleCodeExporter commented 9 years ago
Active extensions needs to be rebuilt.

Original comment by markjcrane@gmail.com on 30 Apr 2014 at 4:27

GoogleCodeExporter commented 9 years ago

Original comment by ewsamu...@gmail.com on 24 Mar 2015 at 11:20