911

[phoneguy]

I think Shoretel lacks a little in the saftey field. The system needs to be able to seize a trunk when it needs to call 911. So for instance, the PRI is down and the only trunk available is the backup trunk that is on port 9 (or wherever). If that trunk is being used because it was picked up by someone pressing a line access key, then you will get a reorder tone when trying to place a 911 call. Trunks Unavailable to Route to 9.

[OldPhoneGuy]

I think you'd find that to be true in most any phone system out there. You need to have an available facility before you can complete a call.

[matthiasgoodman]

I would love the ability to have some user able to use a trunk for normal calls and all users able to use it for 911.

[Jlorenz]

In the Shoretel appendix B of the administration Guide defines the suggested established process for 911

It is recommended that every site with an SG have one dedicated Pots line for 911 (In a real world scenario)

The Admin Guide is pretty clear on its usage. I would think that foremost Safety of the employees would be at the top of the list. Saying that, the ShoreTel is only doing what it is established to do by FCC regulation as with any OEM.

Following the Guide Lines and dedicating a single POTS for 911 is a must (IMO) by the Company using any system. It is the responsibility of the Partner / Consultant to offer all viable solution to their customers on this very important matter.

In a case where you have a single pots on a site along with a PRI, there is a method (custom Dial String) that can be in place to ensure 911 is going out the Pots Only. TAC can do this very easily.

I understand what you requesting, the system is capable of doing just as you ask, follow the guidelines as per Appendix B and you will have what you want.

[gberkemeyer]

Don't block 911 on any trunk group

In a case where you have a single pots on a site along with a PRI, there is a method (custom Dial String) that can be in place to ensure 911 is going out the Pots Only. TAC can do this very easily.

I realize you were just making a point about custom dial strings here, but preventing 911 calls from going out the PRI would probably be a bad idea, because the POTS line could fail and the PRI still be functional. The easiest way would be to let the 911 calls go out the PRI if channels are available, but configure the POTS line for 911 only (no Local, Long dist, etc). That way if no PRI channels are available, the call will then use the POTS line, and you don't need any custom dial strings.

[Jlorenz]

I realize you were just making a point about custom dial strings here, but preventing 911 calls from going out the PRI would probably be a bad idea, because the POTS line could fail and the PRI still be functional. The easiest way would be to let the 911 calls go out the PRI if channels are available, but configure the POTS line for 911 only (no Local, Long dist, etc). That way if no PRI channels are available, the call will then use the POTS line, and you don't need any custom dial strings.

With regards to dedicated POTS, that is exactly what I stated as deploying POTS in every site dedicated for 911 as described in the appendix B of the admin guide.

with 911 you have to be very careful, in some areas of the country, 911 is legislated to be very strict in standards. For example a 500,000 sq ft building, that is a large area, Some State Laws, you have to have a 911 designation for each point within every 50,000 sq ft or whatever to designate the point of origin (Makes Sense).

That site has a PRI and a dedicated pots for 911, since 911 is not route-able in ShoreTel, you have to force it (In comes the Dial String) What the dial string does that the Unchecked of 911 doesn't? is force the 911 out a specific trunk "FIRST" then out the backup if the primary is not available.

In this scenario each are in need of its own pots has to have its own trunk grp / usr grp defined to accommodate. There is massive planning for this application.

Hope it helps clear things up