
Feature Reference
Multifrequency signaling
1610
Administrator’s Guide for Avaya Communication Manager
November 2003
To set up modem pooling for compact modular cabinets, see Installation, Upgrades and Additions for
Avaya CMC1 Media Gateways.
To set up modem pooling for multi-carrier cabinets, see Made Easy Tool for DEFINITY Media Server
Configurations.
To set up modem pooling for DEFINITY SI cabinets, see Made Easy Tool for DEFINITY Media Server
Configurations.
Multifrequency signaling
Multifrequency (MF) signaling is a form of address signaling used between media servers and the CO. It
is similar to DTMF signaling in that tones convey the dialed number.
With MF signaling, the signal is typically a combination of two frequencies from a group of 5 or 6
frequencies (2/5 or 2/6). The origination and destination servers or switches exchange tones that have
specific meanings according to the MF protocol.
Detailed description
Avaya Communication Manager supports two frequency groups:
•
R2-multifrequency compelled signaling (R2-MFC) frequency
•
R1 frequency (for Spain and Russia)
R2-MFC is a version of MFC recommended by the International Telecommunication Union (ITU). It
provides signaling between a CO and a media server over analog or digital CO, DID, or DIOD trunks. It
also provides signaling between any 2 servers running Communication Manager.
Communication Manager provides MF signaling that complies with ITU regulations and national
regulations for specific countries. It provides these types of MF signaling: MFE) MF Shuttle, and
multifrequency compelled (R2-MFC). These protocols signal the called number, the calling party’s
number (ANI), and information about the type of call or type of caller (category).
Communication Manager allows prefix digits for ANI sent on outgoing calls to be defined per PBX or
per the originator’s class of restriction.
If a call is a tandem call and the incoming and outgoing trunk use different protocols, Communication
Manager makes no attempt to convert between the various protocol’s meanings for category. Instead,
•
the PBX uses the incoming trunk’s COR assigned category if the outgoing trunk is Russian or
R2-MFC, and
•
the PBX uses ARS call types if the outgoing trunk is MFE.
The server running Communication Manager provides the incoming ANI to all features on
Communication Manager that need to identify the calling party.
Содержание Communication Manager
Страница 320: ...Setting Up Telecommuting Training Users 320 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 416: ...Managing Group Communications Observing Calls 416 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 502: ...Administering Media Servers SNMP Agents 502 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 602: ...Phone Reference Internet Protocol IP Softphones 602 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 1338: ...Screen Reference Vector Directory Number 1338 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 1832: ...Glossary and Abbreviations Z 1832 Administrator s Guide for Avaya Communication Manager November 2003...
Страница 1854: ...Index X 1854 Administrator s Guide for Avaya Communication Manager November 2003...