52.7 Transport Initial Peers

The initial peers (see 44.2.2 Setting the ‘Initial Peers’ List) for Real-Time WAN Transport have the following form:

A participant ID limit (see 24.1 Peer Descriptor Format) of ‘0@’ is always assumed for udpv4_wan initial peers because the <peer_public_port> is required in the locator; therefore, Connext does not attempt to reach out to additional ports based on the participant ID.

<peer_public_IP_address>:<peer_public_port> defines the public IP transport address at which the remote DomainParticipant is reachable. For example, assume the following configuration for a remote DomainParticipant:

<dds>

    <qos_profile name="ExternalParticipant">

        <domain_participant_qos>

            <transport_builtin>

                <mask>UDPv4_WAN</mask>

                <udpv4_wan>

                    <public_address>50.10.23.45</public_address>

                        <comm_ports>

                            <default>

                                <host>1234</host>

                                <public>2345</public>

                            </default>

                        </comm_ports>

                </udpv4_wan>

            </transport_builtin>

        </domain_participant_qos>

    </qos_profile>

</dds>

The initial peer that can be used to establish communication with the remote DomainParticipant is:

For scenarios in which Cloud Discovery Service (CDS) is involved, the initial peers have the following form:

<CDS_public_IP_address>:<CDS_public_port> defines the public IP transport address at which CDS is reachable. For example, assume the following CDS configuration:

<dds>

    <cloud_discovery_service name="CDS">

        <transport>

            <element>

                <alias>builtin.udpv4_wan</alias>

                <receive_port>5678</receive_port>

                <property>

                    <element>

                        <name>dds.transport.UDPv4.builtin.public_address</name>

                        <value>50.10.23.45</value>

                    </element>

                </property>

            </element>

        </transport>

    </cloud_discovery_service>

</dds>

The initial peer that can be used to establish communication with CDS is: