Avaya IP Telephony Guia de Configuração descarregar pdf (Página 105)

Chapter 6 Setting up VoIP trunks for outgoing calls 105

IP Telephony Configuration Guide

Setting up VoIP trunks for fallback

This section includes these topics:

• “Setting up the VoIP schedule” on page 114

• “Configuring routes for fallback” on page 107

• “Creating destination codes for fallback routes” on page 109

• “Example: A private network configured for fallback” on page 115

• Monitoring fallback: “PSTN fallback metrics” on page 121

By enabling PSTN fallback on the Local Gateway IP Interface screens for H.323 and SIP trunks,

you allow the system to check the availability of suitable bandwidth for a VoIP call, then switch

the call to a PSTN line if the VoIP trunk is not available or cannot produce the expected quality.

Refer to “Setting up the local gateway” on page 87. The Local Gateway IP Interface screen is

accessed at Services, IP Telephony, IP Trunks, H.323 Trunks or SIP Trunks.

You use scheduling and destination codes to allow the call to switch from H.323 and/or SIP line

pools to a PSTN line without requiring intervention by the user.

On any IP gateway for which you want to allow fallback, you need to ensure that QoS monitor is

enabled. Refer to “Configuring a remote gateway (H.323 trunks)” on page 96 and “Configuring

remote endpoints (SIP trunks)” on page 99. The Remote Gateway screen is accessed at Services,

IP Telephony, IP Trunks, H.323 Trunks, Remote Gateway, and Services, IP Telephony, IP

Trunks, SIP Trunks, Address Book.

Note: Use the dialing plan worksheet in the Programming Records to plan your dialing

requirements so you can pinpoint any dialing issues before you start programming. If you

are programming an existing system, you can look at what numbers the users are familiar

with dialing, and you can attempt to accommodate this familiarity into your destination

codes plan.

The Programming Operations Guide provides configuration charts for various types of

networks using PRI lines. They can be adapted to VoIP trunks by adding the Remote

Gateway information to the configuration.

Warning: QoS monitor must be turned on at both endpoints. QoS Monitor is found under

Services. For information about using the QoS monitor, refer to “Quality of Service

Monitor” on page 120.

Network note: All systems on your private network must be running BCM 3.5 or later

software or have the QoS patch installed that supports this release. Business

Communications Managers running BCM 3.0.1 or earlier software cannot provide a

compatible VoIP trunk with BCM 3.5 or later software without this patch.

1 2 ... 100 101 102 103 104 105 106 107 108 109 110 ... 211 212

Sem comentários

Avaya IP Telephony Guia de Configuração Página 105