managing a highly available voip system
play

Managing a Highly Available VoIP System Andreas Granig - PowerPoint PPT Presentation

Managing a Highly Available VoIP System Andreas Granig <agranig@upcbroadband.com> 1 Agenda Sources of Failures Countermeasures Design Proposal 2 Sources of Failures Major Cause of Downtime 66% for PSTN 75% for


  1. Managing a Highly Available VoIP System Andreas Granig <agranig@upcbroadband.com> 1

  2. Agenda ● Sources of Failures ● Countermeasures ● Design Proposal 2

  3. Sources of Failures ● Major Cause of Downtime ● 66% for PSTN ● 75% for Internet Services 3

  4. Sources of Failures ● Major Cause of Downtime ● 66% for PSTN ● 75% for Internet Services Human Error 4

  5. Countermeasures ● Focus on Simplicity ● Workflow ● Separation ● detached subsystems ● discrete environments 5

  6. Design Proposal 6

  7. “Traditional” Design 7

  8. “Traditional” Design ● Scalability? 8

  9. “Traditional” Design ● Scalability? ● NAT? 9

  10. OpenSER as Load-Balancer 10

  11. OpenSER as Load-Balancer ● One visible IP per LB-Pair ● Defined paths ● Scalable 11

  12. Path-Header in a Nutshell REGISTER sip:proxy1.voip.inode.at SIP/2.0 ... To: Alice <sip:alice@proxy1.voip.inode.at> From: Alice <sip:alice@proxy1.voip.inode.at>;tag=4fed24366e56031 Contact: Alice <sip:alice@172.31.23.177> ... Path: <sip:lb@192.168.1.5;lr;received=sip:172.31.23.177:5060> 12

  13. Path-Header in a Nutshell INVITE sip:alice@172.31.23.177:5060 SIP/2.0 ... To: sip:alice@proxy1.voip.inode.at From: sip:bob@proxy1.voip.inode.at;tag=bd995782dcfef08 Contact: sip:bob@213.229.17.18:5060 ... Route: <sip:lb@192.168.1.5;lr;received=sip:172.31.23.177:5060> ... 13

  14. Summary ● Simplicity ● Modularity 14

  15. Thank you. 15

Recommend


More recommend