Is nobody else having this issue? I've had at least 5 different endpoints loose registration with LS Cloud Over the past couple of months. Sometimes a reboot fixes this, other times, I have had to factory reset and re-register?
We aren't having any known issues with registrations at this time. However, we are looking at ways to resume registration quicker when lost and improving the detection time of a lost registration. I will also note that these changes will be most helpful during brief losses of connectivity and consistent losses of connectivity should be reduced as much as possible through network troubleshooting.
Were your losses of registration during calls? If you have a diagnostic from an Icon during the time period of one of these losses I would be happy to examine and give you a timeline of the loss from the Icon's perspective.
Support Line: 1-877-LIFESIZE (US/Can)
Int. Support Line: 00 800 5433 7493 (EU)
They lose registration in various ways but mostly when idle. I did have one loose registration while recording. Each time they have lost registration, they have done so in unique ways and they never reregister. I don't have any of my systems set to auto reboot but it's something I'm going to have to do. I have one case open where the only way I could get one of my systems to re-register was to factory reset the system. The account that this icon system was tied to completely disassociated itself from the icon 450 and the health monitor on the icon was reporting invalid email or password.
Video Conferencing Technologist, Client Services
Brock University /Information Technology Services
Niagara Region/1812 Sir Isaac Brock Way
St. Catharines, Ontario L2S 3A1
brocku.ca<http://brocku.ca/>/<http://brocku.ca/> T 905-688-5550 x3588<tel:905-688-5550;3588>/ M 289-228-9024<tel:289-228-9024>/
You should see improvement in 3.4 with the type of loss you are describing. The release notes mention the following issue is resolved:
"ICON-1653 - Icon 800 dropped cloud Registration"
I can confirm that the problem description of the above issue is one of your drop scenarios:
Icon800 was performing an RTSP video stream to their VC when it lost its Cloud registration
Also, the resolution to ICON-1653 mentions another case which may be a similar scenario:
ICON was happily registered to both Cloud (SIP1) and PBX (SIP2) until an autoreboot occurred at 5am PDT. After the reboot, SIP2 became registered within 1 min of boot, while SIP1 only asked to register to Cloud for just over 1 min before it just gives up.
I'll be monitoring for 3.4 cases, let us know if you see an improvement.
Retrieving data ...