Jump to content

LINE Key's Like a Key System


esoare

Recommended Posts

So I deployed 5 phones at a small site. Ported their numbers, and while deploying, the customer was like...oh, you have to transfer? Why can't I just push a Line button?....

So I scrambled and came up with the following.

Yealink T42G's.
After Building in Smart PBX
Went over to the Advanced Provisioner APP.

Key 1 =Type: Line / Account: Account 1
Key 2 = Type: BLF / Value:*3101 / Label, Line 1 (Note *3 is park or retrieve, 101 is the first park slot, 102 is the second and so on)
Key 3 = Type: BLF / Value:*3102 / Label, Line 2
Key 4 = Type: BLF / Value:*3103 / Label, Line 3
Key 5 = Type: BLF / Value:*3104 / Label, Line 4

So. Usage.

A Call Comes in and gets answered by anyone in the ring group. If it is for someone else. They press "Tran" and Line 1. The call gets parked. And the button lights red.
To retrieve. Any of the users press the Line 1 button. And the call gets 'retrieved'.

This is as close to a 'key system' as you can get (I think :) ).

The irony in the whole thing, is that they do have to transfer...but they can just push 1 button to pickup the call.

Link to comment
Share on other sites

I wonder if there could be something in the back end, that would change a phone pressing the normal "Hold" key, that would actually on the Server, place the call into a Park Slot!!

Noo!
Transfer + BLF of *3101/Line 1.
Just press HOLD
Call gets into the next available park slot
BLF for that park slot Lights up.

That would be an interesting idea. It would have to be used carefully, but for small offices, it would be a cool feature/idea.
Link to comment
Share on other sites

What you are trying to replicate is called Shared Line Appearance.  Asterisk does it fairly well.
I typically do the same as you are referring to... Parking lots named Line 1, Line 2, etc.  Darren shared a Best Practices Demo at KazooCon about this that was very interesting.  I just wish I could remember it.  Hopefully he reads this and does a quick write up about it.
Link to comment
Share on other sites

Thanks Anthony.

@ Karl S. I was pondering doing the Call Park locally on the phones, but realize that I soon as I made a change on any other part of the 5 phones, the Provisioner File would change, and when the phone downloaded the new file, it would overight the custom changes I made.... I guess I could turn off the Auto Provisioning from the phones (after allowing local http admin rights also) and then make the change to Call Park...

Where do we put the "Idea" for adding Call Park (to the Yealinks) on the Advanced Provisioner :)
Link to comment
Share on other sites

I need to be careful saying this since we rarely use Yealinks, but I am about 80% positive that the 2600hz provisioning files will NOT overwrite the BLF keys on Yealinks, so if you set them in the web UI for the Yealink phone it should stick without an issue. That being said, it isn't the best method and is not recommended. I did it about 6 months ago and had no problems.

Something Darren mentioned in the same breakout session Anthony is referring to was that 2600hz will be adding a way for you to tweak or upload your own custom config via Monster. This way even if they have not added the feature in, you can still set it from Monster and then have it provision automatically without needing to go into the web UI. This would eliminate the issue you mentioned.
Link to comment
Share on other sites

@Karl S.

So I was poking around at the customer site yesterday. And I programmed some Line Keys with BLF *3101 etc...

I had an active call.

Pressed the BLF *3101

The call was parked!!

The light lit up

I was able to pick it up from any of the other phones by pressing that BLF *3101 button!


So you can Park a call (on Yealink phones through hosted) just by pressing the appropriate button. :)


And of course, BLF is in the Auto Provisioner. Problem solved.


es
Link to comment
Share on other sites

  • 3 weeks later...
×
×
  • Create New...