MP54/56/58 Support

[SSherwood]

Product	Enterprise Annual
Version Number	18.0 (Build 307)

Hello,

I'm running a POC on the MP54 (MP54, 56 and 58 all seem to use the same firmware - current = MP58(MP54,Teams_MP56)-122.15.0.60.rom) against our v18 3CX. We are planning on moving from a legacy PBX to 3CX, and also are looking to do the teams integration at the same time.

As the MP54 supports running in hybrid mode, I've already managed to get the MP54 to connect to 3CX by selecting the T5x series which appeared the most similar.

Just wondering what is involved in having the MP5X series added to the supported list? We are seeing a firmware validation error during provisioning on the phone, and were having issues with inbound connectivity which seems to be resolved with TCP or TLS transport that I've got working with a modified T5x template.

We are planning on deploying 100+ of the MP5x handsets, so ideally I'd like to streamline the management piece etc..

Any advice?

 

[Evolute IT]

Product	Enterprise Annual
Version Number	18.0 (Build 307)

Hello,

I'm running a POC on the MP54 (MP54, 56 and 58 all seem to use the same firmware - current = MP58(MP54,Teams_MP56)-122.15.0.60.rom) against our v18 3CX. We are planning on moving from a legacy PBX to 3CX, and also are looking to do the teams integration at the same time.

As the MP54 supports running in hybrid mode, I've already managed to get the MP54 to connect to 3CX by selecting the T5x series which appeared the most similar.

Just wondering what is involved in having the MP5X series added to the supported list? We are seeing a firmware validation error during provisioning on the phone, and were having issues with inbound connectivity which seems to be resolved with TCP or TLS transport that I've got working with a modified T5x template.

We are planning on deploying 100+ of the MP5x handsets, so ideally I'd like to streamline the management piece etc..

Any advice?

Teams phones won't be supported ever. Yes the template may work but issues or misconfigurations can happen anytime. Also, not all features may work.

You would be better off using Teams directly in conjunction with Teams Direct Routing through 3CX. This way, you can using your Teams phone but as your 3CX extension.

Also, avoid STUN(Direct SIP) configurations, specially for big deployments.

 

[JohnS_3CX]

Hello,

There are no plans to provide support for Teams firmware-based phones.

We would recommend to purchase the T5x series variants that are compatible with 3CX instead:
https://www.3cx.com/sip-phones/yealink-t5-series/

 

[SSherwood]

Hello,

There are no plans to provide support for Teams firmware-based phones.

We would recommend to purchase the T5x series variants that are compatible with 3CX instead:
https://www.3cx.com/sip-phones/yealink-t5-series/

Thanks for this response, and also for @ConceptsWeb reply too.

My thought behind support for the MP/Teams models of the Yealink phones was to be able to add a layer of additional functionality, and as well, business continuity should there ever be issues with the Azure/MS side of things. Being able to manage the end points more effectively from 3CX is also something which would be welcome.

We do plan on integrating our 3CX with Teams, and the thinking was should Teams be unavailable, the handsets could fail over to SIP via 3CX directly. This added bit of fault tolerance would be tremendously valuable if it could be done correctly, and while I can continue to use a custom template etc., I'm not really that keen on the idea.

So long as 3CX has recognized the possibility already, and set the idea of a fault tolerant configuration of Teams + SIP aside, I think I have my answer. If however this would be of interest, I would certainly like to know.

Many thanks!

PS - the T55A, T58A also supports teams, but are EOL per Yealink, and is thus no longer being developed...

..."
End of Life Announcement for Yealink SIP-T55A-Teams/SFB & SIP-T56A-Teams/SFB & SIP-T58A-Teams/SFB

Dear Customers,

Yealink hereby informs you that the SIP-T55A-Teams/SFB & SIP-T56A-Teams/SFB & SIP-T58A-Teams/SFB has been discontinued since Nov 1st, 2021. After the date, new orders for the product would not be accepted.

After the End-of-Life date, Yealink will not pursue any new feature development on SIP-T55A-Teams/SFB & SIP-T56A-Teams/SFB & SIP-T58A-Teams/SFB, but we will follow the industry standard practices regarding software support of the discontinued (EOL) products. Consistent with such standards, Yealink will continue to offer support and after-sale service.
..."

 

[SAslanis]

Hello, To clarify, did you make MP54 work?
If yes can you share your solution?
We have 20 MP54 devises and thinking to go to 3CX. We do not want them to get wasted.

Thanks in advance

 

[SSherwood]

Hello, To clarify, did you make MP54 work?
If yes can you share your solution?
We have 20 MP54 devises and thinking to go to 3CX. We do not want them to get wasted.

Thanks in advance

Unfortunately, no. We ended up going with a supported handset instead. 3CX made it clear that the native Teams phones weren't going to work, so we went with T54W handsets instead.

 

[SAslanis]

Update for historical reasons.
Yealink has firmware version MP58-OS12(MP54,Teams_MP56,MP54-OS12,MP56-OS12)-122.15.0.142.rom
with this Hybrid Mode can be enabled.
Using Hybrid Mode you can register manually a SIP account and use the phone.
The only htink you can do is get and receive phones, no directory no speed dial nothing
Yet the devise is not totally useless