Its been over a year since the last update.
All Lifesize on premise infrastructure is end of sale with no future updates expected. Conference rooms systems (Icons) and Share are the only on premise hardware offered by Lifesize and continue to receive software updates.
My apologies. I am talking about the Icon 400/600/800 that we own.
We are using them as stand alone devices. While we do own licensing for Lifesize cloud we cannot convert these devices to Cloud devices as they would stop internal video traffic across the MPLS from taking place.
We have 60+ locations, some being tightly controlled due to FDA requirements so there is no Internet at these locations.
We refuse to pay for a MPLS link at Lifesize clouds datacenter so we keep these devices in stand alone mode.
I went ahead and corrected the title.
Sorry for the confusion. The post below implies that 3.6 for on premise Icons will be released soon. Many Icon updates are cloud specific (to take advantage of new cloud infrastructure features) and there would not be any benefit to stand alone systems. Good news on the MPLS network preference, we are currently rolling out direct media to the desktop apps and expect to add it to the Icons in the future. This feature keeps the media local for point to point calls (the bridge is still located in the cloud for 3 or more callers).
Direct media: Now Available: Direct Media for Lifesize Clients
Its been about 6 months since they announced it would be out. There has been a load of updates made to the cloud devices that are not cloud specific.
The point to point requires both sides to be lifesize enabled devices correct? Doesn't work for us since we have Cisco devices at some offices.
If you want to have VC with 3rd party devices, you don't need to have Lifesize Cloud on Both the End. If you have Cisco devices on IP, you can Always call from that device to Lifesize Device over Standard SIP/H.323 Protocol.
Here is How:
Expand Your Conference Room Experience with Standards-Based Interoperability
But i would recommend to use our 3rd party Integration Facility. Your Non-Lifesize device can be registered with Lifesize cloud with Single Click.
Here is How you can do that:
Lifesize Third-Party Video Conferencing System Registration Overview
Third-party device registration
For More information You can Always Contact Lifesize Customer Support - We’re Here to Help!
Harish, Thanks for the reply.
If our VC's are cloud enabled can I contact to our remote sites using Internal IP addresses? The Cisco devices are at locations with MPLS access only and no internet access.
Its always been a limitation of Lifesize cloud enabled devices that they cannot call over the LAN. Has this changed?
When Lifesize device is Registered to Lifesize Cloud, All the Calls you make will be Forwarded to Lifesize Cloud Server. If server detect the Local IP, call will be Rejected which is Expected.
So in your case i would suggest 2 solution.
1. Register your 3rd party device to Lifesize Cloud using our 3rd party Integration service.
2. Enable NAT for your 3rd party device and Dial TO public IP from Lifesize Device which works.
Regarding the LAN call, We have Enabled for Desktop Cloud Application. Its known as Direct media.
For Icon Direct media will be available Soon. We are actively working on this already. Phased Rollout for Client-to-Client Direct Media Complete
Unable to register those devices as its a different division that manages them. They are another company owned by the same holding company as mine.
Unable to do Nat as those locations are only on the MPLS and do not see the internet.
Also it is my understanding that Direct Media only works if both devices are on Lifesize Cloud. Upset that something as simple as a routing table on the devices are stopping this from happening.
Any update on this? We are having issues with slow response times when using the remote. We think its linked to this fix but we are stuck at 3.4
HDMI signal quality issues when using short cables
I have the same question, when will new software updates be released for on-premise Icons?
Retrieving data ...