No DTMF on J-Series on R11.0.4 SP3

[racom]

I recently upgraded a Powered By Avaya Hosted IP Office from R11.0.2 to R11.0.4 SP3. I had issues on the 11.0.2. After upgrading I received complaints that DTMF was not being recognized when the customer dialed into automated attendants outside of their business. I tried different firmware for the J Series phones, and they all failed. Finally went back to the R11.0.2 and all is good, but then I have my original bug. Avaya said they can't downgrade Server edition. Arggghhh. I am stuck and have an unhappy customer. I opened a case with Avaya, and they are saying it may be weeks before getting a fix. I have tried adding some info in the NoUser that adjusts DTMF settings. I also changed the DTMF to inband in Extensions and nothing. I do know that the H323 phones are fine, only the J series. In System Status, you do see the DTMF being registered when you trace a user. But nothing is being sent out (at least nothing recognizable to auto attendants). Anyone???

 

[Richard10d]

I once had this issue with 9608 phones on a PRI when the default codec was G722. Perhaps the codec translation was the problem. Perhaps that is happening to you.

 

[icet500]

Set the codec in the SIP line to only g711 and select “codec lockdown”

 

[racom]

It is a bug in the R11.0.4 SP3. Avaya is working on it. I was able to upload a .RPM file to downgrade the system to R11.0.4 SP2 and it resolved my issue. If you have J series phones, I would avoid R11.0.4 SP3. Thanks again!

 

[derfloh]

Is it the same with 11.1?

IP Office remote service
Fixed price SIP trunk configuration
CLI based call blocking
SCN fallback over PSTN

 

[racom]

I did not attempt. I learned the hard way to not go to the latest release until the bugs are worked out.

 

[Richard10d]

Powered By does not support 11.1 as well.