Another FreePBX Sangoma Query . . .
-
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:
-
-
@JaredBusch You know what - I didn't come to this forum to be treated in this disrespectful manner. You have no idea what I know and don't know, Jared, and I never addressed you in such a disrespectful manner.
Equally, you responded to Dashrender in a similar disrespectful manner. The idea of a forum is that you can ask a question and, even, give a reply without being disrespected!
-
@JasonMinard welcome to "the Jared experience."
-
-
@JasonMinard said in Another FreePBX Sangoma Query . . .:
You have no idea what I know and don't know,
No, I do not. But you clearly do not know the basics of how parking works on FreePBX. My statement was the unvarnished truth based on your words.
Could be my fault. I guess I misinterpreted
being using Yealink and Sangoma with a couple of years nowto mean that you have been administrating these instead of simply using them. -
@JasonMinard said in Another FreePBX Sangoma Query . . .:
Equally, you responded to Dashrender in a similar disrespectful manner.
@Dashrender sidelined the response with incorrect information based on his desires for something not "built in" to Asterisk the way he wants it.
-
@JasonMinard said in Another FreePBX Sangoma Query . . .:
The idea of a forum is that you can ask a question and, even, give a reply without being disrespected!
Meh, I didn't even swear at you yet.
-
We currently do call parking on the Freepbx / Yealink by selecting "Call Parking" instead of BLF and then specifying the park slot number as the value, in the name call it "Park 1" etc.
-
Working perfectly! Once I excluded 70. Thanks everybody.
No need to treat anybody like you have Jared - childish! We are here to help each other - nothing gained by disrespecting each other! Just makes people afraid to ask question then.
-
@JasonMinard said in Another FreePBX Sangoma Query . . .:
Once I excluded 70.
70 would be the park command. slots would start at 71. However it can be changed. On our it starts at 9000 as we have way too many extensions.
-
@360col said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
Once I excluded 70.
70 would be the park command. slots would start at 71. However it can be changed. On our it starts at 9000 as we have way too many extensions.
What @Dashrender wants is to park a call on a person’s extension. Because that is how Mitel does it. He refuses to entertain retraining users to use general parking.
My solution for him was to crest a huge ass parking system. If his extensions are 3 digits, then create parking lot 7000 with 999 slots.
Then he has to make a prefix button for everyone labeled park with **7 as a value. People would be able to hit park, dial the extension, and hit send.
Each extension would have a “my park” button that would pick up theit park.
-
@JaredBusch said in Another FreePBX Sangoma Query . . .:
@360col said in Another FreePBX Sangoma Query . . .:
@JasonMinard said in Another FreePBX Sangoma Query . . .:
Once I excluded 70.
70 would be the park command. slots would start at 71. However it can be changed. On our it starts at 9000 as we have way too many extensions.
What @Dashrender wants is to park a call on a person’s extension. Because that is how Mitel does it. He refuses to entertain retraining users to use general parking.
My solution for him was to crest a huge ass parking system. If his extensions are 3 digits, then create parking lot 7000 with 999 slots.
Then he has to make a prefix button for everyone labeled park with **7 as a value. People would be able to hit park, dial the extension, and hit send.
Each extension would have a “my park” button that would pick up theit park.
That is exactly how our old Intertel system did it. My users like the new "Park Call" button better, it was a super easy transition, too. This way, if I call somebody's extension to tell them they have a call, they don't need to know what phone I put them on hold from, they just see that "Line 1" is red and they touch it and go. It's far better for us.
