Avaya BCM 4.0 Networking Guide de configuration télécharger pdf (Page 714)

100

101

714 Appendix B ISDN overview

N0060609N0060609

• Public: Public service calls connect your BCM set with a Central Office (CO). DID and DOD

calls are supported.

• Private: Private service calls connect your BCM set with a Virtual Private Network. DID and

DOD calls are supported. A private dialing plan may be used.

• TIE: TIE services are private incoming and outgoing services that connect Private Branch

Exchanges (PBX) such as BCM.

• FX (Foreign Exchange): FX service calls logically connect your BCM telephone to a remote

CO. It provides the equivalent of local service at the distant exchange.

• OUTWATS: OUTWATS is for outgoing calls. This allows you to originate calls to telephones

in a specific geographical area called a zone or band. Typically a flat monthly fee is charged

for this service.

• Inwats: Inwats is a type of long distance service which allows you to receive calls originating

within specified areas without a charge to the caller. A toll-free number is assigned to allow for

reversed billing.

Consult your customer service representative to determine whether or not this feature is

compatible with your provider.

Emergency 911 dialing

(North America only)

The ISDN PRI feature is capable of transmitting the telephone number and internal extension

number of a calling station dialing 911 to the Public Switched Telephone Network (PSTN). State

and local requirements for support of Emergency 911 dialing service by Customer Premises

Equipment vary. Consult your local telecommunications service provider regarding compliance

with applicable laws and regulations. For most installations the following configuration rules

should be followed, unless local regulations require a modification.

• All PSTN connections must be over PRI.

• In order for all sets to be reached from a Public Safety Answering Position (PSAP), the system

must be configured for DID access to all sets. In order to reduce confusion, the dial digits for

each set should be configured to correspond to the set extension number.

• The OLI digits for each set should be identical to the DID dialed digits for the set.

• The routing table should route 911 to a PRI line pool.

• If attendant notification is required, the routing table must be set up for all 911 calls to use a

dedicated line which has an appearance on the attendant console.

• The actual digit string 911 is not hard-coded into the system. More than one emergency

number can be supported.

If transmission of internal extension numbers is not required or desired, then it is recommended

that the person in charge of the system maintain a site map or location directory that allows

emergency personnel to rapidly locate a BCM set given its DID number. This list should be kept

up to date and readily available.

IP telephony note: Ensure that you do not apply a 911 route to an IP telephone that is off the

premises where the PSAP is connected to the system.

1 2 ... 709 710 711 712 713 714 715 716 717 718 719 ... 757 758

Commentaires sur ces manuels

Pas de commentaire

Avaya BCM 4.0 Networking Guide de configuration Page 714

Commentaires sur ces manuels

Produits connexes et manuels pour Mise en réseau Avaya BCM 4.0 Networking