0

Mobility extension - Confirm on answer

Fabian Huiskes

February 03, 2020 16:55

None

Follow

Im in need for some help on a specific case. Situation described:

 

We have a hosted solution for our office telephony system (we're a provider ourself) but want our emergency number to run on a different provider and PBX. We previously used freepbx on a raspberry pi but stability sometimes was an issue. 

What we want;

8 mobile phones to ring. I can fix this by making a 'dummy' extension and use it as a mobility extension. Plus side is that we can add a extra SIP account to our devices in office so it rings simultanesly

When a user answers the phone (or a VM picks up the conversation) we want to confirm it by pressing '1' for example. This is a common feature in other PBX systems.

 

Now i can get step 1 to work without an issue, however. Does there exist a feature like my second colomn? So confirm a mobile converstation by pressing a button. Or are there any alternatives to get a similar working?

 

• Facebook
• Twitter
• LinkedIn

3 comments

• 0
  
  Pixy Tse February 04, 2020 03:06

  Hi Fabian, we currently don't have the confirmation feature yet. Do you have any  feature reference of other pbx we might refer how the feature is.

• 0
  
  Fabian Huiskes February 04, 2020 07:47

  Can't find a detailed describtion online this soon, but in FreePBX for example its described as following;

   

  If checked, any queue member that is actually an outside telephone number, or any extensions Follow-Me or call forwarding that are pursued and leave the PBX will be forced into Call Confirmation mode where the member must acknowledge the call before it is answered and delivered.

  And for the 'Call confirm announce' (a prompt which asks you to press 1 to accept the call)

  Announcement played to the Queue Memeber announcing the Queue call and requesting confirmation prior to answering. If set to default, the standard call confirmation default message will be played unless the member is reached through a Follow-Me and there is an alternate message provided in the Follow-Me. This message will override any other message specified..

• 0
  
  Larry Neblett February 06, 2020 11:57

  Pixy, I think he is referring to a feature known as "find me, follow me".

   

  While the implementation may differ between manufacturers, it is where the user sets up a find me, follow me at the extension level.

   

  When a caller dials in, it will usually ring at the local extension for a period and then an announcement from the PBX will be played back to the caller indicating something like "please wait while I try and locate the person you are calling". The PBX then places the caller on-hold and then sets up a second call to the follow me destination be it a cell, landline or softphone, When the follow-me destination answers the call, the PBX will announce the caller and ask if the follow me destination wished to take the call by pressing 1, or reject the call by pressing another number. If the follow me presses one, the caller is connected to the follow me destination. If 2 is pressed, then the PBX retains control of the call and sends the caller to the VM box on the PBX of the original extension or follows the rule established for same. If the follow me does not answer directly, but the cellular VM does or there is no answer, then it is not possible to get a 1 or 2 response and the PBX will timeout and return the caller back to the PBX as if the call was rejected by the follow me. You can also set up more than one follow me destination.

  While Yeastar can ring various devices in a linear fashion, the confirmation to accept or reject is not really there. Of course, the number of destinations and all is dictated by the connection type as there must be enough call paths to support the number of calls.

  This is a pretty common standard offering in Asterisk.

  I am not aware of the functionality being available as a feature set of a queue,  as all that I have seen are done at the extension level. However, just because I have not seen it associated to a Q, does not mean that some don't have that.

  As the S-PBX does not really support external numbers, this really may be a two-fold request. Some systems have it such that numbers not associated as extensions to the PBX can be members of a Q. A typical application if the use of LDAP where one can create entries in the PBX directory and then use those entries in some features as though they were extensions. But one has to realize the pitfalls of doing so.