Transmission Protocol Support

In this section:

Scenario

The

Unable to show "metadata-from": No such page "_space_variables"

supports a range of transmission protocol (UDP by default, and TCP) requirements at the access edge.

Refer to the background information in Basic Service Availability - DNS.
At the access edge the nature of the connections is temporary.
The
Unable to show "metadata-from": No such page "_space_variables"
maintains separate IP/transmission stacks on either side of the call and bridge the SIP application. This allows it to fully inter work between transmission protocols. This is also applicable for bridging between IPv4/IPv6 domains.

Transmission Protocol Support

The IADs may use a variety of different transmission layers for the transport of SIP protocol messages. In the access space, UDP is used predominantly but in some cases TCP is used.
The
Unable to show "metadata-from": No such page "_space_variables"
s can talk to either AS1 or AS2. Since AS1 can only accept UDP, the sessions directed to AS1 will be over UDP. Since AS2 requires TCP, the SBCs host an TCP connection to AS2 and send sessions using TCP
AS1 only supports UDP, so
Unable to show "metadata-from": No such page "_space_variables"
s connecting to it must use UDP irrespective of the access side protocol used by the IAD.
Unable to show "metadata-from": No such page "_space_variables"
performs the protocol conversion.
AS1 only supports TCP, so
Unable to show "metadata-from": No such page "_space_variables"
s connecting to it must use TCP irrespective of the access side protocol used by the IAD.
Unable to show "metadata-from": No such page "_space_variables"
performs the protocol conversion.