It is possible to include additional Rallypoints in the mesh network without those Rallypoints being member servers in the Rallypoint group. This enables different ICE Server systems to 'bridge' their voice networks by connecting their Rallypoints.

Note that when peering Rallypoints from different ICE Server systems, both systems must be using the same Rallypoint certificates ('certstores') as deployed in the ICE Desktop -> Settings -> Organization -> Certificate management settings. If peer systems are using different certificates, the Rallypoints will fail to establish either inbound or outbound peer connections, and voice audio will not flow between these disparate nodes in the mesh.

To establish the federated peer, add the host and port of the peer Rallypoint, along with its ID (copied from the 'Peer ID' element in the user interface). Each member server in the local group must be able to establish an outbound connection to the remote peer for the mesh to function correctly. If there are multiple nodes in the remote mesh, each member of the remote mesh should be added as a federated peer in the local group.

It is recommended that federated peers be defined on both systems to address issues of asymmetric connectivity caused by firewalls and other network restrictions (for example, the local system can establish and outbound link with the remote system, but the remote system cannot establish an outbound link the other way).

When federating multi-node meshes, each node in the mesh must be federated.