---
title: "Creating SIP Unicast connections in xNode"
slug: "creating-sip-unicast-connections-in-xnode"
updated: 2024-12-16T14:03:39Z
published: 2024-12-16T14:03:39Z
canonical: "docs.telosalliance.com/creating-sip-unicast-connections-in-xnode"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating SIP Unicast connections in xNode

## Scope

This document covers the configuration of unicast audio in the Telos Alliance xNodes running version 2.4.7 or higher.

> [!CAUTION]
> While the **Unicast Link** settings in the xNode still exist, this has been most deprecated by the addition of AES67 SIP Unicast connections. The **Unicast Link** settings are no longer the recommended method for establishing Unicast links.![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/443ede99-4ba3-4ed4-ad30-db1f5dc0f283-unicast-link.png?sv=2026-02-06&spr=https&st=2026-11-01T21%3A20%3A55Z&se=2026-11-01T22%3A20%3A55Z&sr=c&sp=r&sig=iXwrrAhiXL9oiDbebfi6sO0wWTy%2BSCr%2F8CTp%2BcI1FD4%3D)

## Description

Sometimes you may need to send audio from one xNode to another over a link that does not support multicast. In this case, AES67 SIP Unicast links are preferred. For best results, please make sure your xNodes are running [version 2.4.7 or higher.](/v1/docs/xnode-xswitch-and-xselector-software-package-v247-update-instructions-release-notes)

## Enable the SIP Options

SIP connections are disabled as a security feature in version 2.4.7 xNode software and must be enabled.

1. Using a web browser, click on the **Synchronization and QoS** link on the left side menu of your xNode
2. Under the **SIP:** heading set the **Enable SIP Disclosure** to Enabled as shown below
3. Set the **SIP Server Port** (if required)

> [!WARNING]
> UDP port 5060 is the default SIP port and seldom needs to be changed.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/1c06f4a4-02f2-4003-a859-53e008d328ad-image.png?sv=2026-02-06&spr=https&st=2026-11-01T21%3A20%3A55Z&se=2026-11-01T22%3A20%3A55Z&sr=c&sp=r&sig=iXwrrAhiXL9oiDbebfi6sO0wWTy%2BSCr%2F8CTp%2BcI1FD4%3D)

1. Click the **Apply** button

> [!NOTE]
> xNode does NOT require a reboot when enabling this option

## Configuring Sources (the SENDER)

Sources in the xNodes must be configured properly for Unicast. Sources are configured in the SENDING xNode. We will configure the receiver xNode in the next step.

1. Click on the **Sources** link on the main web page of your xNode that will be SENDING the audio.
2. Enter a descriptive name to help you keep the input straight. The name here is unimportant. It's only used for you to see what the source is used for.
3. Leave the **Channel/Address** field blank.
4. Set the Stream Mode to **Stereo 1ms (AES67)** (Standard Stereo can also be used if you are connecting from xNode to xNode).
5. Click **Apply**.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/a502aefb-ed94-41a5-b816-4d2d02274987-image.png?sv=2026-02-06&spr=https&st=2026-11-01T21%3A20%3A55Z&se=2026-11-01T22%3A20%3A55Z&sr=c&sp=r&sig=iXwrrAhiXL9oiDbebfi6sO0wWTy%2BSCr%2F8CTp%2BcI1FD4%3D)
6. The blank Channel/Address is what triggers the xNode to know this is a Unicast connection. Take note of the AES67: link (shown here in green). This will be needed in the next step.

> [!NOTE]
> Repeat these steps if other sources will be used for Unicast. Note that it's okay to mix Multicast and Unicast as needed in an xNode. Sources 1 and 2 are normal Livewire Multicast sources in this example.

## Configure Destinations (the RECEIVER)

1. Click on the **Destinations** link on the main web page of your xNode that will be RECEIVING the audio.
2. Enter a descriptive name to help you keep the input straight. The name here is unimportant. It's only used for you to see what the destination is used for.
3. Enter the AES67 link information from the previous screen in the Channel/Address filed. In this case, it's `sip:8@192.168.2.114.`

> [!WARNING]
> This tells the destination we will use the **SIP:** protocol, the channel is **8**, at (**@**) the IP address **192.168.2.114.** Think of this like the "phone number" for it to get the audio.
4. Click the Apply button.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/681172e7-0004-4ddf-9c6c-a6dbaa0fc377-image.png?sv=2026-02-06&spr=https&st=2026-11-01T21%3A20%3A55Z&se=2026-11-01T22%3A20%3A55Z&sr=c&sp=r&sig=iXwrrAhiXL9oiDbebfi6sO0wWTy%2BSCr%2F8CTp%2BcI1FD4%3D)

## Does it work?

If the network between the two devices is configured property and a connection is allowed you should be receiving audio. You can verify this by observing the meters on the sending xNode.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/446e961b-1b49-4a78-9260-e8fcf67550ba-image.png?sv=2026-02-06&spr=https&st=2026-11-01T21%3A20%3A55Z&se=2026-11-01T22%3A20%3A55Z&sr=c&sp=r&sig=iXwrrAhiXL9oiDbebfi6sO0wWTy%2BSCr%2F8CTp%2BcI1FD4%3D)

And then observing the meters on the Receiving xNode.

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/9137d3bf-3744-4758-8d7c-3530107a7966-image.png?sv=2026-02-06&spr=https&st=2026-11-01T21%3A20%3A55Z&se=2026-11-01T22%3A20%3A55Z&sr=c&sp=r&sig=iXwrrAhiXL9oiDbebfi6sO0wWTy%2BSCr%2F8CTp%2BcI1FD4%3D)

If they don't work the most likely issue is a network issue between the two devices.

## Let us know how we can help

If you have further questions on this topic or have ideas about improving this document, please [contact us](https://www.telosalliance.com/support-request).