DTMF For Long Distance Carrier Code

[AQS4B]

Group,

I am testing the Yealink T48G with firmware versions 35.8.0.34 and 35.8.0.43.

Calls to PSTN are routed from S4B through Sonus SBC1000 then to AT&T PRI circuits.

Long distance calls require a Long Distance PIN Code from AT&T.

When greeting with the prompt for PIN Code, pressing the number keys on the T48G generate no tone and the long distance call can not be placed.

DTMF tones work with all other IVR systems. The DTMF only fails with AT&T long distance pin code.

Recap: DTMF is not audible for AT&T Long Distance PIN Code but works everywhere else.

Side note: We are also testing the T46G and we can hear the DTMF tones when prompted for AT&T Long Distance PIN with the T46G. However, the PIN code still does not work with the T46G even though it can be heard.

We are testing these for a 1000 user S4B environment and this is hanging us up from purchasing.

[AQS4B]

Additional Note: DTMF works for everything including the AT&T Long Distance PIN when using other S4B phones (Polycom CX & VVX, AudioCodes 440HD, and S4B Desktop Client).

[AQS4B]

I submitted config, syslog, and pcap of scenario to Yealink by way of a Yealink partner and received the following update from Yealink Support:

“Here’s an update, by debug the information provided, our development team seems find the root cause out, and are doing some code changes to verify.
Once we verify patch would good fit for that affected long distance call scenario, will let you know. I ask team and hopefully we can add this fix onto the next release.”


Hopefully this code fix will make it into all of the S4B T4X series phones with the next firmware update.

Fingers crossed that it will be sooner than later. We've tested Polycom (CX, VVX), AudioCodes (440HD - currently using in production), and Yealink (T46G, T48G) and we prefer the Yealink for our VDI environment with S4B.

[dougher1]

(09-02-2016 08:47 PM)AQS4B Wrote:  I submitted config, syslog, and pcap of scenario to Yealink by way of a Yealink partner and received the following update from Yealink Support:

“Here’s an update, by debug the information provided, our development team seems find the root cause out, and are doing some code changes to verify.
Once we verify patch would good fit for that affected long distance call scenario, will let you know. I ask team and hopefully we can add this fix onto the next release.”


Hopefully this code fix will make it into all of the S4B T4X series phones with the next firmware update.

Fingers crossed that it will be sooner than later. We've tested Polycom (CX, VVX), AudioCodes (440HD - currently using in production), and Yealink (T46G, T48G) and we prefer the Yealink for our VDI environment with S4B.

Was this issue ever resolved? I have the same issue only we use Centurylink SIP trunks. All other devices work (polycom cx600, Sangoma analog). The phone client seems to have an issue not honoring rfc2833

[AQS4B]

Sorry for the delayed response. This project got pushed back. To answer your question, NO the DTMF issue was NOT resolved. We still can't get past the AT&T access code. DTMF doesn't work with AT&T access code but still works with all other DTMF/IVR menus.

(12-15-2016 08:58 PM)dougher1 Wrote:  

(09-02-2016 08:47 PM)AQS4B Wrote:  I submitted config, syslog, and pcap of scenario to Yealink by way of a Yealink partner and received the following update from Yealink Support:

“Here’s an update, by debug the information provided, our development team seems find the root cause out, and are doing some code changes to verify.
Once we verify patch would good fit for that affected long distance call scenario, will let you know. I ask team and hopefully we can add this fix onto the next release.”


Hopefully this code fix will make it into all of the S4B T4X series phones with the next firmware update.

Fingers crossed that it will be sooner than later. We've tested Polycom (CX, VVX), AudioCodes (440HD - currently using in production), and Yealink (T46G, T48G) and we prefer the Yealink for our VDI environment with S4B.

Was this issue ever resolved? I have the same issue only we use Centurylink SIP trunks. All other devices work (polycom cx600, Sangoma analog). The phone client seems to have an issue not honoring rfc2833

[dougher1]

Yealink released new f/w for the t-40 SFB phone (54.8.60) which corrects this issue. Still waiting for the T-48 and T-46 fix.

[AQS4B]

Thanks for the update dougher. I'll reach out through some contacts to see if I can get an update on the status of that build for the T-48 and T-46.

We only have the T-48 and T-46 models currently. The latest version of firmware I've tested for the T-48 is 35.8.0.50 and it still doesn't work.

(01-31-2017 06:42 PM)dougher1 Wrote:  Yealink released new f/w for the t-40 SFB phone (54.8.60) which corrects this issue. Still waiting for the T-48 and T-46 fix.

[dougher1]

We're running that f/w also. I have asked my contacts when it will be delivered. I'll post if I hear anything.

[AQS4B]

Dougher1,

I received a copy of the Yealink firmware updates for the T46G sfb and the T48G sfb and the issue is resolved!

The firmware versions that worked for us were:

T46G: T46-28.8.0.60.rom
with Yealink BToE Connector for Lync (3.0.0.31).exe

T48G: T48-35.8.0.60.rom and/or (T48-35.8.1.50.rom)
with Yealink BToE Connector for Lync (3.0.0.31).exe
or with Yealink BToE Connector for Lync (3.0.0.32).exe


Note: We've tested this on 2x T46G's and 2x T48G's. The T46G users were locked out of Active Directory after installing BToE but we unlocked them and everything works.

Call control from SfB deskop application controls the Yealink phones and the long distance codes work.

I'm going to purchase ~ 30 T46G sfb phones and ~5 T48G sfb phones and get more end user feedback as well as work on call recording now.

Just wanted to let you know the updated firmware versions that we saw correcting the issue for us.

Thanks for the feedback and assistance.

(01-31-2017 08:24 PM)dougher1 Wrote:  We're running that f/w also. I have asked my contacts when it will be delivered. I'll post if I hear anything.

[dougher1]

I received both of these, too. T-46 installed fine. The T-48, however, blows up and loads up the syslog with memory leak error messages. I notified yealink.