Query regarding Telephone Event Payload Types

[mattKnight]

Hi all

I am having intermittent issues between a CM 5.2.1 and an Avaya Meeting exchange server. There is an Avaya Session manager in the mix as well.

The primary issue is that intermittently DTMF is not received/recognised by the Meeting Exchange server. The CM SIP trunk is configured to send DTMF as rtp-payload, using Telephone Event Payload Type of 120. The MX server is configured to use Telephone Event Payload type 127.

Is this mis-match the root cause of intermittent DTMF transmission? I'd change the values - but as the ystems are under change freeze at the moment; I need a bit of confirmation before I request a freeze break...

Any ideas - a network sniff would be possible, but with the amount of traffic ruunig onto the MX, makes finding a DTMF failure a tall order!

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[ewaaijenberg]

It could be the issue. We also had this once where the payload should be send over the none Avaya standard protocl and the DTMF digits where not entering. You should change this on the trunk form or in the MX Exchange.
If you don't want to change this on the trunk to the session manager you should consider creating a new trunk group to the session manager where the setting is different.