FusionPBX - Voicemail DTMF not working

[krishanodedra]

Hello,

We are having an issue where any key's being pressed during the listening of a Voicemail greeting is not registering. For instance as soon as you sign into your VM box with the password and start listening to the VM, you cannot press 7 or any other digits.

 

[bcmike]

Are you accessing your voicemail by pressing *97 or *98 and then logging in?

 

[krishanodedra]

Are you accessing your voicemail by pressing *97 or *98 and then logging in?

*97

 

[bcmike]

Are you using rfc2833 in your sip profile and is the phone also using rfc2833?

Also look in the log and check the byte length of the tones.

 

[krishanodedra]

Are you using rfc2833 in your sip profile and is the phone also using rfc2833?

Also look in the log and check the byte length of the tones.

We are using rfc2833 on both the phone and sip profile.

It looks like we've tracked the problem down to only Yealink T42S's. Any other model Yealink phone works OK.

Firmware version on the 42s doesn't seem to make a difference.

 

[MTR]

Can you list the codecs you have enabled under account settings.

 

[krishanodedra]

Can you list the codecs you have enabled under account settings.

Opus,G722,G729,PCMU,PCMA

The same codecs are enabled on a T52s that is working just fine.

I've also noticed that I cannot see the internal IP of the T42s devices on the registration tab in Fusion. All of our other devices show the internal LAN IP.

 

[taptech]

I've just noticed this problem on my T46S as well as T42S. Oddly, this was working before doing some minor changes to the PBX system... I just wish I knew what caused things to change!
Changing the phone setting to RFC2833+SIP INFO resolves the problem.

 

[taptech]

You can also simply remove the OPUS codec from the list of enabled codecs. Strangely, even if OPUS is at the bottom of the list of enabled codecs, the problem still appears. I'm pretty sure this is a Yealink bug. Someone on irc sent me some very useful info (agree_) about it. You can change the dtmf payload to 103, or just disable OPUS.

 

[aitp/nadmin]

We recently stumbled upon this issue with 4.5.7 on Debian 9; we too have yealink phones.

We were able to resolve it by going to Advanced > Default Settings > Provision (Category) and setting the variable 'yealink_dtmf_type' to the value '3' as pictured in the attached screenshot. After quickly reprovisioning the yealink devices (In Status > Registrations, press "Provision" ), we can DTMF press away through the IVRs and Voicemail menus much more quickly and reliably.

Hope this helps someone.

Respectfully,

aitp/nadmin

 

[kobus.morgan]

Hi All,

I am struggling with an issue where the phones use PCMA, PCMU, G722 and G729. I've got the same codecs on my Fusion Trunk with the difference of OPUS being added as my first priority codec.

Phones are a mix of Polycom IP33X, some polycom IP650 and yealink phones (various).

Calling to an OPUS enabled system works 100% on audio but having some issues when using DTMF though. If I call from an OPUS enabled device, via fusionpbx, to a number compatible with OPUS everything works 100%.

Seems to be something wrt something happening on the backend between the phone and fusion. DTMF seems to register on fusion but not on the remote system.

Any idea what I can try?

Thanks
Kobus

 

[kobus.morgan]

One thing that I have noticed is that, at some point, the remote party sends a Re-INVITE, because PIN has been put it allowing you to call their conference bridge. DTMF seems to break after this happens. At the same time Fusionpbx sends RTP -> OPUS and right after RTP -> G722

 

[kobus.morgan]

Ok so issue sorted. Seems to have been linked to the transcoding portion of Fusion.

I set "media_mix_inbound_outbound_codecs" from true to false. Issue fixed.