Avaya BCM 2.0 IP Telephony Manual de usuario descargar pdf (Pagina 68)

68 Configuration

Enterprise Edge 2.0 IP Telephony Configuration Guide P0911590 Issue 02

With the fallback feature disabled, calls move across the IP telephony trunks no

matter the QoS. The fallback feature is only active at call setup. A call in progress

does not fall back if the QoS degrades.

Calls fallback if there is no response from the destination, an improperly configured

remote gateway table, or if there are not enough DSP resources available to handle

the new call.

IP trunks on the core telephony services use routes to determine which outgoing

facilities to use. A given destination code can have an alternate route configured.

The alternate route is used if the main route is not available to process calls. For

example, if all the lines in a line pool are busy.

IP trunks also use this capability. One capability unique to IP trunks takes advantage

of the QoS monitoring that is part of IP telephony. If fallback to conventional

circuit-switched facilities is enabled in the Local Gateway Configuration, calls

route to the circuit-switched facilities if the QoS is below the acceptable threshold.

The installer configures fallback as follows:

1. Launch Unified Manager and select the IP Telephony radio button.

2. Enable fallback in the Local Gateway Configuration.

3. Enable QoS monitoring for the required destination in the Remote Gateway

Configuration.

4. Set the Tx and Rx thresholds (MOS numbers) for the required QoS.

5. Configure all alternate routes for the IP trunks.

1 2 ... 63 64 65 66 67 68 69 70 71 72 73 74 75 76

Sin comentarios

Avaya BCM 2.0 IP Telephony Manual de usuario Pagina 68