Parking Lot Appearance on Yealink T-26

mhorwood

New Member
Joined
Jun 8, 2011
Messages
30
Reaction score
0
Opening myself up for constructive criticism.

Have configured a PBXIAF Purple system for commercial deployment at my Wife's CPA office. Turn up will happen 9-28. They are coming off of a 15 year old Comdial Impression Key system. (Yes I sold them the comdial too)

New PBXIAF Using 13 Yealink t-26 phones, two as attendant stations with ex-39 button expansions. (sorry Ward they would not pop for 6757i's, the Yealink is 1/2 the price, they like the Yealink look.). The Yealink t-26 phone has 13 programmable keys. I am trying to make the transition to a PBX as easy as possible for both them AND me..

I have discovered that the extensions (71-78) used as the parking lot, are programmable on buttons, and asterisk will allow direct access to the parking lot on those buttons. As I see it this will allow for a visual link to the parked calls from all stations. I have programmed the 9 of the 10 keys along the right side of the phone as a DSS for 9 of the most used extensions. The 10th key I have made a dedicated "Transfer to Park" key.

I have programmed the 3 "line" buttons beside the display on all stations, to monitor parking spaces 71,72,73. I have 8 total spaces assigned. I have assigned buttons for all 8 parking spaces on the 2 attendant DSS expansion boxes.

When a call is parked, the Line button assigned to the parking space blinks, which gives them a visual indication that a call is parked there. Most times, on a system with only 10 users, there won't be more than 3 parked calls at a time. it also gives them the ability to continue to say "you have a call on line 1", which is now actually parking space 71, and the other user can pick up the call directly from the button.

Yes there will be issues during tax season when the fourth call gets parked to 74 and there is no visual indication except on the attendant station. Some training will be required.

I will also give optional access to the Flash Operator Panel, where they can see "ALL" that is going on... if they wish.

Call me Naive', but I've researched shared line appearance and I think this has fewer pitfalls. This gives visual indication of parked calls, which i think is the biggest user issue in transition from a key system.

I think this will work, or have I missed something...
I welcome your feedback.

Thanks, Mike Horwood
 
Thanks, The re-park issue having the parking space changing is one that I had not thought through. I plan on training to transfer as much as possible, so as to minimize this impact. Believe it or not, they insist on the calls being answered live person, and are resisting using voicemail... Talk about old school ! .. I am working to transition them into this century... Thanks for your thoughts.
 
I actually love the Yealink phones. I think their sound quality is better than anything out there except perhaps the high-end Cisco phones. And the Yealink can hold its own even with those phones in my purely subjective testing.
 
Thanks Ward. Glad to hear you have good experience with them. I took Aastra & Grandstream for the demo, and they picked the Yealink on looks alone from the cutsheet. My web research yielded no glaringly bad reports, so I took a chance. Have only found one "bug" in the save and restore utility... I now know how to make a Yealink respond to multiple accounts even when the GUI shows only one.... (Had default and reprogram 5 phones from scratch to fix...) thanks for the input.
 
FYI...
The button programming for the T-26 has a Call park pre-configured setting. Using the Pre-Configured setting for call park, the caller hears the parking lot announcement not the Called party. Using the keypad ##70 gives the desired result with the Called party hearing the announcement when they park the call. SO... INSTEAD use DTMF for the button programming with ##70. Works as expected. Yealink is doing something other than the ##70 in the pre-programmed setting... Just hope this helps someone else... Mike H.
 
FYI...
The button programming for the T-26 has a Call park pre-configured setting. Using the Pre-Configured setting for call park, the caller hears the parking lot announcement not the Called party. Using the keypad ##70 gives the desired result with the Called party hearing the announcement when they park the call. SO... INSTEAD use DTMF for the button programming with ##70. Works as expected. Yealink is doing something other than the ##70 in the pre-programmed setting... Just hope this helps someone else... Mike H.

'DTMF for the button programming with ##70' - I needed to see this so badly. Thanks! I never knew why ##70 was NOT working from the DSS programming as 'transfer'. 'DTMF' did it! Thanks
 

Members online

No members online now.

Forum statistics

Threads
26,688
Messages
174,412
Members
20,257
Latest member
Dempan
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top