ServerIron ADX Advanced Server Load Balancing Guide 7
53-1002435-01
SIP SLB and Call Persistence using ServerIron ADX
1
• Proxy
• Redirect
• Registrar
The ServerIron supports the following methods in accordance with RFC 3261:
• INVITE
• REGISTER
• ACK
• CANCEL
• BYE
• OPTIONS
Additionally, the following methods are supported:
• SUBSCRIBE
• NOTIFY
• Other proprietary methods
SIP and Call Persistence specifications
The SIP Server Load Balancing feature has the following specifications:
• By default, server selection is persistent on Call-ID.
• Pass-through SIP traffic from real SIP servers to SIP clients gets translated. The ServerIron
replaces source IP (SIP server real IP) with Virtual IP (VIP)
• The ServerIron does not modify any of the SIP header fields.
• No SIP Aware NAT support.
• This implementation is based on RFC 3261.
The ServerIron SIP SLB is not implemented as a SIP proxy server, but rather as a load balancer of
proxy or registrar traffic.
The ServerIron does not modify any of the SIP headers. It also does not perform SIP-aware NAT.
Sample deployment topologies
ServerIron switches offer application-aware advanced intelligence for SIP server load balancing.
The following sections describe some SIP Server Load Balancing scenarios.
Design #1: SIP Server Load Balancing with DSR mode
Figure 3 shows an SIP server farm built around ServerIron application switches for higher
availability, accelerated performance, on-demand scalability, and robust security.
Comments to this Manuals