Applies To:

Show Versions Show Versions

Manual Chapter: SIP Overview
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

SIP Overview

A BIG-IP® system's message routing framework (MRF) SIP solution provides high scalability, availability, and reliability to SIP Proxies, Session Border Controllers, Media Servers and many other SIP devices. The BIG-IP LTM can distribute and balance SIP and RTP traffic among multiple SIP devices, to help maintain availability, under high call volumes. Additionally, the F5 solution can perform advanced health checks on the SIP devices, routing SIP clients away from unstable or unreliable devices and providing increased reliability to existing SIP solutions.

Capabilities

This section provides a concise summary of the BIG-IP® MRF SIP solution.

Load Balancing

  • Route SIP control messages, without modifying SIP headers.
  • The following headers can be configured to be automatically modified.
    • VIA Header inserted
    • Record Router Header inserted
    • Decrementing max forwards
  • Any header attribute can be modified via iRule.
  • Natively route messages based on:
    • From URI
    • To URI
    • Request URI
    • Originating Virtual Server
  • Route messages via iRule on any attribute of the message.
  • Response routing natively using data added to the inserted VIA Header.
  • Response routing available via iRule:
    • Add private header to request
    • Insertion of VIA Header to request via iRule
    • Route to upstream device using received VIA Header
    • Remember data from request processing
  • Bi-directional persistence support.
    • Persistence key selection via configuration or custom key via iRule
  • Connection Re-Use Support
  • High Availability (HA)
    • Connection mirroring
    • Persistence table replication

ALG without SNAT (No Address Translation)

  • Snoop control messages flowing through to manage media flows.
  • iRule can be used to rewrite headers.
  • Create media records in session db.
  • Create deny listeners to drop media packets received before the callee responds with its media details.
  • Create media flows to forward packets between caller and callee.
  • High Availability (HA)
    • Call table replication (supports failback)
    • Control connection mirroring (can be recreated on failback by endpoint)
    • Media flow mirroring
SRTP Compliance (RFC 3711)

We do not support SRTP in ALG without SNAT mode.

Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)