Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual Page 31

  • Download
  • Add to my manuals
  • Print
  • Page
    / 136
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 30
ServerIron ADX Advanced Server Load Balancing Guide 19
53-1002435-01
Configuring SIP SLB
1
SIP Stateful sample configuration
Load Balancing SIP over TCP
Like HTTP, SIP protocol follows a request and response model. However, SIP transactions are
independent of the underlying transport layer protocol. For example, some transactions run over
UDP connections, some get transported over TCP connections, and some use a combination of TCP
and UDP interchangeably, depending on the size of the data.
Generally most SIP deployments are observed over UDP transport. However, some service
providers use TCP instead of UDP to offer advanced SIP based voice and video services. The
primary reason for this method is to avoid the fragmentation experience over UDP connections and
to use the congestion avoidance mechanism of TCP.
In most cases, TCP and UDP are used interchangeably, depending on the data length. This behavior
poses a few challenges for the SIP application delivery controller vendor. Support for TCP in
addition to UDP is provided for seamless deployment of advanced SIP services. This
implementation is based on RFC 3261.
The sections below describe sample supported topologies for TCP SIP SLB.
Connection handling with SIP requests initiated by client
When a SIP client initiates a call using TCP, it uses either a separate TCP connection for each call or
groups multiple calls together over a single TCP connection.
When a ServerIron receives these calls over a single or multiple TCP connections, it load balances
them among back end proxy servers. The call persistence is maintained using SIP Call-ID.
For the server side connection, the ServerIron uses either a single or multiple TCP connections with
or without using source NAT of the client IP address.
Client side: No connection reuse
Figure 6 shows that each SIP call uses a separate TCP connection. Each request has its unique
Call-ID. ServerIron load balances these requests among backend SIP proxy servers.
Page view 30
1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 135 136

Comments to this Manuals

No comments