VoIP_Access
Download as PPTX, PDF0 likes342 views
The LBA functions as a load balancer for SIP traffic in the network architecture. It uses two VLANs, one each for SIP and RTP. A session border controller could potentially replace the LBA. If the LBA goes down, new calls cannot be established but existing calls will not be disconnected. The LBA uses two interfaces, one for internal SIP traffic and one for external SIP traffic.
VoIP_Access
- 1. SIP LBA
- 2. Fast Quiz What is the function of the LBA in the NW Architecture ? SIP Load Balancing How many VLAN does the Network Architecture use ? Two SIP and RTP I consider replacing the LBA with Media GW/Gatekeeper/SBC ,What might work ? Session Border Controller The LBA is down , what will happen No new calls, Existing call will not disconnect How many interfaces the LBA is using Two - SIP Internal and SIP External
- 3. Network Architecture VoIP NW RTP SIP RTP SIP LBA Radware AS-I/AS-II LBA Radware AS-I/AS-II Web Server Director Web Server Director RSTP/STP LN CO 10 PWR 1 3 5 7 FD 0 K L LN CO 10 PWR 1 3 5 7 FD 0 K L 2 4 6 8 AC HD Tx Rx RESET SYSOK 1 1 2 T 2 4 6 8 AC HD Tx Rx RESET SYSOK 1 1 2 1 2 3 4 5 6 7 8 T 1 2 3 4 5 6 7 8 SIP SIPSIP 1 3 5 7 9 11 13 15 17 19 21 23 Catalyst 2950 SERIES 1 3 5 7 9 11 13 15 17 19 21 23 Catalyst 2950 SERIES 1 2 1 2 SYST RPS SYST RPS STRT UTIL DUPLXSPEED STRT UTIL DUPLXSPEED MODE 2 4 6 8 10 12 14 16 18 20 22 24 2 4 6 8 10 12 14 16 18 20 22 24 MODE Switch(2950/4948) Switch(2950/4948) SIP RTP CMS HMP Secure Zone Secure Zone
- 4. Software • LBA SW Ver 8.23.06c Comverse SIP version • Future Ver AppDirector 1.06 • Cisco 2960 is using 121-22.EA6 • Cisco 4948 is using 122-25.EWA12
- 5. Hardware • Radware As-I with 256MB Ram Memory • 8 FE and 2 GBIC • Radware AS-II with 256 MB Ram Memory • 16 FE and 5 GBIC • Cisco DMZ SW L2 2950 Default • 24 FE ports + 2 GE • Alternatively Cisco 4948 – 48GE L3 • CMS HMP using 4 NICs (LAN Ports) • 2 for RTP only • 2 for SIP and DMZ<->SZ
- 6. Performance (Aging 900 sec) • Radware As-I with 256MB Ram Memory • 200 new Call per second • Radware AS-II with 256 MB Ram Memory • 250 new Call per second
- 7. LBA – Configuration OverView One Farm VRRP – High Availability Health Monitoring and not connectivity check Layer 7 UDP Load Balancing • Call-ID Header Tracking • Hashing • Persistency Incase of Failover the same Call-ID will reach the same Server Local Triangulation Mode • No layer-3 change • MAC Replacing • Loop Back IP of the servers Must be identical to the Farm VIP Server NAT • Use the same IP of the Farm/Loopback IP
- 8. Loopback Interface SIP App is Bind to the Loopback IP LBA is sending SIP Traffic to the Server’s Loopback IP
- 9. SIP Health Monitor Checking Server Availability • Health Monitor Sending SIP Options Transport Layer UDP Port 5060 Awaits a response of 200 OK from the Server
- 10. SIP Health Monitor - Example Server MAC UDP 5060 (Local Triangulation) LBA Internal Loopback IP Interface SIP Options
- 11. SIP Health Monitor – Example Cont. Server Response 200 OK
- 12. Farm - Parameters •Farm Parameters •IP Address 10.1.2.9 •Farm Name (-n) VOIP-SIP5060 •Admin Status (-as) Enable •Client Aging Time (-at) 60 •Dispatch Method (-dm) Hashing •Connectivity Method (-cm) Disable •Sessions Mode (-sm) RemoveOnSessionEnd-SPS •Redundancy Mode (-fm) Primary / Backup • Extended Farm Parameters •SIP port (-sip) 5060
- 13. Health-Check Parameters •Health Check Parameters •Check Name CHK-CMS1 •Method (-m) SIP UDP •Destination (-d) 10.1.2.9 (Farm IP) •Next HOP (-h) 172.17.4.11 (Server IP) •Port (-p) 5060 (SIP Port) •Interval (-i) 10 •Retries (-r) 3 •Timeout (-t) 3 •Arguments (-a), Listed below •URI 10.1.2.9 (Farm IP) •FROM 172.17.4.6 (Interface IP) •Forward 70 •C1 200
- 14. Persistency Parameters •Persistency Parameters •Farm IP 10.1.2.9 (Farm IP) •Port 5060 •Protocol UDP •Key (-k) Call-ID •Timeout (-t) 1800 seconds •Lookup Mode (-l) Header •Learning Direction (-d) Both Directions
- 15. Configuration Methods Console Configware Insite WEB
- 16. Important Debug Commands System device-info
- 17. Important Debug Commands Cont. net ip-interface
- 18. Important Debug Commands Cont. net route table
- 19. Important Debug Commands Cont. wsd farm table
- 20. Important Debug Commands Cont. wsd farm server table
- 21. Important Debug Commands Cont. Health-monitoring check
- 22. Important Debug Commands Cont. Health-monitoring binding
- 23. Important Debug Commands Cont. System internal wsd session-id-info
- 24. Summary