problem of dtmf between Cisco Call Manager 6.1 and Alcatel PBX

Unanswered Question
Sep 2nd, 2008
User Badges:

Current, I have a problem of dtmf between MGCP Cisco Gateway and Alcatel PBX using Digital phone of the Alcatel PBX


The configuration is:


Phone Digital ---> Alcatel PBX --> MGCP Cisco router ---> Call Manager 6.1 ---> MGCP Cisco Router---> PSTN


Any recomendation?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Marwan ALshawi Tue, 09/02/2008 - 20:43
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Best Publication, December 2015

this is the dtmf-relay command


mgcp dtmf-relay voip codec {all | low-bit-rate} mode

{cisco | nse | out-of-band}


and this is its details so check up to be comptible with ur pbx


Use the mgcp dtmf-relay command in global configuration mode

to ensure accurate forwarding of digits on compressed codecs.

Use this command to access an announcement server or a voicemail

server that cannot decode RTP packets containing DTMF

digits. When the mgcp dtmf-relay command is active, the DTMF

digits are removed from the voice stream and carried so that the

server can decode the digits.

The following codecs are available:

■ all: Dual-tone multifrequency (DTMF) relay is to be used with

all voice codecs.

■ low-bit-rate: DTMF relay is to be used with only low-bit-rate

voice codecs, such as G.729.

■ cisco: Real-Time Transport Protocol (RTP) digit events are

encoded using a proprietary format similar to Frame Relay

as described in the FRF.11 specification. The events are

transmitted in the same RTP stream as nondigit voice

samples, using payload type 121.

■ nse: Named service event (NSE) RTP digit events are

encoded using the format specified in RFC 2833, Section

3.0, and are transmitted in the same RTP stream as nondigit

voice samples, using the payload type that is configured

using the mgcp tse payload command.

The following modes are available:

■ out-of-band: Media Gateway Control Protocol (MGCP) digit

events are sent using NTFY messages to the call agent,

which plays them on the remote gateway using RQNT

messages with S: (signal playout request).

■ nte-gw: RTP digit events are encoded using the named

telephony event (NTE) format specified in RFC 2833,

Section 3.0, and are transmitted in the same RTP stream as

nondigit voice samples. The payload type is negotiated by

the gateways before use. The configured value for payload

type is presented as the preferred choice at the beginning of

the negotiation.

■ nte-ca: Identical to the nte-gw keyword behavior except that

the call agent's local connection options a: line is used to

enable or disable DTMF relay.


if helpful Rate

Actions

This Discussion