Sensores

EMERGENCY CALL FEATURE

The system will immediately allow access to local emergency facilities whenever a station user enters the Emergency Call feature code (defaults to 911/999). When activated, the Emergency Call feature will select a trunk or route the call based on the device programming. The digit(s) required to call the local emergency services facility (defaults to 911/999) are then automati- cally dialed. Because a condition may exist where a critical situation needs to be reported, this feature will override all toll restrictions and trunk access programming.

In versions prior to 7.0, when a user dialed 911/999 at intercom dial tone, the system selected an idle trunk using the trunk access code programmed for this feature (defaults to Trunk Group 1) or an individual line code (direct trunk access). In versions 7.0 and later, however, the emer- gency extension is programmable on a per-station basis. In addition, Day/Night Emergency Outgoing Access lists are provided to validate the extension making the emergency call. When a user dials 911/999 at intercom or CO dial tone, emergency outgoing access is granted based on how system programming and what the user dialed, as described below.

• If the user dials the emergency feature code from a station with a trunk or trunk group programmed as the Emergency Extension, the Emergency Call feature routes the call

based on the station’s Emergency Extension. The trunk or trunk group does not validate the station originating the emergency call against the trunk group’s Emergency Day/ Night Outgoing Access List. An idle trunk is seized, and the system automatically dials Emergency Number 1.

• If the user dials the emergency feature code from a station with ARS programmed as the Emergency Extension:

a. The Emergency Call feature routes the call based on the station’s Emergency Extension.

b. The call is routed to Route Group 1.

c. The call tries the first facility group in Route Group 1.

d. The trunk group or node trunk group validates the station originating the emer- gency call against the group’s Emergency Day/Night Outgoing Access List.

e. If the call is denied, it tries the next member in the facility group. If each member

denies the call, the call tries the next facility group in Route Group 1’s list.

If everything is denied due to Emergency Outgoing Access, the call is routed once

again to Route Group 1. The call then tries the first facility group in Route Group 1. The trunk group or node trunk group does not validate the station originating the emergency call against the group’s Emergency Day/Night Outgoing Access List. If no trunks are available, the call tries the next member in the facility group. If all of the members are unavailable, the call camps-on to Route Group 1 until a trunk is available.

• If the user accesses a trunk or trunk group and dials any Emergency Number (1-10), the

trunk or trunk group does not validate the station originating the emergency call against the trunk group’s Emergency Day/Night Outgoing Access List. An idle trunk is seized, and the system automatically dials the emergency number.

NOTICE

It shall be the responsibility of the entity or person(s) completing installation and mainte- nance of hardware or software described herein to research, comply with and be responsi- ble for the specific governmental rules and regulations regarding Emergency Outgoing Access (911/999) of the geographic location in which such functions are performed.

• If the user accesses ARS and dials any Emergency Number (1-10):

a. The call is routed to Route Group 1.

b. The call tries the first facility group in Route Group 1.

c. The trunk group or node trunk group validates the station originating the emer- gency call against the group’s Emergency Day/Night Outgoing Access List.

d. If the call is denied, the call tries the next member in the facility group. If each

member denies the call, the call tries the next facility group in Route Group 1’s list.

If everything is denied due to Emergency Outgoing Access, the call is routed once

again to Route Group 1. The call then tries the first facility group in Route Group 1. The trunk group or node trunk group does not validate the station originating the emergency call against the group’s Emergency Day/Night Outgoing Access List. If no trunks are available, the call tries the next member in the facility group. If all of the members are unavailable, the call camps-on to Route Group 1 until a trunk is available.

NOTE: Inter-Tel highly recommends that only local trunks be installed and used for emergency trunk access and that only local trunks be programmed in Route Group 1. Programming a node in Route Group 1 may cause the system to access a trunk on a separate node when ARS is used for emergency access. If this occurs, Emergency Out- going Access is no longer validated.

The system will allow the Dialing Wait After Connect timer to expire and will then dial the digit string programmed in the database as the emergency number.

At the time the call is processed, a minor alarm will be generated by the system and sent to all administrator stations. Also if the Message Print option is enabled, the alarm message is sent to the designated output port.

Emergency Outgoing Access Lists

As of version 7.0, the system supports two outgoing access lists called Emergency Day Outgo-

ing Access and Emergency Night Outgoing Access. These lists, which are similar to the Day/

EMERGENCY CALL FEATURE

AXXESS DATABASE: Station user dials 911 EMERGENCY EXT. = TRUNK GROUP 1 (92001) EMERGENCY No. = 911 CALL PLACED TO 911 ALARM #11 DISPLAYED MESSAGE PRINTOUT, IF ENABLED OR

Page 169

Ten Emergency Numbers

Ten Emergency Numbers

The system can store up to ten emergency numbers that are dialed when the Emergency Call feature is used.

When the Emergency Call feature code (defaults to 911/999) is dialed at intercom dial tone, the Emergency Call feature will select a trunk (defaults to Trunk Group 1) and then automatically dial Emergency Number 1. If a station user accesses a trunk or ARS and dials Emergency Numbers 1-10, the dialed number will automatically override all toll restrictions and trunk access programming.

If the system is installed in an area where 911/999 service is not available, it is suggested that the number for the local police or fire department or the telephone company operator be substi- tuted.

If the database programmer renders this feature inoperative by removing all trunk access and/ or by removing the dialed digit string, the database program will present a warning message indicating that the feature has been disabled and requiring the programmer to acknowledge or change this condition before being allowed to continue.

Like all other feature codes, the 911/999 feature code can be changed to another 1- to 5-digit code, if necessary, but it is not recommended.

An emergency number is blocked if there are no trunks or emergency numbers programmed in the database, or all trunks in a trunk group are busy.

If the Emergency Call feature is programmed to use ARS, route group 1 (local calls) will be used even if its dial patterns are reprogrammed.

Emergency calls, by default, use the first local trunk group and will not be sent using node trunk groups on other nodes. However, when ARS is used to place an emergency call, Route Group 1 is used even if it contains nodes. This means that the network can access a trunk on a node other than the user’s node if the user accesses ARS and dials the emergency number.

Local trunks must be installed and used for emergency number trunk access and nodes should not be used in Route Group 1. When a user places an emergency call, every administrator in

the network receives an emergency alarm.

Calling Party Number Field

Each station can be programmed to send an identifying number when a call is placed. The “Calling Party Number field is located in Devices and Feature Codes - Stations - Individual Station programming. This information is required for emergency 911/999 calls in some states. You can program any number up to 48 digits in the Calling Party Number field. However, check with your service provider to determine their specific requirements for this field. This number will be sent in the ISDN setup message in the Calling Party Number Information Ele- ment. In addition, the system will also send the extension number of the station in the Calling Party Number Sub-address Information Element. The CO should ignore this information ele- ment if it does not support it.

NOTE: There is no default number for this field. It is up to the programmer to supply the cor- rect Emergency Calling Party Number for each station.

If an off-premises extension is used for dialing 911/999, the 911/999 operators will see Calling Party Number or the address of the location of the system, not the off-premises address. Off- premises personnel should be prepared to give the correct address and other pertinent informa- tion if it is not programmed as the Calling Party Number.

IP Devices and Local Loop Support

System V7.0 or later supports IP-based solutions for providing local Public Switched Tele- phone Network (PSTN) connectivity using the IPRC card and a third-party Media Gateway Control Protocol (MGCP) gateway. The system requires software V7.0 or later and IPRC firm- ware V1.3 or later. The firmware supports up to 32 IP endpoints/SLAs/SoftPhones and Loop Start Adapters (LSAs). Support for IP-based local loop does not require Premium Features. Up to 32 ports of an IPRC can be programmed to be loop start adapter ports (MGCP gateway trunks). The IPRC statically maps Voice over IP resources on a one-to-one, non-blocking basis for each loop-start port within the MGCP device.

Inter-Tel currently supports the following gateways:

• AudioCodes MP-100 Foreign Exchange Office (FXO) Gateway: Supports up to four

loop start line (FXO) ports.

• AudioCodes MP-104 FXO Gateway: Supports up to four loop start line (FXO) ports.

Although the MP-104 is similar to the MP-100, each gateway uses a different switch type for configuring the device. The MP-100 uses DIP switches, and the MP-104 uses a command line switch (-fb). The MP-104 on an IPRC v8.1 firmware supports the peer- to-peer (P2P) audio feature.

With v9.0 or later software, the system supports SIP (Session Initiated Protocol) trunks to reach the CO in addition to MGCP trunks. SIP trunks allow the system to communicate with the CO via SIP-enabled gateways. As the SIP protocol becomes more and more popular, it is important to be able to communicate to SIP gateways in the IP-centric world. Inter-Tel cur- rently supports the AudioCodes™ MP-104 SIP gateway (with software version 4.2). For details on the gateway device, see the latest version of the MGCP Gateway Installation Guide (part no. 835.2741).

Page 171

IP Devices and Local Loop Support

The following diagram illustrates a remote site with an MGCP gateway.