Connecting AAEs on the Local Network
Connect AAEs to distribute audio between stations and allow the APEX Client to locate stations hosted on different AAEs.
Before starting, make sure both AAEs are running and connected to the same local network.
1. Find the destination AAE’s IP address.
On the destination AAE, locate Server IP Address. Click it to copy the address.
2. Open Settings in the APEX Client.
Connect the client in Local Mode to a station on the first AAE, then open Settings.
3. Enter the destination IP address.
In Connected AAEs, enter the address in an unused row beside an AAE 1–10 button.
4. Test and pair the connection.
Click the AAE button beside the address. Watch the connection-status message below the list.
5. Approve the connection on the destination AAE.
During first-time pairing, the destination AAE displays an approval request. Confirm that it identifies the expected computer, then approve it.
6. Verify the connection.
After pairing succeeds, the button displays the destination computer’s name. The adjacent drop-down lists its stations eligible for audio distribution. This list is informational; selecting a station here does not send audio or change the connection.
7. Click Save Changes.
Save the addresses in the Connected AAEs section. These settings belong to the connected AAE and are shared by clients using that AAE.
8. Repeat for additional AAEs.
Use one row per AAE computer, even when that computer hosts multiple stations. Pairing also records the connection on the destination AAE, so it normally does not need to be entered again in reverse.
Once connected, eligible stations appear in the Audio Library’s Distribute Audio selection list. New Wave stations are excluded from audio distribution.
When switching stations in Local Mode, the client can automatically use the discovered AAE address. The user must still have permission to access the selected station.
For reliable connections, reserve each AAE’s IP address in the router or use a properly configured static address. If pairing fails, verify the address, confirm that both AAEs are running, and check that the firewall permits AAE WebSocket communication on TCP port 2002.