3CX V16RC - No More DTMF tones with Yealink T58

[mattlowe67]

Hello,

I'm having an issue with the latest release candidate of V16 where my Yealink T58 is not able to send DTMF tones to my 2N IP Verso intercom anymore.

I'm using the door phone feature, but I've also programmed a BLF key as a DTMF tone and it still doesn't send. Manually dialing the code also does not work.

Tones are still able to be sent with T48's and T46's as BLF keys, just not the T58

I've tried firmware
58.80.0.40
58.80.0.65
58.83.0.25

 

[mattlowe67]

Also, while I'm here, Video calls fail using T58 firmware 58.83.0.25 from the IP Verso to the T58 unless I have 'Polycom Compatibility Mode' checked on the IP Verso. The description for this is "Set SDP compatibility with some earlier Polycom and Cisco phone models. If this mode is on, the intercom does not send the sendonly flag in the SDP message in the video codec offer."

Video calls work on 58.80.0.65 and 58.80.0.40 with the box unchecked.

On 58.83.0.25 with the box unchecked and failed video calls, capture reports SIP 481 Call Leg/Transacation does not exist

Also, no matter what version of firmware I use, I still can not get the preview video function to work.

 

[nb]

we checked with same firmware and it works.
Please contact Yealink.

 

[mattlowe67]

Hello,

So I found the issue. When the 2N IP Verso registers directly with my cloud hosted 3CX, DTMF tones work. When the 2N IP Verso registers using the SBC as a proxy, then DTMF tones fail, but only with the T58. T46's and T48's send DTMF tones correctly when 2N IP Verso uses SBC as proxy

Was hoping to use the SBC as to keep traffic local, especially video traffic.

Also - I see these in the 3CX Log

03/19/2019 12:55:44 PM - Exception: ParseException Exactly one button character expected in SIP INFO @ DtmfPayloadContents.cxx:135

 

[nb]

Hello,

So I found the issue. When the 2N IP Verso registers directly with my cloud hosted 3CX, DTMF tones work. When the 2N IP Verso registers using the SBC as a proxy, then DTMF tones fail, but only with the T58. T46's and T48's send DTMF tones correctly when 2N IP Verso uses SBC as proxy

Was hoping to use the SBC as to keep traffic local, especially video traffic.

Also - I see these in the 3CX Log

03/19/2019 12:55:44 PM - Exception: ParseException Exactly one button character expected in SIP INFO @ DtmfPayloadContents.cxx:135

I dont understand - 2N is a device. Its an IP Device. What does that have to do with T58? Why do you relate and connect the failure of the T58 with the 2N? Another IP Phone?
DTMF go to the server. SO if 2N is an intercom, then that intercom is failing proxying the DTMF to the server. I do not understand why you say this affects the T58 (a completely separate ip phone)

 

[mattlowe67]

Setup: Cloud Hosted PBX, Local SBC acts as gateway
Intercom: 2N IP Verso, registered as Extension 100
IP Phones: Yealink T48's, T46's, and T58

When someone presses the call button on the intercom, the IP Verso dials a list of extensions. Right now I have it going to Ext 413 which is the T58. On the phone, the user can unlock the door by sending DTMF code, either by BLF key set to send the DTMF sequence, or on the T58 by pressing the built in Unlock Door button, which does the same thing.

I had the IP Verso using the SBC as a proxy, just like all our phones. Everything worked on Beta2. All T46's, T48's, and T58's were able to send DTMF tones to unlock the front door.

Upgrading to V16RC, with the IP Verso using the SBC as a proxy, the T58 was unable to send DTMF tones, but the 48's and 46's still worked.

I was able to get the T58 to send tones again and unlock the door by having the IP Verso register directly with our PBX instead of using the SBC as a proxy