Yealink T46U all set up as router phones

[mitty]

Does anyone have or can see any problem with having every supported handset on a PBX acting as it's own router phone ? If for arguments sake a customer wanted 50 Yealink T46U but had no server or didn't want anything dedicated for an SBC could they all be configured on the same 3CX system as router phones and work in this fashion ?

Thanks

 

[TheodorosG_3CX]

Yes all phones can be provisioned as router phones.

 

[JohnMorris]

The T46U isnt a supported handset for Router Phones
Only the Yealink T5 series can be router phones.
https://www.3cx.com/blog/docs/sbc-router-phone/

 

[TheodorosG_3CX]

T46U can be a router phone, however this is not the case for the S series:
• https://www.3cx.com/sip-phones/yealink-t4-series/

 

[KMorley]

In the V20 Basic Certification Class, I specifically asked if there was any limit to the number o SBCs a system can support and was told "No - there is no limit". I currently have a 3CX system loaded with 15 SBCs and it works just fine.

 

[SteveITS]

Off the top of my head…

Pros: all phones portable. Don’t need static IPs (so other phones find it).

Cons: internal audio can’t stay behind a common/shared SBC (like it usually would). “Trunk reconnection” alert triggers whenever a phone drops/connects.

 

[ivank]

Cons: internal audio can’t stay behind a common/shared SBC (like it usually would).

In V20 local traffic should stay local if the router phones are on the same LAN behind the same public IP.

 

[SteveITS]

In V20 local traffic should stay local if the router phones are on the same LAN behind the same public IP.

Oh! That is good to know.