How to force DTMF method? Impossible?

[moona]

Hi guys,

It was my understanding that Mitel used RFC 4733 and not RFC 2833, that is fine. However I am currently working with a SIP provider who is saying we are sending DTMF as In-Band which Mitel says they do not support and neither does the SIP carrier.

So I am left a little confused. Where can DTMF type actually be toggled within the MiVB ecosystem? The only option I've found is to alter the payload number.

[moona]

I have looked at a number of wireshark traces and not one RTPEVENT appears in any of them when calling different IVRs. Which means everything is being sent Inband?

There is a real lack of clarity with Mitel when it comes to how DTMF actually operates within the MiVB..

[JasonTaylor]

I have this issue with BT wholesale SIP.  Speaking between BT and Mitel I have raised a DCR to request that when DTMF inband is presented, MiVB returns error code so that a supported DTMF payload can be re-offered.

[rhys.ci.hughes]

Jason

Has this request been actioned my mitel yet?


Sent from my iPhone using Tapatalk

[acejavelin]

Jason

Has this request been actioned my mitel yet?


Sent from my iPhone using Tapatalk

DCR (Design Change Requests) that have been approved take a while to implement, anywhere from 6 months to years.

The real challenge is getting them approved for implementation... I've done several DCR's, most never get acted on at all. The more people who put in DCR's for the same thing, the more likely it is to be implemented. Remember that DCR's are NOT bug fixes, they are changes to the current implementation of the software.

[sunspark]

All dcr I sent have never been implemented

[petr.necas]

All dcr I sent have never been implemented

I also submitted few DCRs and none of them were implemented either.

[rhys.ci.hughes]

This all sounds like Mitel don’t really listen to requests that come in


Sent from my iPhone using Tapatalk

[rhys.ci.hughes]

Jason

Has this request been actioned my mitel yet?


Sent from my iPhone using Tapatalk

DCR (Design Change Requests) that have been approved take a while to implement, anywhere from 6 months to years.

The real challenge is getting them approved for implementation... I've done several DCR's, most never get acted on at all. The more people who put in DCR's for the same thing, the more likely it is to be implemented. Remember that DCR's are NOT bug fixes, they are changes to the current implementation of the software.

I have an update on this but on SIP trunks. We have had a few calls with Mitel and with calls that come in with inband DTMF we have asked them to send a 488 error message and not accept the call like it currently does. This will then allow Telephone Events to be sent after the 488 coming back from the Mitel. Not sure if it’s gonna be a patch for us on added to the next SP / Release


Sent from my iPhone using Tapatalk