Managing Monitoring StarLeafLast updated February 27, 2020
The StarLeaf Portal can send email notifications about the state of hardware endpoints that are registered with StarLeaf.
This feature is not enabled by default. Contact StarLeaf technical support if you would like to receive endpoint monitoring notifications.
On a per-organization basis, you can configure a list of email addresses that receive notifications. The email notifications will alert you when StarLeaf room systems connect and disconnect. Additionally, for H.323 endpoints, notifications will alert you for failed or rejected registrations (for example, if H.460 is not available for an endpoint).
Example events that prompt email notification:
|Registration rejected||H.323 registration with IP address 10.4.1.51 via node node.address.starleaf.com for int:61327262104 rejected because H.460 is required for endpoint behind NAT||This H.323 endpoint could not register to the StarLeaf Cloud because H.460 is not enabled. Refer to Adding H.323 endpoints to the Portal for more information|
|Endpoint connected||Endpoint [email protected] (TestEndpointName) connected using H.460 with public address 220.127.116.11 and private address 10.4.1.51 via node node.address.starleaf.com||
When an H.323 endpoint successfully registers and connects to the StarLeaf Cloud, a notification provides IP address information.
When a StarLeaf room system connects to the Cloud, there will be an email notification
|Endpoint disconnected||Endpoint [email protected] (TestEndpointName) using H.460 with public address 18.104.22.168 and private address 10.4.1.51 via node node.address.starleaf.com disconnected||
When an H.323 endpoint disconnects from the StarLeaf Cloud an email notification is sent.
When a StarLeaf room system disconnects from the Cloud, there will be an email notification
|Registration failure||H.323 registration for int:61327262104 failed to authenticate (probably missing or incorrect password)||If an H.323 endpoint fails to authenticate with the StarLeaf Cloud, an email notification is sent. Authentication failure is usually caused by a missing or incorrect password. Refer to Adding H.323 endpoints to the Portal for more information|