Medias Mediatrix 1204, Справочное руководство

Страница: 286 / 390

Chapter 23 - Telephony Attributes Remote Line Extension
260 Mediatrix 1204
4. Define the Hook Flash Processing as per “Hook Flash Processing” on page 256 .
Setting the telephonyAttributesHookFlashProcessing variable to outOfBandUsingRtp means the
following:
5. Set the behaviour for the support of RFC 2833 in the voiceIfDtmfEnforceDefaultEvents variable for
both units.
6. If applicable, configure port mapping as per “Source Line Selection” on page 196 .
You could map FXO ports to IP Phones or analog phones connected to FXS ports. This creates
transparent and user-friendly call scenarios, as IP endpoints can act as remote PBX extensions.
Thus the reach of a PBX can be extended beyond the physical location of the PBX. This is
especially an attractive option for SOHO users.
Table 169: Hook Flash Processing
Mediatrix 1204 Mediatrix FXS Device
The hook-flash event received via an RFC
2833 RTP packet is executed. The hook-flash event is relayed as telephone-
event 16 via an RFC 2833 RTP packet.
Table 170: DTMF Enforce Default Events
Parameter Description
enable Conformance is enforced and support for RFC 2833 implies the support of basic
telephony-events. When setting the variable
voiceIfDtmfTransport to
outOfBandUsingRtp ( “DTMF Transport Type” on page 205 ), or the variable
telephonyAttributesHookFlashProcessing to outOfBandUsingRtp ( “Hook Flash
Processing” on page 256 ), the unit will advertise the support for events 0-15; it will
assume support for events 0-15 when support for RFC 2833 is received in an
announcement.
disable This creates a deliberate deviance to RFC 2833 as support of basic events is not
automatic. The variables
voiceIfDtmfTransport and
telephonyAttributesHookFlashProcessing then act independently to specify which
events will be relayed via RFC 2833. If Hook Flash relay is enabled by itself, support
of event 16 alone will be advertised; if both Hook Flash and DTMF relay are
activated, events 0-16 are supported.