** PARKING LOT PROBLEM ** version 2.4
When a call is parked to extension 70 the system fails to announce the actual parking lot location. When the call is parked; all you here is MOH, yet the call is retrivable by picking the first position, in this case extension 71.
This problem exists on 2 seperate boxes; 1 production with 100+ extensions and one test with just a few extensions. each was installed clean with the ISO's. The test box also has the latest YUM.
Assistance would be wonderful, please test this on your units and provide me with some feedback.
Regards,
Lance - Tampa, Bay FL.
Bug report has been posted.
We are having the same exact problem. You can park the call and instead of reading back the parking location it goes straight to the Music on Hold. If you guess the right park number you can pick the call up. I am just about ready to go live with this system and this is the one feature that I cannot get figured out so any help would be greatly appreciated.
I have a Clean 2.4 ISO box. No YUM updates since it went on line Jan 3rd. (Only SIP trunks and Linsys SPA FXO Adapters).
I set the Parking Lot through FreePBX to Ext 7000 since all my extensions are four digits. An the Calls get parked in 7001-7009. An everything has been working fine for us as of today.
Can you try setting you Parking lot to the Same length of your extensions or are you using two digit extensions since you are using Extension 70 to Park.?
Kerry
To my Knowledge Parking a call is the only reliable way to pickup a call if your not at your desk. This feature is not working I believe is called a ShowStopper, waiting, hopefull, maybe respectfully is not acceptible. There must be something we can do considering Digium has already fixed the issue.
I am using the ISO for the 2.4 base Release it shows;
Asterisk 1.4.16-1 RPM by vc-rpms@voipconsulting.nl, Copyright (C) 1999 - 2007 Digium, Inc. and others.
Created by Mark Spencer
I have a system running 2.4.0 + asterisk 1.4.16 - park does anounce the slot, but then launches into moh afterwards, this is a bit confusing to users as it leaves them guessing as to what is going on if they werent listening closely, a hangup would most likely be more appropriate as has happened in the past, but it works for me.
I didnt need any of the patches in 1.4.17 (T1 drops was the only reason to upgrade), so I left it unbroke and didnt fix it ;)
on to a possible fix (meaning not tested)- you can try removing asterisk:
yum remove asterisk
then copy the rpm files from the original 2.4.0 iso found in the trixbox.tar.gz
rpm -ihv asterisk-1.4.16-1.i386.rpm
rpm -ihv asterisk-addons-1.4.4-13.491.i386.rpm
I am not sure if the above is the exact version numbers you will see in the trixbox tar on the cd, from scratching around on my system here thats what I find. - make sure to make a backup in freepbx at the very least (and copy it off).
Here we are running 1.4.17-1 RPM by vc-rpms@voipconsulting.nl built by root @ localhost.localdomain on a i686 running Linux on 2008-01-04 08:28:26 UTC
Any idea when the build with the fix for this issue will be released?
{Expletive}, are you kidding me? I have the same problem on a 2.4.0.2 build, went into production today. I thought I had just missed a configuration setting...
This is really going to make my customer (who is migrating from a key system with SLA) really happy--now they can't reliably retrieve calls from another extension. Nice.
I really like tb, but these niggling "little" issues are starting to get to me...
My Box at TB 2.4.0 & Asterisk 1.4.16 seems solid, but I have no analog on it at all. All traffic is SIPConnect to CBeyond networks or SIP to a SPA400.
Next / New box coming up is going to have a 4 T card in it and I expect some issues based on postings here.
Has anyone tried the 1.4.18 build yet ?
--------------------------
Are the instructions posted above by jahyde the ones you used to downgrade to 1.4.16-1?
Kerry, could you maybe have 1.4.16-1 put in the Package Manager repository, or is it just as easy to downgrade via command line?
Any info on when an Asterisk version with the patch fixed will be available?
I have the parking lot installed and it is working fine when I park a call the system announces the slot ie 71 that the call is placed in. I am not seeing this issue myself. Version I am running Asterisk 1.4.17-1 RPM by vc-rpms@voipconsulting.nl built by root @ localhost.localdomain on a i686 running Linux on 2008-01-04 08:28:26 UTC
I also have a Sangoma A101 PRI PCI adapter
Jim
I have the lates 2.4.2 with Asterisk 1.4.17-1 and after some testing I have found the following and am wondering if others see the same. The receptionist has a Aastra 55i with sidecar. In the test I called in and had her try the following ways to park the call.
1. use the softkey I setup for parking to park the call - call parked but it did not say the park location.
2. use the phones transfer key to park the call -> transfer 100 (we use 100 - 105 for parking lot) - again the call parked but no announcement.
3. had her use ## 100 - parked call and announced the location
perhaps those who know more than me can use info.
Mike
Manually dialing ##70# works, but I cannot setup a softkey to dial "##70#" while in a call in an Aastra 480i config file.
The only softkey config that works for parking (in my experience) is:
softkey2 type: park
softkey2 label: "Park"
softkey2 value: asterisk;70 #
softkey2 line: 1 (I don't know if this is needed, or what it does)
softkey2 states: connected
How can I setup a softkey that will dial "##70#" while in a call, without having to press "Xfer" first?
I used the web interface and set the type for speeddial value of ##70
yours would be like this:
softkey2 type: speeddial
softkey2 label: "Park"
softkey2 value: ##70
softkey2 line: 1
softkey2 states: connected
on my 9113i in the config file
prgkey1 type: speeddial
prgkey1 label: Park
prgkey1 value: ##100 (This is my parking lot number)
see if this works
When I set the softkey that way:
softkey2 type: speeddial
softkey2 label: "Park"
softkey2 value: ##70
softkey2 line: 1
softkey2 states: connected
and press the "Park" softkey during a call, nothing happens.
I've commented out the "softkey2 line: 1", and it made no difference. I've tried setting the type to "park" (no quotes), and it makes no difference.
Also, if I set the type to speeddial, and the states to include idle, the softkey will show up when the phone is idle. If I then press the softkey (during idle), only one "#" symbol will be dialed, then that's it.
I tested the softkey setup on our receptionists 55i and found the softkey doesn't work but using one of the programable keys does, I don't know if the 480i has programmable keys in the web UI but if it does try setting one of those as a speeddial for ##70. also I have the latest firmware on the 55i.
Hope this helps
lancekoster: Could you be more specific, please? For WHAT to work? Parking? Setting the softkeys to dial "##70#"?
SchlingBlade: What method did you use? Softkey? Manually pressing "##70#"? Pressing Transfer > 70? What model phone?
garnerm: The 480i has only softkeys, not programmable ones.
jahyde: I'm somewhat a noob, but not THAT much of a noob! (No offense taken.)
To reiterate my issue: The programmable softkey will park the call, if set to: asterisk; 70 #, but will not read back the parking lot position. Hitting Xfer > 70 will park the call, but not read back the parking lot position. Hitting ##70# parks the call, and reads the extension number. I would love to set a softkey to park the call using ##70#, but it won't work: Nothing happens if I set a softkey to speeddial or park, with the value as "##70#" will do nothing if pressed during a call.
I made a new topic in the Aastra forum:
http://www.trixbox.org/forums/vendor-moderated-forums/aastra-endp...
The ## transfer feature seems to work fine. I always get the extension announced. The Grandstream phones I use (GXP-2000/2020) do not send anything from the speed dials while in call. This seems to somewhat make sense. So I have to manually dial ## (far too quickly for an old guy).
If you transfer using the transfer button on the phone, the transfer to park occurs and the phone hangs up. Asterisk finishes working through the dial macro with a zombie SIP connection. I actually see the extension digits announced after the phone hangs up.
Rev
jahyde:
Yes, that's how I have it setup. What I want to know is if I can set the softkey to dial it as "##70#" instead of "asterisk;70". With "asterisk;70", the parking lot number is not read back when parking the call. When I manually enter "##70" on the keypad, the parking lot number is read. I would like to program a softkey to dial "##70" so that I can hear the parking lot number.
This is an issue with the newest Asterisk version (1.4.17-1). I'm just trying to make it easier for my client to use the parking lot--we've been avoiding it because of this issue.
sorry that didnt work - i will post in your other thread so to not fill this one
http://www.trixbox.org/forums/vendor-moderated-forums/aastra-endp...
For the Aastra 480i, you must put the following in your aastra.cfg or the
softkey10 type: speeddial
softkey10 label: "Park"
softkey10 value: "##70#"
Obviously, the softkey10 can be any #, ie softkey2, softkey3, whatever.
I hope this helps someone else...
Jeff
Using ##70 works fine for my client to put the call into park and hear were it went, but he *really* needs to see the busy LED on his Grandstream 2000/2020s lit. I programmed the BLF keys, but they do not light for the park feature.
Is this broken in trixbox 2.4.2?
Are there *any* work around?
What stable version of trixbox did this work in (just one T1, no analog)? This is a must-have feature for this client...
Thanks!
Artie
Artie,
I have seen a few posts here and there on your question. One is in an article on presence: http://www.voip-info.org/wiki/view/Asterisk+presence
It sounds like a matter of supplying the hints for the parking extensions. I have not tried this.
After banging our heads against the wall for a while with this parking problem... It turns out our previous method of parking calls with our Cisco 7960's has some new issue with this build of Trixbox, resulting in not hearing the parkinglot number, and calls being dropped instead of returned after the parking timeout expired.
Our previous method of parking which worked previously was: While on a call - "Transfer" -> 70 -> "Dial" -> *listen for extension* -> "Transfer"
(Trixbox 2.4.0)
Now I've instructed users to: While on a call - Dial "##70#" -> *Listen for Extension*
(Trixbox 2.4.2)
Hopfully this will help with some debugging.


Member Since:
2007-04-20