Another FreePBX Sangoma Query . . .
-
I am in the process of moving a customer from one VoIP Provider to ourselves. We use FreePBX whereas the previous provider use Kazoo(?).
The handsets are Yealink T26 and they want to continue using these i.e. not investing in new handset hardware without good reason.
Most of the changeover is extremely straight forward except for one thing - they use four line keys as "park keys" on their phones at the moment called Park 1, Park 2, Park 3 and Park 4. These keys are programmed as:
Park 1 = BLF for *31
Park 2 = BLF for *32
Park 3 = BLF for *33
Park 4 = BLF for *34When on a call they can park INTO A PARTICULAR SLOT, the BLF LED will go from Green to Red to indicate that a call is parked in there and they can retrieve the call by pressing the same key.
I can see the logic - it was probably used to ease the change from old key system etc.
Now with FreePBX / Sangoma I have *70 only which will park calls into stack incrementing slot per call and Audio / REST Feedback as to Slot Number etc.
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
Is there any way we can have the performance IDENTICAL?
-
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
This question is unclear to me. But here is where you change those keys:
-
@JasGot said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
This question is unclear to me. But here is where you change those keys:
LOL - Intuit - really?
-
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JasGot said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
This question is unclear to me. But here is where you change those keys:
LOL - Intuit - really?
Damn dude. I fixed it under 30 seconds! I pasted the wrong clipboard.
-
@JasGot said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
This question is unclear to me. But here is where you change those keys:
I get what he wants - and it's a huge part of why I'm not on FreePBX today. Parking.
With FreePBX, he'd have to hit a button called park a call - which would then park it and announce what slot it was on.. then assuming he has more keys, he could label them Parking 70, Parking 71, Parking 72, etc.. and whatever slot was announced by using the park a call key, would light red.
His desire is not to have one key for parking and a different for retrieving. Though, a single key like this should be pretty easy transition, assuming they have a free key.
-
@JasGot said in Another FreePBX Sangoma Query . . .:
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JasGot said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
This question is unclear to me. But here is where you change those keys:
LOL - Intuit - really?
Damn dude. I fixed it under 30 seconds! I pasted the wrong clipboard.
Sorry,
just had to give ha grief. -
@Dashrender said in Another FreePBX Sangoma Query . . .:
With FreePBX, he'd have to hit a button called park a call - which would then park it and announce what slot it was on.. then assuming he has more keys, he could label them Parking 70, Parking 71, Parking 72, etc.. and whatever slot was announced by using the park a call key, would light red.
So that's the same scenario I deal with. The screenshot I posted is showing what you are describing. I don't like it either, but this one is a hosted PBX and we are stuck with it.....
When I asked them to change it, they said too difficult while supporting both Yealink and Polycom in the same Admin Portal.
The funny thing is.... because of that answer, we don't use their admin portal for programming anymore. We program them locally.
-
@JasGot We have no difficulty making changes via the Web Interface - being using Yealink and Sangoma with a couple of years now. I think you missed what I was asking - Thanks a mill anyway . .
-
@Dashrender Thanks Dashrender- Exactly!
-
@JasonMinard said in Another FreePBX Sangoma Query . . .:
@JasGot We have no difficulty making changes via the Web Interface - being using Yealink and Sangoma with a couple of years now. I think you missed what I was asking - Thanks a mill anyway . .
I'm sure I did, that's why I said the question was unclear to me. It became clear when Dashrender posted his comment.
-
@JasGot Perfect! Thanks . . .
-
The default FreePBX parking lot extension is 70. You transfer to that and it will park the call to the next available slot, 71-78.
You can also park direct to 71-78 by transferring the call to the extension directly. That is how most people actually do parking.
Yealink phones will do a blind transfer on DSS key natively. it is a built in option.
So you simply program the DSS key as a BLF for extension 71, 72, etc.
-
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JasGot said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
This question is unclear to me. But here is where you change those keys:
I get what he wants - and it's a huge part of why I'm not on FreePBX today. Parking.
With FreePBX, he'd have to hit a button called park a call - which would then park it and announce what slot it was on.. then assuming he has more keys, he could label them Parking 70, Parking 71, Parking 72, etc.. and whatever slot was announced by using the park a call key, would light red.
His desire is not to have one key for parking and a different for retrieving. Though, a single key like this should be pretty easy transition, assuming they have a free key.
You are totally talkign out of your ass.
You want a very specific replication of a feature from your old ass Mitel system. You do not want standard call parking. Do not conflate shit.
-
@JaredBusch said in Another FreePBX Sangoma Query . . .:
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JasGot said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
This question is unclear to me. But here is where you change those keys:
I get what he wants - and it's a huge part of why I'm not on FreePBX today. Parking.
With FreePBX, he'd have to hit a button called park a call - which would then park it and announce what slot it was on.. then assuming he has more keys, he could label them Parking 70, Parking 71, Parking 72, etc.. and whatever slot was announced by using the park a call key, would light red.
His desire is not to have one key for parking and a different for retrieving. Though, a single key like this should be pretty easy transition, assuming they have a free key.
You are totally talkign out of your ass.
You want a very specific replication of a feature from your old ass Mitel system. You do not want standard call parking. Do not conflate shit.
Gee thanks for telling me what I already know - yes I wanted a specific Mitel feature - Parking (at least what we call parking). So climb off your high horse
-
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JaredBusch said in Another FreePBX Sangoma Query . . .:
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JasGot said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
This question is unclear to me. But here is where you change those keys:
I get what he wants - and it's a huge part of why I'm not on FreePBX today. Parking.
With FreePBX, he'd have to hit a button called park a call - which would then park it and announce what slot it was on.. then assuming he has more keys, he could label them Parking 70, Parking 71, Parking 72, etc.. and whatever slot was announced by using the park a call key, would light red.
His desire is not to have one key for parking and a different for retrieving. Though, a single key like this should be pretty easy transition, assuming they have a free key.
You are totally talkign out of your ass.
You want a very specific replication of a feature from your old ass Mitel system. You do not want standard call parking. Do not conflate shit.
Gee thanks for telling me what I already know - yes I wanted a specific Mitel feature - Parking (at least what we call parking). So climb off your high horse
Except it matters. you are misleading with your reply.
-
@JaredBusch said in Another FreePBX Sangoma Query . . .:
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JaredBusch said in Another FreePBX Sangoma Query . . .:
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JasGot said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
This question is unclear to me. But here is where you change those keys:
I get what he wants - and it's a huge part of why I'm not on FreePBX today. Parking.
With FreePBX, he'd have to hit a button called park a call - which would then park it and announce what slot it was on.. then assuming he has more keys, he could label them Parking 70, Parking 71, Parking 72, etc.. and whatever slot was announced by using the park a call key, would light red.
His desire is not to have one key for parking and a different for retrieving. Though, a single key like this should be pretty easy transition, assuming they have a free key.
You are totally talkign out of your ass.
You want a very specific replication of a feature from your old ass Mitel system. You do not want standard call parking. Do not conflate shit.
Gee thanks for telling me what I already know - yes I wanted a specific Mitel feature - Parking (at least what we call parking). So climb off your high horse
Except it matters. you are misleading with your reply.
I'll pull some Scott level shit on ya and say - if you read what I wrote.... then you wouldn't be mislead.
I get what he wants - and it's a huge part of why I'm not on FreePBX today. Parking.
You offered me the parking the OP talked about - and that wasn't deemed acceptable at the time (i.e. a huge part of the why) - and then I start a new sentence with one word - Parking - i.e. that was my issue, doesn't matter that Mitel's definition is different from yours (or FreePBX's). And I didn't expand upon my actual issue - so there was no conflating at all.
-
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JaredBusch said in Another FreePBX Sangoma Query . . .:
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JaredBusch said in Another FreePBX Sangoma Query . . .:
@Dashrender said in Another FreePBX Sangoma Query . . .:
@JasGot said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The shortfall of this is that we can monitor those slots with BLF but we are pressing the same Key to Park / UnPark. i.e. you can program a Call Park Key and setup a few BLFs to monitor, say, 70, 71, 72 etc. but you are parking with a different key to retrieving.
This question is unclear to me. But here is where you change those keys:
I get what he wants - and it's a huge part of why I'm not on FreePBX today. Parking.
With FreePBX, he'd have to hit a button called park a call - which would then park it and announce what slot it was on.. then assuming he has more keys, he could label them Parking 70, Parking 71, Parking 72, etc.. and whatever slot was announced by using the park a call key, would light red.
His desire is not to have one key for parking and a different for retrieving. Though, a single key like this should be pretty easy transition, assuming they have a free key.
You are totally talkign out of your ass.
You want a very specific replication of a feature from your old ass Mitel system. You do not want standard call parking. Do not conflate shit.
Gee thanks for telling me what I already know - yes I wanted a specific Mitel feature - Parking (at least what we call parking). So climb off your high horse
Except it matters. you are misleading with your reply.
I'll pull some Scott level shit on ya and say - if you read what I wrote.... then you wouldn't be mislead.
I get what he wants - and it's a huge part of why I'm not on FreePBX today. Parking.
You offered me the parking the OP talked about - and that wasn't deemed acceptable at the time (i.e. a huge part of the why) - and then I start a new sentence with one word - Parking - i.e. that was my issue, doesn't matter that Mitel's definition is different from yours (or FreePBX's). And I didn't expand upon my actual issue - so there was no conflating at all.
I’ve also worked multiple solutions to your parking needs. Still waiting on you to setup a test for the last version.
-
@JasonMinard said in Another FreePBX Sangoma Query . . .:
being using Yealink and Sangoma with a couple of years now.
Blatantly not as you have no idea how parking actually works on FreePBX.
-
@JaredBusch said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
being using Yealink and Sangoma with a couple of years now.
Blatantly not as you have no idea how parking actually works on FreePBX.
In his defense I've been using Yealink phones since 2014 and FreePBX since Elastix hasn't been viable, and I had no clue the BLF DSS keys would also blind transfer. I knew you could transfer directly to ext 72, for example, but I never tried the other way :man_shrugging_light_skin_tone:
-
