hiMeshConnect
At a Glance
|
Field |
Value |
|---|---|
|
Product Code |
9303322 |
|
License Type |
Perpetual |
|
Entitlement Basis |
Per hiMesh Peer Connection at Each Endpoint |
|
Lifecycle |
Pre-release - features are subject to change |
|
Base Requirement |
hiMesh |
|
Best For |
Each peer connection at a hi system endpoint beyond its included connection |
What the License Enables
hiMeshConnect licenses a peer relationship locally at one hi installation. Each direct peer connection consumes one entitlement at each connected installation. An installation-wide hiMesh license includes one local hiMeshConnect entitlement.
Included Capabilities
|
Capability |
What It Enables |
|---|---|
|
hiMesh system connection |
License one connection through the hiMesh interface. |
Requirements and Combinations
hiMeshConnect requires hiMesh. Count one entitlement at each hi installation for every peer connected to that installation. Each installation's hiMesh license includes one local connection entitlement. Additional hiMeshConnect licenses are required when the local peer count exceeds that included entitlement.
Planning Notes
Caution
This is a pre-release license. Confirm current availability and feature scope with Riedel Customer Success before planning a deployment; features may change before general release.
Worked Connection Quantity Example
Three installations have direct peer connections A to B and B to C. A and C do not have a direct peer connection.
|
Installation |
Direct Peers |
Required Local Entitlements |
Included with hiMesh |
Additional hiMeshConnect Licenses |
|---|---|---|---|---|
|
A |
B |
1 |
1 |
0 |
|
B |
A and C |
2 |
1 |
1 |
|
C |
B |
1 |
1 |
0 |
Each installation also requires hiMesh and its hiAdvancedWorkflows prerequisite. The additional license belongs to B because B has two direct peers.
This table illustrates entitlement counting only. It does not establish indirect connectivity, media forwarding, or supported workflow behavior between A and C.
Scope Boundary
hiMeshConnect does not replace the hiMesh federation license or the hiAdvancedWorkflows requirement for hiMesh.
Related Pages
Trademarks
Note
All product names, logos, and brands are property of their respective owners. Copyright in third-party software and materials remains with the respective owners. Use of these names does not imply endorsement.
License information is subject to change without notice.