Avaya IP Telephony Guía de configuración Pagina 105

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 222
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 104
Chapter 6 Setting up VoIP trunks for outgoing calls 105
IP Telephony Configuration Guide
6 Click the Save button.
Receive Threshold 0.0 (bad) to 5.0
(excellent)
Enter the Mean Opinion Score (MOS) that the system uses to
determine when a call needs to fallback to a PSTN line. If the
MOS on the receive channel falls below this value for all of the
available codecs, the BCM will fallback to a PSTN line.
For more information about MOS, refer to Appendix E,
“Quality of Service,” on page 191 and the QoS Monitor
chapter of the Programming Operations Guide.
Gateway Type BCM3.6
BCM3.5
BCM3.0
BCM2.5
BCM2.0
CSE 1000
CS 2000
IPT
NetMeeting
Norstar IP
Gateway
Other
Choose the type of system that is accessed through the
remote gateway:
BCM3.6: Business Communications Managers running 3.6
software.
BCM3.5: Business Communications Managers running 3.5
software.
BCM3.0: Business Communications Managers running 3.0
software.
*BCM2.5: Business Communications Managers running 2.5
or 2.5 FP1 or FP1 Maintenance Release software.
BCM 2.0: Business Communications Managers running 2.0
software, or Enterprise Edge systems running 2.0.x software.
IPT: M1 Internet Telephony Network Gateway
CSE 1000: CSE1000 switch.
CS3000: CS3000 switch.
NetMeeting: Microsoft NetMeeting trunk protocol.
Norstar IP Gateway: Norstar IP trunk protocol.
*If your gateway is set to BCMX.X and the other system is
upgraded to 3.6, your system will automatically update this
listing to BCM3.6 when the other system is contacted after the
upgrade. If this does not occur, your original configuration may
not be correct and you will have to set the change manually.
Gateway Protocol None
SL-1
CSE
Select the gateway protocol that the trunk expects to use.
None: No special features
SL-1: Use for BCM 2.5 systems only that require MCDN over
VoIP trunks
CSE: MCDN protocol for gateways that provide VoIP service
through Meridian 1 IPT (BCM 3.6 and newer software) or CSE
1000 gateways (BCM 3.0 and newer software)
Destination Digits <numeric>
(could be the
same as the
destination code
for the route to
this system)
Set the leading digits which callers can dial to route calls
through the remote gateway. Ensure that there are no other
remote gateways currently using this combination of
destination digits.
If multiple leading digits map to the same remote gateway,
separate them with a space. For example, 7 81 9555.
These numbers are passed to the remote system as part of
the dialed number.
Table 25 Remote gateway record (Continued)
Field Value Description
Vista de pagina 104
1 2 ... 100 101 102 103 104 105 106 107 108 109 110 ... 221 222

Comentarios a estos manuales

Sin comentarios