How do I identify which node that an endpoint (Express or Icon) is using for a LSCloud call, while the call is still active?
You can navigate to an Icon's web console using the IP address of the icon, then find the LifeSize UVC ClearSea section of the Preferences tab (it is on the left side). Expand that section, and you will see the IP address of the current node in the Server Address section. It is grayed out during a call, but visible.
You can also find the information on a phone, if connected to the system, by touching System and then touching Info. You will find the IP address of the registered node as the beginning of the dialing string in the Lifesize Cloud Service section of the displayed information.
Don't miss the Express 220 part of the answer here: https://community.lifesize.com/thread/3403-how-to-identify-which-node-an-endpoint-is-connecting-to#comment-7638
Thank you Michael. Any instructions for an Express system? Express 220 specifically.
It looks like there isn't a good way to get at the information from the UI. firstname.lastname@example.org might be able to help.
I was looking at the 'status call active' and 'status call history' commands via cli (log in to the device via putty (default user is auto and pw is lifesize)) but I'm not sure if these provide what you are looking for when the 220 is connected to cloud.
I'll keep digging, too.
Thank you. I'll reach out to Stuart.
Unfortunately the "call status active/history/statistics" doesn't seem to produce an IP address of the cloud nodes. I don't mind using CLI to get this information as opposed to the UI.
I wanted to follow up, since I have been poking around with this all morning. I seem to have found something, if you download the Express 220 "comm" log (through the support page http://ipaddress/support - login: cli/lifesize - in the "Advanced Comm Settings" area, very top of page is comm log).
When viewing this log, it seems that any line with "comm: INFO: Incoming message..." and/or "comm: INFO: Sending message..." appears to list the cloud node IP address. It also appears to list these messages for a call that is active/ongoing while pulling/downloading the log file itself!
Can an engineer confirm if this is correct information?
Eric, yes you are correct. That is a valid way of discovering which node you are currently paired with on a 220 series endpoint. You can then compare which node IP matches from the list below.
Lifesize Server, SfB/Lync, Tunnel Gateway, and Direct Media IP Address Lists
Retrieving data ...