1 / 7

Load balancing for SIP media applications

This article discusses the problem of resource consumption in media servers and explores different solutions for implementing load balancing in a media server farm. It explains the use of traditional IP load balancers and leveraging SIP routing for spreading requests. The article also covers round-robin style load balancing and hashing-based methods.

susangriffin
Download Presentation

Load balancing for SIP media applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Load balancing for SIP media applications Fostel 2007 Raphael Coeffic (raphael.coeffic@tekelec.com)

  2. Problem statement • Media servers consume usually a lot of ressources (SEMS is not an exception). • It is then more common to have a media server farm. • How are we supposed to implement the load balancing in such a farm?

  3. Different solutions • At the IP layer: • use traditional IP load balancers (UDP/TCP). • You will need at least some basic support from the SIP side to get that to work. • You could have troubles with NATs or firewalls. • SIP-wise: • leverage SIP routing to spread the requests. • You will need a very fast SIP proxy / load balancer. • Guess what? SER is doing more than 5k transactions / second.

  4. SIP load balancing • Background • Media applications are mostly addressed by request URI (as recommended by relevant RFCs). • How? • Round-robin style: • You may also want to implement some more complicated stuff, maybe based on load feedback. • Requests are just spread, and the load balancer does not need to stay in the signaling path. • Hashing based method: • Some value in the SIP message is hashed to determine the target. • The load balancer could even sit on the signaling path and stay stateless. • Statistics sometimes play tricks if the population is small.

  5. Example: Voice2email Round-robin load balancing 1. INV raphael@voicemail.iptel.org 2. INV raphael@voicemail.iptel.org

  6. Example: PSTN conferencing Hashing based load balancing 1. Dial “0800 CONFERENCE“ 2. INV conf@iptel.org 3. INV conf@iptel.org 5. INV 1234@conf.iptel.org 4. Transfer call to: 1234@conf.iptel.org

  7. Thank you!Questions? Fostel 2007 Raphael Coeffic (raphael.coeffic@tekelec.com)

More Related