Ticket #530 (closed Feature Requests: wontfix)

Opened 6 years ago

Last modified 4 years ago

Allow trunk takeover in an emergency

Reported by: caribou7 Assigned to:
Priority: minor Milestone: 2.5
Component: Core Version:
Keywords: Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description (Last modified by mbrevda)

I don't know if this is possible in Asterisk, but if it is, I suggest that you include a checkbox when setting> up a route that says something like "this is an emergency route" - it would normally be a route used only for 911 (in North America) or similar emergency-only numbers elsewhere. If a route is> designated as the emergency route, it should have the> ability to take over a trunk if none are free for the call. Ideally, I would suggest that, for example, when 911 is dialed the system would first look for an available> trunk, but if none is found, it would first deliver a quick recorded announcement to all parties on the> needed trunk (something like a couple of distinctive> alerting tones, followed by "This line is needed for an emergency call - Goodbye" - it would then disconnect> the call, wait two seconds, seize the outgoing trunk> and dial the emergency number).>> This would primarily be useful for users that only have> one or two PSTN lines, but those are the only lines> that can send a 911 call to its proper location. The only time an emergency call should fail is if all> useable trunks are already in use for emergency calls> (if an explosion happens, everybody in the building> might attempt to call 911 at the same time, and you> don't want the first person who gets through to be cut> off by a second, third, fourth, etc. caller just as> they are giving the details of the emergency).>> If there is more than one candidate trunk, I would> suggest that the trunk to seize would be selected by this logic:

First choice: Trunk with call not yet completed (caller is listening to ringing or other call progress> tones). Second choice: Trunk with call in progress for 10> seconds or less (could make number of seconds> configurable) - if the call has JUST been established, the caller is probably still listening to an IVR or answering message or something like it. If more than> one trunk fits the criteria, then the one that's been connected the shortest amount of time. Third choice: The call that's been in progress the> longest - chances are more likely they've got their> business completed and are just shooting the bull, so to speak. My worry is that in cases where you only have one or two PSTN trunks and they are in use, a caller trying to> call 911 will get congestion. It's better to have a> dedicated emergency trunk, of course, but most small> businesses and nearly all homes will NOT have a dedicated emergency trunk.

Change History

03/26/06 03:21:46 changed by qldrob

Logged In: YES 
user_id=943208

Yup, that's the plan. It will be, I think, a seperate
module, where you specify a specific zap channel is for
emergency calls, and it'll let you specify the emergency
number too. But, it hasn't been written, at all, yet. It's
on my to-do list.

04/11/06 13:52:28 changed by wozto1s

  • description changed.
  • milestone set to 2.2.

I recon we should do this as part of the trunk re-write in 2.2 that I've been threatening to do :)

fyi, this is what I currently have in my extensions_custom.conf file for this...

; 999 calls...should ALWAYS get out exten => 999,1,ChanIsAvail?(ZAP/1) exten => 999,2,Dial(ZAP/1/999) exten => 999,3,Hangup() exten => 999,102,Playback(pls-hold-while-try) exten => 999,103,SoftHangup?(ZAP/1-1) exten => 999,104,Wait(1) exten => 999,105,Goto(from-internal-custom,999,1)

04/15/06 21:16:23 changed by wozto1s

  • owner deleted.
  • status changed from assigned to new.

10/20/06 02:32:10 changed by gregmac

  • version deleted.
  • milestone changed from 2.2 to 2.3.

01/08/07 13:46:49 changed by

  • milestone deleted.

Milestone 2.3 deleted

01/08/07 14:08:19 changed by vgster

  • milestone set to 2.3.

02/23/07 17:09:40 changed by andre_ruiz

I remember seeing exactly this (playing a message and hanging up the callers to use the trunk to emergency call) on voip-info.org. Somebody described the whole procedure and then users came up with code. Unfortunately I cannot find it right now. It even had protection for the trunk being taken again by another call in that 2 second wait before calling 911. It should be easy to find again with enough patience.

07/30/07 07:03:48 changed by wvroger

  • engine_version changed.
  • svn_rev changed.
  • milestone changed from 2.3 to 3.0.

bump to 3.0, there is a option on the outbound routes section at this time but it doesn't cease the trunk at this time.

11/13/07 17:20:42 changed by WAudette

  • confirmation set to Unreviewed.
  • description changed.
  • milestone deleted.

11/15/07 13:00:26 changed by WAudette

  • confirmation changed from Unreviewed to Confirmed.
  • description changed.

Somehow I deleted the description. I have replaced it here and adjusted the status.

WAudette...

07/24/08 17:43:38 changed by mbrevda

  • description changed.

07/24/08 19:52:39 changed by ryppn

  • milestone set to 3.0.

07/24/08 20:32:40 changed by p_lindheimer

  • status changed from new to closed.
  • resolution changed from None to wontfix.
  • milestone changed from 3.0 to 2.5.

actually closing. First off, what if the current call is an emergency call. Second, this is too specialized and too much liability is at stake. The end installer should assure that a system is properly covered for what ever e911 issues they may have to deal with.