VVX300 vs 301 & VVX400 vs 401

[Axsom]

First off I am new to 3cx, I just want to get that out of the way...

I have a VVX 300, 400, & 600 laying around. I see that in the phone provisioning dropdowns in 3CX have 301, 401, & 601.

Can they be used to provision the 300, 400, & 600? As long as their respective firmware has been upgraded? Or do I have to do something else...Or will all my questions be answered when I do my certs this weekend?

 

[VasilisV_3CX]

Hello @Axsom,

The VVX 300 and VVX 301 are different generation devices and therefore haven't been tested with regards to your question above. I have doubts that it would work and we recommend against it.

 

[JohnS_3CX]

Hi @Axsom

Just a clarification to the above, you can use those models if you want but only if they are on the same LAN as the PBX. They have a separate entry, do not use the 301, 401, & 601 templates for those.

They are in the End-Of-Life list so they have a number of limitations, especially with regards to provisioning.
Read the guide here: https://www.3cx.com/sip-phones/polycom-vvx-eol/

 

[Axsom]

Thank you for that - after digging into things a bit [3CX does have wonderful documentation] that's what I had figured out. We just joined in Thursday, so there is a bit to learn...
I am a remote worker, so they're not going to work for me. I was wanting to build a lab here for me to be able to assist out clients. As most of them will be hosted solutions, we will need to just get them new hardware.

 

[JohnS_3CX]

You could set up a local install at home for testing and learning if you want, but those older models are not really representative of the experience you get with the newer supported models that are practically plug and play these days.

You also have the ability of using our various apps for Android, iOS, Windows, or even Webclient. This removes any dependence on deskphones wherever they are not strictly necessary.

By the way since you are new, I highly recommend to continue using our free 3CX Academy and our free training, Upcoming Webinars found on the right column of the forum (I see you already passed Basic )

This will be a great resource to get you started with all the fundamentals!
https://www.3cx.com/3cxacademy/

 

[Axsom]

I absolutely am going to be continuing with the certifications. I am already using Android, Windows, and the Webclient options and find them VERY versatile.
Thank you for your information.

 

[edwindrood]

I have a client who already owned several of the Polycom VVX 410 phones (some 310). We have deployed these in remote offices (remote from the PBX) and all we needed to do was get one Raspberry Pi 4 in each remote office (configured as SBC)

These phones work great and are supported (even though considered "legacy" or "End Of Life").

One remote legacy phone is not cost-effective
If you already own one single legacy phone, purchasing a Raspberry Pi with case and heat-sink, etc. will probably cost you more than purchasing a Fanvil 3Xs phone from e-Bay. Not cost effective to have a Raspberry Pi for just one phone.

However, if you already have an older computer lying around and want to install the 3CX SBC on it, then it would be free and would work great.

The short list of things that these legacy Polycom phones CANT do is not a major obstacle. I could write a long list of things that I can do with these or more about my experience with these if it is desired.

 

[edwindrood]

Curious. I had seen the link that you sent before. It mentions 3CX version 15 and mentions Polycom firmware version 5.6.0.

I have done a lot of testing with 3CX version 16 and polycom firmware 5.9.6.2327. Testing from remote sites using an SBC seems to be working just fine as well. I have seen numerous posts about others using the VVX 410 phones on this forum. Most issues seem to be about provisioning and setting BLF keys. I have not had any problems in these areas with the versions I mention.

It is known that you cannot use provisioning to push out multicast Paging settings nor the Daylight Savings settings (however this can be done from the phones web-interface).

The text youi quoted says these phones will not work remotely WITHOUT an SBC. This is because this model does not have STUN built in (even in latest firmware.) The SBC provides the secure link that is lacking in the legacy phone.

I don't think I would buy this model phone at the outset, but many companies who are dumping RingCentral already own these phones.

From a sales viewpoint, it is a huge factor to migrate a company from any other system where they do not have to purchase all new phones.

 

[JohnS_3CX]

Sorry @edwindrood confused it for another model and jumped the gun