Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents

Back to SBC Network Deployment Scenarios

Back to Service Provider Deployment Scenarios

Back to Access (UNI) Scenarios

Panel

In this section:

Table of Contents
maxLevel2
minLevel1

Scenario

The 

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

Background Information

  • Refer to the background information in Basic Service Availability - DNS.
  • At the access edge the nature of the connections is temporary.
  • The
    Spacevars
    0product
    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.

Description

Caption
0Figure
1Transmission Protocol Support

Image Modified

  1. 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.
  2. The
    Spacevars
    0product
    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
  3. AS1 only supports UDP, so
    Spacevars
    0product
    s connecting to it must use UDP irrespective of the access side protocol used by the IAD.
    Spacevars
    0product
     performs the protocol conversion.
  4. AS1 only supports TCP, so
    Spacevars
    0product
    s connecting to it must use TCP irrespective of the access side protocol used by the IAD.
    Spacevars
    0product
    performs the protocol conversion.

Pagebreak